I have a problem running my dockerized phoenix application with postgresql. I specified my docker-compose.yml file to include two services: my phoenix service, build by a dockerfile and a latest postgres image taken from docker hub. My dockerfile for phoenix looks like this: # base image elixer t…

[image] sc4224: If I put these as entrypoints inside of a shell script and run this, my docker container crashes since mix phx.server depends on both ecto create and migrate commands I do not understand that one… ENTRYPOINT /usr/bin/entrypoint.sh #!/usr/bin/env bash set -ex mix ecto.create…

:postgrex, “>= 0.0.0”, host, port, password, username are correct from my understanding

[image] sc4224: :postgrex, “>= 0.0.0”, I asked for the exact version from your mix.lock as it is in the Dockercontainer. [image] sc4224: from my understanding Maybe our or elixirs understand differs from yours, could you just show them? Replacing literal secrets by dummy-values of cou…

“postgrex”: {:hex, :postgrex, “0.13.5” config :my_app, MyApp.Repo, adapter: Ecto.Adapters.Postgres, username: System.get_env(“POSTGRES_USER”), password: System.get_env(“POSTGRES_PASSWORD”), database: “my_postgres_dev”, hostname: “db”, port: 5432, pool_size: 10 maybe docker postgresql:latest…

[image] sc4224: username: System.get_env(“POSTGRES_USER”), password: System.get_env(“POSTGRES_PASSWORD”), Where does your phoenix container know those values from? You are only setting them in db, so System.get_env/1 will return nil, which means in this context, that it shall delete the asso…

Sorry my bad. The system should know this from the environment specified in the docker-compose.yml file under the service db that uses the latest postgres image since i hardcoded them there Should i set them in the phoenix service?

TL;DR: Set them in a way, that makes you able to keep them in synch easily. The environment key is always for the surrounding image only. Usually you are passing those environment variables to the postgresql container to configure it. Then you have to makje sure that all clients use the same cre…

Each service needs its own reference to environment variables. You’ll want to add it to the phoenix service too. You could also put those ENV variables into a file, such as a .env file and then load it in both services with env_file in compose (instead of inlining and duplicating them with environm…

Thanks @cnck1387 I set my POSTGRES_USER and POSTGRES_PASSWORD in the .env file, but it does not seem to work. The error I get back is password authentication failed for user “my_username”. I use this same username and password on my localhost without containers and it works just fine. Just not with …

That’s because the postgres image creates a default database and database user based on those environment variables on the first time it runs (assuming a volume is persisted). Perhaps you changed those values after you’ve upped your project? If that’s the case you’ll want to delete your postgres v…

Yes this did the trick, I also had to add this to my dockerfile CMD mix ecto.create && mix ecto.migrate before doing CMD mix phx.server Do I need to be concerned with this log? db | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/* db | db | wa…

Docker-compose phoenix postgresql

Questions & Help Questions

NobbZ July 24, 2018, 6:23pm 18

I do not understand that one…

ENTRYPOINT /usr/bin/entrypoint.sh

#!/usr/bin/env bash
set -ex

mix ecto.create
mix ecto.migrate

mix phx.server