# Accessing to the database from outside the container

**URL:** https://meta.discourse.org/t/accessing-to-the-database-from-outside-the-container/45257
**Category:** Self-hosting
**Created:** [6월 4, 2016, 7:25오후 UTC](https://meta.discourse.org/t/accessing-to-the-database-from-outside-the-container/45257 "2016-06-04T19:25:40Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [6월 6, 2016, 2:44오전 UTC](https://meta.discourse.org/t/accessing-to-the-database-from-outside-the-container/45257/4 "2016-06-06T02:44:04Z")

</div>

I can’t reproduce the problem. If I do what you describe, it Works For Me. Presumably there’s some other sort of customisation you’ve applied, but not mentioned, that’s causing the problem.

Incidentally, since you’re running on the same machine, you don’t have to expose the port, you can just connect to the Docker-internal IP (`172.17.0.<X>`) on port 5432 and it should work.

---

_[View the full topic](https://meta.discourse.org/t/accessing-to-the-database-from-outside-the-container/45257)._