unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Tanguy LE CARROUR <tanguy@bioneland.org>
To: Pierre Langlois <pierre.langlois@gmx.com>
Cc: help-guix@gnu.org
Subject: Re: `dockerd` service not starting
Date: Mon, 04 Apr 2022 09:03:45 +0200	[thread overview]
Message-ID: <164905582504.15440.11342230706141304980@localhost> (raw)
In-Reply-To: <87czhzvjux.fsf@gmx.com>

Hi Pierre,


Quoting Pierre Langlois (2022-04-02 12:43:35)
> Tanguy LE CARROUR <tanguy@bioneland.org> writes:
> > […]
> > I still have the same error message:
> >
> > ```
> > failed to start daemon: failed to dial "/run/containerd/containerd.sock": unknown service containerd.services.namespaces.v1.Namespaces: not implemented
> > ```
> >
> > Next version of `docker` might fix this… or not! ^_^'
> 
> Yeah that might be worth trying, I rebased the docker update series if
> you want to test it: https://issues.guix.gnu.org/52790#7

Thanks!
Unfortunately, it didn't help! :-(


> I wonder if it could be related to the kernel, maybe it could missing
> some support for namespaces?  Are you running the default Guix
> linux-libre kernel?

I don't even know how to run another kernel, so yes! ^_^'


> You could also try and run docker's system test, to check if it works in
> a fresh VM with the default kernel:
> 
>   make check-system TESTS="docker"
> 
> Hopefully this helps!

I'll give it a try! Thanks!


-- 
Tanguy


      reply	other threads:[~2022-04-04  7:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-31  9:48 `dockerd` service not starting Tanguy LE CARROUR
2022-03-31 19:30 ` 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 [this message]

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=164905582504.15440.11342230706141304980@localhost \
    --to=tanguy@bioneland.org \
    --cc=help-guix@gnu.org \
    --cc=pierre.langlois@gmx.com \
    /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).