From: Adam Kandur via <help-guix@gnu.org>
To: Bone Baboon <bone.baboon@disroot.org>
Cc: Help Guix <help-guix@gnu.org>
Subject: Re: using docker in guix
Date: Fri, 4 Jun 2021 21:45:05 +0200 (CEST) [thread overview]
Message-ID: <MbNYg9o--3-2@tuta.io> (raw)
In-Reply-To: <87mts693xz.fsf@disroot.org>
that's what i have in docker log
---------------------
time="2021-06-04T22:42:01.608529621+03:00" level=info msg="Starting up"
time="2021-06-04T22:42:01.617401481+03:00" level=info msg="parsed scheme: \"unix\"" module=grpc
time="2021-06-04T22:42:01.617505718+03:00" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc
time="2021-06-04T22:42:01.617555322+03:00" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock 0 <nil>}] <nil>}" module=grpc
time="2021-06-04T22:42:01.617594849+03: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
time="2021-06-04T22:42:45.808007474+03:00" level=info msg="Starting up"
time="2021-06-04T22:42:45.812465107+03:00" level=info msg="parsed scheme: \"unix\"" module=grpc
time="2021-06-04T22:42:45.812538632+03:00" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc
time="2021-06-04T22:42:45.812584087+03:00" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock 0 <nil>}] <nil>}" module=grpc
time="2021-06-04T22:42:45.812624258+03: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
Jun 3, 2021, 18:51 by bone.baboon@disroot.org:
>
> Adam Kandur writes:
>
>> Hi Bone,
>> thank you but this command didn't helped, i got
>> ```
>> Service dockerd could not be started.
>> herd: failed to start service dockerd
>> ```
>> Jun 3, 2021, 17:19 by bone.baboon@disroot.org:
>>
>>> Adam Kandur via writes:
>>>
>>>> i'm sorry, i mean this error "Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?"
>>>>
>>>
>>> You could try `sudo herd restart dockerd`.
>>>
>
> Did you try running `sudo guix system reconfigure
> /path/to/system/configuration.scm` before running `sudo herd restart
> dockerd`?
>
next prev parent reply other threads:[~2021-06-04 19:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 17:06 using docker in guix Adam Kandur via
2021-06-03 17:19 ` Bone Baboon
2021-06-03 17:28 ` Adam Kandur via
2021-06-03 18:51 ` Bone Baboon
2021-06-04 19:45 ` Adam Kandur via [this message]
2021-06-04 23:27 ` Ricardo Wurmus
2021-06-05 12:59 ` Adam Kandur via
2021-06-05 21:36 ` Orhan Kemal Yüksel
-- strict thread matches above, loose matches on Subject: below --
2021-06-03 17:05 Adam Kandur via
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=MbNYg9o--3-2@tuta.io \
--to=help-guix@gnu.org \
--cc=bone.baboon@disroot.org \
--cc=rndd@tuta.io \
/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).