From: Bruno Victal <mirai@makinata.eu>
To: Pierre Langlois <pierre.langlois@gmx.com>
Cc: arunisaac@systemreboot.net, "Ludovic Courtès" <ludo@gnu.org>,
61627@debbugs.gnu.org
Subject: bug#61627: Cannot start a container built with `guix system container --network'.
Date: Mon, 20 Mar 2023 17:46:23 +0000 [thread overview]
Message-ID: <b52480ff-484e-fdd4-da22-ffd2b096a0f5@makinata.eu> (raw)
In-Reply-To: <873571u0vx.fsf@gmx.com>
Hi,
On 2023-02-19 15:29, Pierre Langlois wrote:
>
> Pierre Langlois <pierre.langlois@gmx.com> writes:
>
> Digging into the container script code, I think the reason is that when
> sharing the network, it's supposed to remove any network-related
> services from the containerized operating system. And it's not aware of
> the new hosts-service-type. The following diff seems to fix the issue:
>
> --8<---------------cut here---------------start------------->8---
> diff --git a/gnu/system/linux-container.scm b/gnu/system/linux-container.scm
> index c2fd55d48e..9190d013bc 100644
> --- a/gnu/system/linux-container.scm
> +++ b/gnu/system/linux-container.scm
> @@ -49,9 +49,12 @@ (define* (container-essential-services os #:key shared-network?)
> (define base
> (remove (lambda (service)
> (memq (service-kind service)
> - (list (service-kind %linux-bare-metal-service)
> - firmware-service-type
> - system-service-type)))
> + (cons* (service-kind %linux-bare-metal-service)
> + firmware-service-type
> + system-service-type
> + (if shared-network?
> + (list hosts-service-type)
> + '()))))
> (operating-system-default-essential-services os)))
>
> (cons (service system-service-type
> --8<---------------cut here---------------end--------------->8---
>
> I wonder if this is a full fix though, I see that we also remove network
> related configuration files, using `%network-configuration-files', and I
> wonder if "/etc/hosts" is still supposed to be there?
>
> --8<---------------cut here---------------start------------->8---
> (define %network-configuration-files
> ;; List of essential network configuration files.
> '("/etc/resolv.conf"
> "/etc/nsswitch.conf"
> "/etc/services"
> "/etc/hosts"))
> --8<---------------cut here---------------end--------------->8---
/etc/hosts is created by hosts-service-type, so if you remove that service
it shouldn't be present anymore.
Cheers,
Bruno
next prev parent reply other threads:[~2023-03-20 17:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-19 14:58 bug#61627: Cannot start a container built with `guix system container --network' Pierre Langlois
2023-02-19 15:29 ` Pierre Langlois
2023-03-20 17:46 ` Bruno Victal [this message]
2023-03-21 12:53 ` Arun Isaac
2023-03-23 12:50 ` Bruno Victal
2023-03-25 16:10 ` Arun Isaac
2023-03-26 13:14 ` Pierre Langlois
2023-03-26 13:41 ` Pierre Langlois
2023-03-26 22:20 ` Arun Isaac
2023-02-26 20:54 ` Nicolò Balzarotti
2023-03-19 19:26 ` Arun Isaac
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=b52480ff-484e-fdd4-da22-ffd2b096a0f5@makinata.eu \
--to=mirai@makinata.eu \
--cc=61627@debbugs.gnu.org \
--cc=arunisaac@systemreboot.net \
--cc=ludo@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.
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.