It’s 4k+ and logs are: https://paste.osmc.tv/asozefafeh
Your /etc/apt/sources.list file has the following lines:
deb [arch=arm64] https://download.docker.com/linux/debian buster stable
# deb-src [arch=arm64] https://download.docker.com/linux/debian buster stable
I’m not sure how well the arm64 version will run on a Vero4K, so I’d suggest that you remove the references to [arch=arm64] and then run:
sudo apt-get update
sudo apt-get dist-upgradeSimilar with the armhf version:
osmc@HTPC:~$ sudo apt-get install docker-ce docker-ce-cli containerd.io
Reading package lists… Done
Building dependency tree
Reading state information… Done
containerd.io is already the newest version (1.3.7-1).
Recommended packages:
cgroupfs-mount | cgroup-lite pigz libltdl7
The following NEW packages will be installed:
docker-ce docker-ce-cli
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/47.5 MB of archives.
After this operation, 204 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Selecting previously unselected package docker-ce-cli.
(Reading database … 46095 files and directories currently installed.)
Preparing to unpack …/docker-ce-cli_5%3a19.03.13~3-0~debian-buster_armhf.deb …
Unpacking docker-ce-cli (5:19.03.13~3-0~debian-buster) …
Selecting previously unselected package docker-ce.
Preparing to unpack …/docker-ce_5%3a19.03.13~3-0~debian-buster_armhf.deb …
Unpacking docker-ce (5:19.03.13~3-0~debian-buster) …
Setting up docker-ce-cli (5:19.03.13~3-0~debian-buster) …
Setting up docker-ce (5:19.03.13~3-0~debian-buster) …
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.
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)
Active: activating (auto-restart) (Result: exit-code) since Mon 2020-09-21 11:29:50 BST; 34ms ago
Docs: https://docs.docker.com
Process: 4565 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
Main PID: 4565 (code=exited, status=1/FAILURE)
Sep 21 11:29:50 HTPC systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Sep 21 11:29:50 HTPC systemd[1]: docker.service: Failed with result ‘exit-code’.
Sep 21 11:29:50 HTPC systemd[1]: Failed to start Docker Application Container Engine.
dpkg: error processing package docker-ce (–configure):
installed docker-ce package post-installation script subprocess returned error exit status 1
Processing triggers for systemd (241-7~deb10u4) …
Errors were encountered while processing:
docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)
Hi,
iptables-persistent & netfilter-persistent, had to uninstall and reinstall both, then the upgrade completed. I suggest removing (backup your config) docker-ce, reinstall then try and running apt-get dist-upgrade again.
Thanks Tom.
Hi,
Yes, have completely wiped docker and tried fresh install of both armhf and 64 but throws same error.
failed to start daemon: Devices cgroup isn't mountedHi,
Is the buster upgrade now complete?
Have you tried rebooting?
Also can you see if this works:
service docker stop
service containerd stop
cgroupfs-umount
cgroupfs-mount
service containerd start
service docker start
Thanks Tom.
Hi Tom,
Buster update went fine. Only docker upgrade won’t complete.
osmc@HTPC:~$ service docker stop
osmc@HTPC:~$ service containerd stop
osmc@HTPC:~$ cgroupfs-umount
-bash: cgroupfs-umount: command not found
osmc@HTPC:~$ cgroupfs-mount
-bash: cgroupfs-mount: command not found
osmc@HTPC:~$ service containerd start
osmc@HTPC:~$ service docker start
Job for docker.service failed because the control process exited with error code
Hi,
You may want to considerer opening a new thread, from some googling it looks like it may issue with docker on buster, rather than issue with the upgrade itself.
I would trying downloading and running check-config.sh :
Thanks Tom.
Cheers Tom. Makes sense and imagine others must be facing this issue, too.
1 Like
I came across this Docker-ce fails to install in Debian GNU/Linux 10 · Issue #769 · docker/for-linux · GitHub which suggests that running openvpn can cause the installation to fail.
This was on an amd64 box, since I’m currently unable to update an OSMC device remotely, but it certainly does fail when openvpn is running. Without openvpn running, it installs just fine.
user@work:/etc/openvpn$ sudo apt-get install --no-install-recommends docker-ce docker-ce-cli containerd.io
Reading package lists... Done
Building dependency tree
Reading state information... Done
Recommended packages:
aufs-tools cgroupfs-mount | cgroup-lite
The following NEW packages will be installed:
containerd.io docker-ce docker-ce-cli
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 91.0 MB of archives.
After this operation, 409 MB of additional disk space will be used.
Get:1 https://download.docker.com/linux/debian buster/stable amd64 containerd.io amd64 1.3.7-1 [24.4 MB]
Get:2 https://download.docker.com/linux/debian buster/stable amd64 docker-ce-cli amd64 5:19.03.13~3-0~debian-buster [44.2 MB]
Get:3 https://download.docker.com/linux/debian buster/stable amd64 docker-ce amd64 5:19.03.13~3-0~debian-buster [22.5 MB]
Fetched 91.0 MB in 11min 36s (131 kB/s)
Selecting previously unselected package containerd.io.
(Reading database ... 145000 files and directories currently installed.)
Preparing to unpack .../containerd.io_1.3.7-1_amd64.deb ...
Unpacking containerd.io (1.3.7-1) ...
Selecting previously unselected package docker-ce-cli.
Preparing to unpack .../docker-ce-cli_5%3a19.03.13~3-0~debian-buster_amd64.deb ...
Unpacking docker-ce-cli (5:19.03.13~3-0~debian-buster) ...
Selecting previously unselected package docker-ce.
Preparing to unpack .../docker-ce_5%3a19.03.13~3-0~debian-buster_amd64.deb ...
Unpacking docker-ce (5:19.03.13~3-0~debian-buster) ...
Setting up containerd.io (1.3.7-1) ...
Created symlink /etc/systemd/system/multi-user.target.wants/containerd.service → /lib/systemd/system/containerd.service.
Setting up docker-ce-cli (5:19.03.13~3-0~debian-buster) ...
Setting up docker-ce (5:19.03.13~3-0~debian-buster) ...
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.
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)
Active: activating (auto-restart) (Result: exit-code) since Mon 2020-09-21 18:10:24 BST; 21ms ago
Docs: https://docs.docker.com
Process: 4594 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
Main PID: 4594 (code=exited, status=1/FAILURE)
Sep 21 18:10:24 work systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Sep 21 18:10:24 work systemd[1]: docker.service: Failed with result 'exit-code'.
Sep 21 18:10:24 work systemd[1]: Failed to start Docker Application Container Engine.
dpkg: error processing package docker-ce (--configure):
installed docker-ce package post-installation script subprocess returned error exit status 1
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for systemd (241-7~deb10u4) ...
Errors were encountered while processing:
docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)
Stop openvpn
user@work:/etc/openvpn$ sudo apt-get install --no-install-recommends docker-ce docker-ce-cli containerd.io
Reading package lists... Done
Building dependency tree
Reading state information... Done
containerd.io is already the newest version (1.3.7-1).
docker-ce-cli is already the newest version (5:19.03.13~3-0~debian-buster).
docker-ce is already the newest version (5:19.03.13~3-0~debian-buster).
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] y
Setting up docker-ce (5:19.03.13~3-0~debian-buster) ...
1 Like
Progresses a bit further but then stops
osmc@HTPC:~$ sudo /etc/init.d/openvpn stop
[ ok ] Stopping openvpn (via systemctl): openvpn.service.
osmc@HTPC:~$ sudo service openvpn stop
osmc@HTPC:~$ sudo apt-get install --no-install-recommends docker-ce docker-ce-cli containerd.io
Reading package lists... Done
Building dependency tree
Reading state information... Done
containerd.io is already the newest version (1.3.7-1).
The following NEW packages will be installed:
docker-ce docker-ce-cli
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/47.5 MB of archives.
After this operation, 204 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Selecting previously unselected package docker-ce-cli.
(Reading database ... 46122 files and directories currently installed.)
Preparing to unpack .../docker-ce-cli_5%3a19.03.13~3-0~debian-buster_armhf.deb ...
Unpacking docker-ce-cli (5:19.03.13~3-0~debian-buster) ...
Selecting previously unselected package docker-ce.
Preparing to unpack .../docker-ce_5%3a19.03.13~3-0~debian-buster_armhf.deb ...
Unpacking docker-ce (5:19.03.13~3-0~debian-buster) ...
Setting up docker-ce-cli (5:19.03.13~3-0~debian-buster) ...
Setting up docker-ce (5:19.03.13~3-0~debian-buster) ...
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.
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)
Active: activating (auto-restart) (Result: exit-code) since Tue 2020-09-22 07:51:08 BST; 34ms ago
Docs: https://docs.docker.com
Process: 25284 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
Main PID: 25284 (code=exited, status=1/FAILURE)
Sep 22 07:51:08 HTPC systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Sep 22 07:51:08 HTPC systemd[1]: docker.service: Failed with result 'exit-code'.
Sep 22 07:51:08 HTPC systemd[1]: Failed to start Docker Application Container Engine.
dpkg: error processing package docker-ce (--configure):
installed docker-ce package post-installation script subprocess returned error exit status 1
Processing triggers for systemd (241-7~deb10u4) ...
Errors were encountered while processing:
docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)
By default, OSMC doesn’t install recommends, so the --no-install-recommends is just emulating OSMC behaviour.
The openvpn part is just a long shot. I’d recommend that you disable openvpn completely:
sudo systemctl disable openvpn
restart the box and try to install docker again. If it still fails, we can probably eliminate openvpn as being the cause of your problem.
1 Like
Played some Vids works well
Unfortunately not. Have disabled openvpn as not using anyway.
As it installed for you, I’m wondering if there are some remnants left over from the stretch version which I have failed to get rid off that are conflicting with the install.
No issue upgrading my pi3
No issue upgrading my pi2
Gonna try my pi1
So what happens if you try to run the command that failed during the installation?
/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
osmc@HTPC:~$ /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
INFO[2020-09-22T22:14:39.018526862+01:00] Starting up
dockerd needs to be started with root. To see how to run dockerd in rootless mode with unprivileged user, see the documentation
osmc@HTPC:~$ sudo /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
INFO[2020-09-22T22:14:49.720918033+01:00] Starting up
failed to load listeners: no sockets found via socket activation: make sure the service was started by systemd
Try sudo systemctl start docker.socket
and then the above command again (with sudo).
I’ve been running the Buster update for the last day with no issues.
Upgrade went mostly smoothly - a bit of a fiddle with smb.conf as the (debian?) package thought I had edited the config. Shelled out and backed up the existing version, only to find, post upgrade, that there were zero differences. Something to do with the OSMC version having it’s own config perhaps?
Everything running fine, and all media I’ve tried to play have been faultless so far.