I’ve followed the tutorial up to

docker run --rm -it --name myapp-server -p 5000:5000 myapp-release foreground

and it hasn’t mentioned that you should uncomment one of the lines below in order for “phoenix in a release” to work.

config/prod.exs

# ## Using releases
#
# If you are doing OTP releases, you need to instruct Phoenix
# to start the server for all endpoints:
#
config :phoenix, :serve_endpoints, true # <--- here
#
# Alternatively, you can configure exactly which server to
# start per endpoint:
#
#     config :test, TestWeb.Endpoint, server: true

Otherwise cowboy is not started. AFAIK it is not uncommented by default so as not to start cowboy on any other task like phx.digest.

Maybe that’ll help you. Don’t forget to re./build.sh the release.

EDIT: server: true is mentioned later in section 7.

Thanks for putting this guide up. I have some questions about other options in the release building process, and the docker-compose setup.

1. Have you looked at generating the release tarball using multi-stage builds rather than your current build script?

2. Shouldn’t the db service in the docker-compose be using a volume for the data in case the container dies?

You need to add ecto_sql to the @start_apps list.

Hey! Just wanted to drop a quick note saying thanks for the write-up

I followed the guide last night and everything seemed to work fine. I’ll perform some tests and alterations and will comment back further if I find anything specific to talk about.

They can also serve as a cache for dependencies, compiled PLT for dialyzer (for dependencies) and probably some other things that don’t change often too.