For example, I’m starting by explicitly saying to not daemonize (to keep the container running):
bundle exec rails s --port 3000 --no-daemon --environment=production --binding 0.0.0.0
but it seems to decide to do it anyway! And then logically the container exits.
discourse_1_f60e0e3f1186 | [358] Puma starting in cluster mode...
discourse_1_f60e0e3f1186 | [358] * Version 3.12.1 (ruby 2.6.3-p62), codename: Llamas in Pajamas
discourse_1_f60e0e3f1186 | [358] * Min threads: 8, max threads: 32
discourse_1_f60e0e3f1186 | [358] * Environment: production
discourse_1_f60e0e3f1186 | [358] * Process workers: 4
discourse_1_f60e0e3f1186 | [358] * Preloading application
discourse_1_f60e0e3f1186 | [358] * Listening on tcp://0.0.0.0:3000
discourse_1_f60e0e3f1186 | [358] * Daemonizing...
docker-compose-discourse_discourse_1_f60e0e3f1186 exited with code 0
It’s weird that there are arguments, instructions, envars for things, but they aren’t actually honored. It’s hard to tell what I’m supposed to trust.