Bugzilla – Bug 1149613
docker-19.03.1_ce-1.1.ppc64le complains about missing containerd.service file
Last modified: 2019-09-07 05:31:09 UTC
When installing docker-19.03.1_ce-1.1.ppc64le on openSUSE Thumbleweed for PowerPC 64, Little Endian (ppc64le), I'm getting the following output after `zypper install docker`: ``` [rubin@MARVEL ~]$ sudo zypper install docker Loading repository data... Reading installed packages... Resolving package dependencies... The following 3 NEW packages are going to be installed: docker docker-bash-completion docker-libnetwork 3 new packages to install. Overall download size: 23.1 MiB. Already cached: 0 B. After the operation, additional 136.7 MiB will be used. Continue? [y/n/v/...? shows all options] (y): y Retrieving package docker-libnetwork-0.7.0.1+gitr2800_fc5a7d91d54c-1.1.ppc64le (1/3), 531.0 KiB ( 1.9 MiB unpacked) Retrieving: docker-libnetwork-0.7.0.1+gitr2800_fc5a7d91d54c-1.1.ppc64le.rpm ..................................................[done] Retrieving package docker-19.03.1_ce-1.1.ppc64le (2/3), 22.5 MiB (134.7 MiB unpacked) Retrieving: docker-19.03.1_ce-1.1.ppc64le.rpm ....................................................................[done (3.4 MiB/s)] Retrieving package docker-bash-completion-19.03.1_ce-1.1.noarch (3/3), 110.2 KiB (113.5 KiB unpacked) Retrieving: docker-bash-completion-19.03.1_ce-1.1.noarch.rpm .................................................................[done] Checking for file conflicts: .................................................................................................[done] (1/3) Installing: docker-libnetwork-0.7.0.1+gitr2800_fc5a7d91d54c-1.1.ppc64le ................................................[done] (2/3) Installing: docker-19.03.1_ce-1.1.ppc64le ..............................................................................[done] Additional rpm output: Updating /etc/sysconfig/docker ... Failed to try-restart containerd.service: Unit containerd.service not found. Failed to try-restart containerd.socket: Unit containerd.socket not found. ```
That warning can be safely ignored (it is part of a workaround for a redesign of our Docker setup from a few months ago -- and the warning is harmless), and we will remove the commands that are causing it in a later update. Closing since it's a harmless warning that doesn't affect how Docker operates.