# 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:** 5

<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 5, 2018, 9:26pm UTC](https://meta.discourse.org/t/cannot-backup-connect-to-postgres-in-docker-dev/79672/5 "2018-02-05T21:26:17Z")

</div>

Welcome home, or away. 🙂

So I’d fix up `~/src/discourse_docker/image/discourse_dev/postgres_dev.template.yml` and submit the PR and **then** after you accepted the PR and rebuilt the image, I could test whether it really worked, right?

If that’s the process, then I think I could contrive to modify `~/src/discourse/bin/docker/boot_dev` to pull my version of that image to test it.

I’ve got three imports running right now. I think that I may end up just spinning up Digital Ocean droplets to run them, but this could be one way to manage running multiple imports at once on a single machine. Or maybe I should be cranking up a VM in VirtualBox. . .

---

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