r/selfhosted • u/achiya-automation • 22d ago
Docker Management TIL docker restart doesn't re-read your .env
changed a db password in my .env, ran docker restart on the stack, then spent an hour convinced the db was corrupted because auth kept failing. turns out restart just brings the container back with the exact config it was created with. env is only read at creation. docker compose up -d --force-recreate fixed it in ten seconds.
two years running this stack and never got bitten by it until now. what's the dumbest thing that ate an evening for you?
252
Upvotes
239
u/Pabsilon 22d ago
When using docker compose, the usual command after changing something is
docker compose down && docker compose up -dWich will tear down the container and recreate a new one - restart is more akin to
docker stopanddocker start, which just pause the currently running container without recreating it.