Actually, not exactly - "You can configure the daemon so that containers remain running if the daemon becomes unavailable. This functionality is called live restore" (https://docs.docker.com/config/containers/live-restore/)
In old/standard configuration (without systemd units for kolla containers) - when I configured "live-restore": true in docker/daemon.json - all containers are remained up and running during docker.service restarting. Now - because of "Requires=docker.service" statement in unit files - all the systemd services are triggered to be restarted together with docker.serivce.
So now - I can't control this behaviour. This is a subject of the bug. And it is really important for the production deployments.
Actually, not exactly - "You can configure the daemon so that containers remain running if the daemon becomes unavailable. This functionality is called live restore" (https:/ /docs.docker. com/config/ containers/ live-restore/)
In old/standard configuration (without systemd units for kolla containers) - when I configured "live-restore": true in docker/daemon.json - all containers are remained up and running during docker.service restarting. Now - because of "Requires= docker. service" statement in unit files - all the systemd services are triggered to be restarted together with docker.serivce.
So now - I can't control this behaviour. This is a subject of the bug. And it is really important for the production deployments.