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
On 26/04/18 23:02, Charles Steinkuehler wrote:
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.
On 4/26/2018 4:50 PM, mugginsac wrote:
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
--
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 [email protected].
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.
