Menu
So as I sit and develop my Rails application and I move more settings into the environment section of my docker compose file. I then shut down all containers and rebuild the image. Seems like a lot of work.
Can it be updated without rebuilding the image?
932
You don't need to rebuild your Docker image in development for each tiny code change. If you mount your code into your dev container, you don't have to build a new image on every code change and iterate faster. It's a great feeling when you make changes and see the results right away!
It is not possible to change the environment variables of a running process except from within that process itself. This could be (made to be) possible by allowing to update the environment variable config (via `docker update) and then restarting the containercontainerIn computer science, a container is a class or a data structure whose instances are collections of other objects. In other words, they store objects in an organized way that follows specific access rules. The size of the container depends on the number of objects (elements) it contains.https://en.wikipedia.org › wiki › Container_(abstract_data_type)Container (abstract data type) - Wikipedia.
It's not stored (in a file) anywhere. It's passed from Docker to the process running in the container.
Overriding a single value in your docker-compose . env file is reasonably simple: just set an environment variable with the same name in your shell before running your docker-compose command.
Just change your env variables in your docker-compose file. And docker-compose up -d will updates your variables without rebuild images.
Rebuild images is necessary if you change your dockerfile.
Check this How to reload environment variables in docker-compose container with minimum downtime?
125
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
