Closed shelltea closed 5 years ago
I suspect similar to https://github.com/getsentry/onpremise/issues/32 - which they closed without trying. Some docker clients create random hostnames for your instances, and the docker-compose specifies known names as environment variables. Try adding a hostname entry in your docker-compose.yml for smtp, memcached, redis and postgres. Also docker for windows seems to have issues with the volumes. They read as having wrong permissions, so you should probably comment them out if you are on non linux host OS.
Example:
postgres: restart: unless-stopped image: postgres:9.5 hostname: postgres # volumes: # - ./data/postgres:/var/lib/postgresql/data
As above, some database images (e.g. Postgres, MariaDB) have issues on Docker on Windows with volumes that use host path. You can use a named volume instead:
services:
# ...
postgres:
image: postgres:9.5
volumes:
- postgres:/var/lib/postgresql/data
# ↑ use a non-path string here, ie one that doesn't start with /, ., or ~
volumes:
postgres:
Maybe you can turn off your firewall and try ~_~
Closing due to inactivity. @shelltea - feel free to ping me if you are still having issues.
I suspect similar to #32 - which they closed without trying. Some docker clients create random hostnames for your instances, and the docker-compose specifies known names as environment variables. Try adding a hostname entry in your docker-compose.yml for smtp, memcached, redis and postgres. Also docker for windows seems to have issues with the volumes. They read as having wrong permissions, so you should probably comment them out if you are on non linux host OS.
Example:
postgres: restart: unless-stopped image: postgres:9.5 hostname: postgres
Thanks! It worked for me!
This is already being done in the default docker-compose file so not sure why you need anything extra.
Sorry, I didn't specify what actulally worked for me. I added the hostname entry like below:
hostname: postgres
I don't see this line in the current docker-compose on master so in my case I needed to add it
https://docs.docker.com/compose/networking/
By default Compose sets up a single network for your app. Each container for a service joins the default network and is both reachable by other containers on that network, and discoverable by them at a hostname identical to the container name.
So we should not need this setting. I don't know what happened with your setup.
Oh I see. I don't know what happened either. It must have been something in my environment. Thanks for the explanation! :)
No worries! Just trying to make sure there's nothing we should fix on our end. If you everffigure it out, please do tell us in case there's something we can fix.