From: "Orhan Kemal Yüksel" <orhan.kemal.yueksel@posteo.de>
To: help-guix@gnu.org
Subject: Re: using docker in guix
Date: Sat, 05 Jun 2021 21:36:36 +0000 [thread overview]
Message-ID: <87zgw4hu3f.fsf@posteo.de> (raw)
In-Reply-To: <MbRFMX5--3-2@tuta.io>
Maybe try to kill the containerd-process manually and then restart it
with herd (`herd start containerd`)?
Good luck!
2021-06-05 / 14:59 / help-guix@gnu.org:
> Hi, Ricardo!
> Actually, containerd is started on my system (at least herd status tells me that).
>
>
>
>
> Jun 4, 2021, 23:27 by rekado@elephly.net:
>
>>
>> Adam Kandur via <help-guix@gnu.org> writes:
>>
>>> 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
>>>
>>
>> You need to start containerd.
>>
>> --
>> Ricardo
>>
next prev parent reply other threads:[~2021-06-06 18:43 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
2021-06-04 23:27 ` Ricardo Wurmus
2021-06-05 12:59 ` Adam Kandur via
2021-06-05 21:36 ` Orhan Kemal Yüksel [this message]
-- 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=87zgw4hu3f.fsf@posteo.de \
--to=orhan.kemal.yueksel@posteo.de \
--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).