all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: 61690@debbugs.gnu.org, Konrad Hinsen <konrad.hinsen@cnrs.fr>
Subject: bug#61690: Failure to mount /sys in nested ‘guix shell’ container
Date: Thu, 02 Mar 2023 18:32:55 +0100	[thread overview]
Message-ID: <875ybjrrco.fsf@jpoiret.xyz> (raw)
In-Reply-To: <87wn3z3wp7.fsf@inria.fr>

[-- Attachment #1: Type: text/plain, Size: 990 bytes --]

Hi Ludo,

Ludovic Courtès <ludovic.courtes@inria.fr> writes:

> Maybe we could, but I must confess I’m totally clueless on this veth
> thing.  :-)
>
> What would this entail?  Hopefully guile-netlink can help?

So, a veth (Virtual Ethernet) device is basically a pipe but for network
devices: they're created in pairs, and any packet going through one end
is instantly received on the other end.  You can then transmit packets
between network namespaces.

One problem that totally slipped by me is that you need to be root to
create a veth device in the original namespace... Rootless containers
use slirp4netns, which is basically a userspace TCP/IP stack
communicating with a special network device in the new namespace (over
which you have complete rights). The situation might thus be a bit more
complicated, since we'd need another library/program as a dependency to
achieve this. I guess there's no best solution for now then :/

Best,
-- 
Josselin Poiret

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]

      reply	other threads:[~2023-03-02 17:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-21 22:45 bug#61690: Failure to mount /sys in nested ‘guix shell’ container Ludovic Courtès
2023-03-02  9:54 ` Josselin Poiret via Bug reports for GNU Guix
2023-03-02 17:11   ` Ludovic Courtès
2023-03-02 17:32     ` Josselin Poiret via Bug reports for GNU Guix [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875ybjrrco.fsf@jpoiret.xyz \
    --to=bug-guix@gnu.org \
    --cc=61690@debbugs.gnu.org \
    --cc=dev@jpoiret.xyz \
    --cc=konrad.hinsen@cnrs.fr \
    --cc=ludovic.courtes@inria.fr \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.