Docker containers are not started automatically after Docker update from docker-19.03.* to docker-20.10.6.*

This document (000020349) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 12 SP5
SUSE Linux Enterprise Server 15 SP2

Situation

The docker restart policy which enables automatic start of containers (e.g. unless-stopped) is not applied when the docker package is patched from docker-19.03.* to docker-20.10.6.*. As a result, all docker containers are not started automatically when the container host starts using docker-20.10.6.*. On top of that, containers are being killed instead of being properly stopped during the update.

Resolution

There is currently no patch available. Possible workaround is to use an "always" restart policy which means that containers are always started when Docker starts up (regardless of upgrades). Otherwise the docker containers need to be manually stopped before the patching of docker and manually started (when the docker is patched and service/host restarted).

Cause

There is a docker upstream issue for some time which has not been addressed yet.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.