From: Tanguy LE CARROUR <tanguy@bioneland.org>
To: help-guix@gnu.org
Subject: `dockerd` service not starting
Date: Thu, 31 Mar 2022 11:48:54 +0200 [thread overview]
Message-ID: <164872013406.7465.9006632236576301623@localhost> (raw)
Hi Guix,
My `dockerd` service has stopped working weeks (months!?) ago, but I've
had no use for it in the meantime, so it was no big deal, until today…
My configuration looks like this:
```scm
;…
(use-service-modules desktop docker)
(operating-system
;…
(services
(append
(list
(service docker-service-type)
;…
))))
```
This used to be enough. But now, it doesn't auto-start any more and,
when I `sudo herd start dockerd`, it hangs and displays:
```console
$ sudo herd start dockerd
Password:
Service dockerd could not be started.
herd: failed to start service dockerd
```
The log contains the following:
```log:/var/log/docker.log
time="2022-03-31T11:31:32.027833616+02:00" level=info msg="Starting up"
time="2022-03-31T11:31:32.031576010+02:00" level=info msg="parsed scheme: \"unix\"" module=grpc
time="2022-03-31T11:31:32.031661605+02:00" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc
time="2022-03-31T11:31:32.031760157+02:00" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock 0 <nil>}] <nil>}" module=grpc
time="2022-03-31T11:31:32.031816856+02:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc
failed to start daemon: failed to dial "/run/containerd/containerd.sock": unknown service containerd.services.namespaces.v1.Namespaces: not implemented
```
`containerd` seems to be running fine, even though I sometimes see the
following in the log:
```log:/var/log/docker.log
failed to start containerd: exec: "containerd": executable file not found in $PATH
```
Actually, it looks like a problem reported in another thread [1][] a year ago,
that hasn't (yet) found a solution!? :-(
[1]: https://lists.gnu.org/archive/html/help-guix/2021-06/msg00019.html
Any help welcome!
Regards,
--
Tanguy
next reply other threads:[~2022-03-31 9:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 9:48 Tanguy LE CARROUR [this message]
2022-03-31 19:30 ` `dockerd` service not starting Pierre Langlois
2022-04-01 6:50 ` tanguy
2022-04-01 19:05 ` Pierre Langlois
2022-04-02 9:12 ` Tanguy LE CARROUR
2022-04-02 10:43 ` Pierre Langlois
2022-04-04 7:03 ` Tanguy LE CARROUR
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=164872013406.7465.9006632236576301623@localhost \
--to=tanguy@bioneland.org \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).