Arch Linux

mbork

Member

Registered: 2019-01-04

Posts: 14

A borked Docker installation

I installed Docker, but my laptop hanged during the install (or something like that happened, unfortunately, I don't remember exactly). I tried to reinstall, it complained about not wanting to overwrite the existing files, I deleted them and reinstalled. And now Docker won't run. :-(

What can I do? Less importantly now, but perhaps more for the future, what do I do when experiencing a hang during package installing?

When I say

sudo systemctl status docker

this is what I see in the Docker logs:

Jun 10 05:50:10 handles systemd[1]: Starting Docker Application Container Engine...
Jun 10 05:50:10 handles dockerd[850912]: time="2024-06-10T05:50:10.551925199+02:00" level=info msg="Starting up"
Jun 10 05:51:10 handles dockerd[850912]: failed to start daemon: failed to dial "/run/containerd/containerd.sock": failed to dial "/run/containerd/containerd.sock": context deadline exceeded
Jun 10 05:51:10 handles systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Jun 10 05:51:10 handles systemd[1]: docker.service: Failed with result 'exit-code'.
Jun 10 05:51:10 handles systemd[1]: Failed to start Docker Application Container Engine.
Jun 10 05:51:10 handles systemd[1]: docker.service: Consumed 1.006s CPU time.
Jun 10 05:51:12 handles systemd[1]: docker.service: Scheduled restart job, restart counter is at 5.

Edit: and while at that, it seems that I borked more packages. :-( What should I do with this?

$ sudo pacman -S containerd 
[sudo] password for mbork: 
resolving dependencies...
looking for conflicting packages...

Packages (1) containerd-1.7.18-1

Total Installed Size:  122.05 MiB

:: Proceed with installation? [Y/n] 
(1/1) checking keys in keyring                                  [###################################] 100%
(1/1) checking package integrity                                [###################################] 100%
(1/1) loading package files                                     [###################################] 100%
(1/1) checking for file conflicts                               [###################################] 100%
error: failed to commit transaction (conflicting files)
containerd: /usr/bin/containerd exists in filesystem
containerd: /usr/bin/containerd-shim exists in filesystem
containerd: /usr/bin/containerd-shim-runc-v1 exists in filesystem
containerd: /usr/bin/containerd-shim-runc-v2 exists in filesystem
containerd: /usr/bin/containerd-stress exists in filesystem
containerd: /usr/bin/ctr exists in filesystem
containerd: /usr/lib/systemd/system/containerd.service exists in filesystem
containerd: /usr/share/bash-completion/completions/ctr exists in filesystem
containerd: /usr/share/man/man5/containerd-config.toml.5.gz exists in filesystem
containerd: /usr/share/man/man8/containerd-config.8.gz exists in filesystem
containerd: /usr/share/man/man8/containerd.8.gz exists in filesystem
containerd: /usr/share/man/man8/ctr.8.gz exists in filesystem
containerd: /usr/share/zsh/site-functions/_ctr exists in filesystem
Errors occurred, no packages were upgraded.

Last edited by mbork (2024-06-10 04:35:56)

impossibleveins23

Member

From: Israel

Registered: 2022-06-18

Posts: 147

Re: A borked Docker installation

See this

---

* Good formatted problem description will cause good and quick solution
* Please don't forget to mark as [SOLVED].