Docker upgrade failing

372 views
Skip to first unread message

mugginsac

unread,
Apr 26, 2018, 5:50:21 PM4/26/18
to Machinekit
I have spent a couple days trying to get docker to run. I keep getting a failure on the installation. Can anybody help?

acondit@D525MW:~$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up docker-ce (18.03.0~ce-0~debian) ...
insserv: warning: script 'realtime' missing LSB tags and overrides
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
invoke-rc.d: initscript docker, action "start" failed.
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
  Drop-In: /etc/systemd/system/docker.service.d
           └─override.conf
   Active: activating (auto-restart) (Result: exit-code) since Thu 2018-04-26 14:40:38 PDT; 66ms ago
     Docs: https://docs.docker.com
  Process: 9301 ExecStart=/usr/bin/dockerd -H tcp://0.0.0.0:2375 (code=exited, status=1/FAILURE)
 Main PID: 9301 (code=exited, status=1/FAILURE)
      CPU: 340ms

Apr 26 14:40:38 D525MW systemd[1]: Failed to start Docker Application Container Engine.
Apr 26 14:40:38 D525MW systemd[1]: docker.service: Unit entered failed state.
Apr 26 14:40:38 D525MW systemd[1]: docker.service: Failed with result 'exit-code'.
dpkg: error processing package docker-ce (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)
acondit@D525MW:~$ sudo systemctl status docker.service
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
  Drop-In: /etc/systemd/system/docker.service.d
           └─override.conf
   Active: failed (Result: exit-code) since Thu 2018-04-26 14:40:40 PDT; 42s ago
     Docs: https://docs.docker.com
  Process: 9394 ExecStart=/usr/bin/dockerd -H tcp://0.0.0.0:2375 (code=exited, status=1/FAILURE)
 Main PID: 9394 (code=exited, status=1/FAILURE)
      CPU: 338ms


Charles Steinkuehler

unread,
Apr 26, 2018, 6:03:12 PM4/26/18
to machi...@googlegroups.com
There's not really enough to tell exactly what went wrong, but IIRC I
ran into similar problems trying to get Docker running on one of my
machines I was also using for CNC tests.

It turns out my problem was with the kernel version or configuration.
The real-time kernel I was using wouldn't work with Docker and the
daemon would just refuse to start. Switching back to a stock Debian
kernel got everything working as expected.
--
Charles Steinkuehler
cha...@steinkuehler.net

mugginsac

unread,
Apr 27, 2018, 12:40:01 AM4/27/18
to Machinekit
I rebooted into the standard kernel, did “sudo apt-get remove docker*”. Then I tried to reinstall. It still failed to complete the installation. It reports that it is failing in dpkg —configure.

I am running Debian Stretch with 4.9.0.6 AMD64.

I also tried the install by downloading the deb for docker-ce but it failed the same way.

schoo...@btinternet.com

unread,
Apr 27, 2018, 11:33:21 AM4/27/18
to machi...@googlegroups.com
I am running v18.03 on an amd64 Buster desktop and v17.03 on my amd64
Stretch server without problems.

As Charles says, it will not run on other than a POSIX kernel, had
problems in the past when I booted into the RT
kernel without thinking about it.

There may be something else in the wind though, this thread is recent
and unresolved
https://github.com/moby/moby/issues/36804

Worth checking the changelogs to see if they have updated without
changing major version number recently?

The obvious first advice is remove it and install your previous version
again via dpkg
Don't think there is anything magic about v18

mugginsac

unread,
Apr 27, 2018, 5:13:06 PM4/27/18
to Machinekit
Schooner,

I uninstalled 18 and tried installing 17.0.3 and it failed too. Must be something wierd with my setup.

Here is the screen from that effort. This was booted in to a non-realtime kernel (4.9.0.6 AMD64).

acondit@D525MW:~$ sudo apt-get install docker-ce=17.03.2~ce-0~debian-stretch

Reading package lists... Done
Building dependency tree      
Reading state information... Done
The following package was automatically installed and is no longer required:
  pigz
Use 'sudo apt autoremove' to remove it.
The following NEW packages will be installed:
  docker-ce
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 21.3 MB of archives.
After this operation, 105 MB of additional disk space will be used.
Get:1 https://download.docker.com/linux/debian stretch/stable amd64 docker-ce amd64 17.03.2~ce-0~debian-stretch [21.3 MB]
Fetched 21.3 MB in 5s (4,250 kB/s)   
Selecting previously unselected package docker-ce.
(Reading database ... 325458 files and directories currently installed.)
Preparing to unpack .../docker-ce_17.03.2~ce-0~debian-stretch_amd64.deb ...
Unpacking docker-ce (17.03.2~ce-0~debian-stretch) ...
Setting up docker-ce (17.03.2~ce-0~debian-stretch) ...
Created symlink /etc/systemd/system/multi-user.target.wants/docker.service → /lib/systemd/system/docker.service.
Created symlink /etc/systemd/system/sockets.target.wants/docker.socket → /lib/systemd/system/docker.socket.

insserv: warning: script 'realtime' missing LSB tags and overrides
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
invoke-rc.d: initscript docker, action "start" failed.
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
  Drop-In: /etc/systemd/system/docker.service.d
           └─override.conf
   Active: failed (Result: exit-code) since Fri 2018-04-27 11:13:30 PDT; 37ms ago
     Docs: https://docs.docker.com
  Process: 4167 ExecStart=/usr/bin/dockerd -H tcp://0.0.0.0:2375 (code=exited, status=1/FAILURE)
 Main PID: 4167 (code=exited, status=1/FAILURE)
      CPU: 515ms

Apr 27 11:13:30 D525MW dockerd[4167]: time="2018-04-27T11:13:30.838786754-07:00" level=debug msg="ReleaseAddress(LocalDefa….17.0.1)"
Apr 27 11:13:30 D525MW dockerd[4167]: time="2018-04-27T11:13:30.838859527-07:00" level=debug msg="ReleasePool(LocalDefault….0.0/16)"
Apr 27 11:13:30 D525MW dockerd[4167]: time="2018-04-27T11:13:30.838944383-07:00" level=debug msg="start clean shutdown of …meout..."
Apr 27 11:13:30 D525MW dockerd[4167]: time="2018-04-27T11:13:30.878010057-07:00" level=debug msg="Cleaning up old mountid : start."
Apr 27 11:13:30 D525MW dockerd[4167]: time="2018-04-27T11:13:30.879990648-07:00" level=debug msg="Cleaning up old mountid : done."
Apr 27 11:13:30 D525MW dockerd[4167]: Error starting daemon: Error initializing network controller: Error creating default…e network
Apr 27 11:13:30 D525MW systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Apr 27 11:13:30 D525MW systemd[1]: Failed to start Docker Application Container Engine.
Apr 27 11:13:30 D525MW systemd[1]: docker.service: Unit entered failed state.
Apr 27 11:13:30 D525MW systemd[1]: docker.service: Failed with result 'exit-code'.
Hint: Some lines were ellipsized, use -l to show in full.

dpkg: error processing package docker-ce (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for systemd (232-25+deb9u3) ...
Processing triggers for man-db (2.7.6.1-2) ...

Errors were encountered while processing:
 docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)

I don't know where to go now.

Alan

schoo...@btinternet.com

unread,
Apr 28, 2018, 9:29:18 AM4/28/18
to machi...@googlegroups.com
> Apr 27 11:13:30 D525MW dockerd[4167]: Error starting daemon: Error initializing network controller: Error creating default…e network
The print is truncated, there should be a more detailed error explanation following a colon after the second ' Error'

eg.
Error starting daemon: Error initializing network controller: could not delete the default bridge network: network bridge has active endpoints

Have a look here, there are several people with similar issues and some resolutions
https://github.com/moby/moby/issues/18283

Otherwise try searching with the full error string
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit
---
You received this message because you are subscribed to the Google Groups "Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages