How to rebuild and update a container without downtime with docker-compose?

Question

I enjoy a lot using docker-compose.

Eg. on my server, when I want to update my app with minor changes, I only need to git pull origin master && docker-compose restart, works perfectly.

But sometimes, I need to rebuild (eg. I added an npm dependency, need to run npm install again).

In this case, I do docker-compose build --no-cache && docker-compose restart.

I would expect this to :

• create a new instance of my container
• stop the existing container (after the newer has finished building)
• start the new one
• optionally remove the old one, but this could be done manually

But in practice it seems to restart the former one again.

Is it the expected behavior?

How can I handle a rebuild and start the new one after it is built?

Maybe I missed a specific command? Or would it make sense to have it?

Answer 1

from the manual docker-compose restart

If you make changes to your docker-compose.yml configuration these changes will not be reflected after running this command.

you should be able to do

$docker-compose up -d --no-deps --build <service_name> 

The --no-deps will not start linked services.

Answer 2

The problem is that restart will restart your current containers, which is not what you want.

As an example, I just did this

• change the docker file for one of the images
• call docker-compose build to build the images
• call docker-compose down¹ and docker-compose up
  • docker-compose restart will NOT work here
  • using docker-compose start instead also does not work

To be honest, i'm not completly sure you need to do a down first, but that should be easy to check.¹ The bottomline is that you need to call up. You will see the containers of unchanged images restarting, but for the changed image you'll see recreating.

The advantage of this over just calling up --build is that you can see the building-process first before you restart.

1: from the comments; down is not needed, you can just call up --build. Down has some "down"-sides, including possible being destructive to your (volume-)data.