Remove and start new container if changes to

[containers]

Remove and start new container if changes to

[muayyad-alsadi]

Yes, this is planned

We already tag the container with checksum of the the file

[cdhowie]

I'm not actually talking about building an image. I'm talking only about "rebuilding" (destroying and recreating) the container.

What I mean is, if you have a docker-compose.yml file and you change a port forward (as an example) by adding to an existing service:

ports:
    - 127.0.0.1:8080:80

And you run docker-compose up -d then Docker will only destroy and recreate the container(s) for the service that you modified. Using the hash of the entire docker-compose.yml file means that every service would have their containers destroyed and recreated even if only one changed.

[muayyad-alsadi]

Precise delta is difficult there are manu types of changes

• Adding containers
• removing containers
• changing details of a container

A naive implemenation, if the hash changed do down for all.

To make it precise the implementation would be

Fetch old hash from pod/first-container
If not different, don't call down
If different, list all containers and walk on them one by one checking service hash.

But currently this is not possible
Because port mapping is done on the pod not on the container

[cdhowie]

Would there be a way to tag the container with a hash of only whatever settings apply to the container? docker-compose up will only rebuild the containers that actually changed; if you have a compose file with three containers and change the ports exposed to the host for only one container, for example, docker-compose up will only rebuild that one container.

[muayyad-alsadi]

Build is a different matter.
If the image is there, no need for build.