Hi, Ricardo!
Actually, containerd is started on my system (at least herd status tells me
that).
Jun 4, 2021, 23:27 by rek...@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
>
