Supporting a rollback in the container-group would be useful by trying to leave the compose project is a useful state after a failed update.
Technically it should be fairly easy to implement by simply save the previous copy of the docker-compose.yaml file, performing some kind of health check (or just check if the containers are still running if there is no HEALTHCHECK directive being used?), then replacing the active compose file with the previous one, and doing a docker compose up again.
Supporting a rollback in the
container-groupwould be useful by trying to leave the compose project is a useful state after a failed update.Technically it should be fairly easy to implement by simply save the previous copy of the
docker-compose.yamlfile, performing some kind of health check (or just check if the containers are still running if there is noHEALTHCHECKdirective being used?), then replacing the active compose file with the previous one, and doing adocker compose upagain.