# Cannot backup (connect to postgres) in docker\_dev

**URL:** <https://meta.discourse.org/t/cannot-backup-connect-to-postgres-in-docker-dev/79672>\
**Category:** Bug\
**Created:** [February 2, 2018, 9:13pm UTC](https://meta.discourse.org/t/cannot-backup-connect-to-postgres-in-docker-dev/79672 "2018-02-02T21:13:28Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [February 2, 2018, 9:13pm UTC](https://meta.discourse.org/t/cannot-backup-connect-to-postgres-in-docker-dev/79672/1 "2018-02-02T21:13:28Z")

</div>

Using the docker\_dev you can’t make a backup from the web interface or from within the container using `./script/discourse backup`. Both fail due to postgres permissions issues. This makes using the container to do an import problematic.

What I’ve been doing is editing `/etc/postgresql/9.5/main/pg_hba.conf` and changing the connections from “peer” to “trust”, like this:

```plaintext
local all postgres trust
local all all trust

```

And then restarting the container, as I’ve yet to figure out how to restart postgres from within it.

This likely isn’t the best solution to this problem, and I don’t even know where to look to fix it if I did.

And while I’m complaining, it would be nice if the container included `libmysqlclient-dev`

---

_[View the full topic](https://meta.discourse.org/t/cannot-backup-connect-to-postgres-in-docker-dev/79672)._
