Docker Fast Mode doesn't replace working container until restart
Good morning folks! I'm using Docker Fast Mode to apply changes to containers quickly and am not sure if i'm doing it correctly. For now, whenever my code changes i build its project and restart the container with changed dll files. It seems to be not-scalable as i might change many projects and have to manually restart them all!
I'd like to just use the docker compose button in the upper-right corner of IDE with the --build flag but it doesn't recreate containers with changed volumes that are mounted by docker fast mode. So i have to restart them manually again.
What i want to know, if there's something i'm missing?
Please sign in to leave a comment.
With using Docker Fast Mode, only the
basestage of Dockerfile is executed. This documentation explains how it works in Rider.Can you see the new build result mounted to the running container automatically? If it's not, a sample solution (with your Rider settings) that reproduces the issue will be helpful. Or you can share the Dockerfile you are using.
Yep i understand it, and for now to apply my code changes to the cotnainer i build it (after this, new bin files are mounting to the container) and restart container(so previous app process is shut down and new one is up using new bin files), but i wonder if where's a faster way to apply my changes(except the dotnet watch command)
Docker fast mode has the similar performance behavior as building your application locally.