GNU bug report logs - #38720
[PATCH] system: linux-container: Recommend guix container

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 38720 in the body.
You can then email your comments to 38720 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Efraim Flashner <efraim <at> flashner.co.il>
To: guix-patches <at> gnu.org
Subject: [PATCH] system: linux-container: Recommend guix container
Date: Mon, 23 Dec 2019 16:07:58 +0200

[Message part 1 (text/plain, inline)]

I've been using guix containers on foreign systems to bring some Guixy
goodness to the unwashed sysadmins out there. When the container starts
up it displays a message like "Run 'sudo nsenter -a -t 65698' to get a
shell into it." Sometimes when I try to do that I'll get an error
message back about the system's nsenter not knowing about the '-a' flag.
I have found that using a 'guix container' command works well for me.

-- 
Efraim Flashner   <efraim <at> flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[0001-system-linux-container-Recommend-guix-container.patch (text/plain, attachment)]

[signature.asc (application/pgp-signature, inline)]

Message #8 received at 38720 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Efraim Flashner <efraim <at> flashner.co.il>
Cc: 38720 <at> debbugs.gnu.org
Subject: Re: [bug#38720] [PATCH] system: linux-container: Recommend guix
 container
Date: Mon, 30 Dec 2019 23:05:02 +0100

Hi!

Efraim Flashner <efraim <at> flashner.co.il> skribis:

> I've been using guix containers on foreign systems to bring some Guixy
> goodness to the unwashed sysadmins out there. When the container starts
> up it displays a message like "Run 'sudo nsenter -a -t 65698' to get a
> shell into it." Sometimes when I try to do that I'll get an error
> message back about the system's nsenter not knowing about the '-a' flag.
> I have found that using a 'guix container' command works well for me.

Oh.  I was conservative and thought that people would rather use
“standard” tools.

> From f2cd59c9eb756e243a5a01e6cd3a6a6e58a02be6 Mon Sep 17 00:00:00 2001
> From: Efraim Flashner <efraim <at> flashner.co.il>
> Date: Mon, 23 Dec 2019 16:05:04 +0200
> Subject: [PATCH] system: linux-container: Recommend guix container.
>
> * gnu/system/linux-container.scm (container-script)[script]: Recommend
> using 'guix container' to get a shell inside the running container.

[...]

> -              ;; XXX: Should we recommend 'guix container exec'?  It's more
> -              ;; verbose and doesn't bring much.
> -              (info (G_ "Run 'sudo nsenter -a -t ~a' to get a shell into it.~%")
> +              (info (G_ "Run 'sudo guix container exec ~a /run/current-system/profile/bin/bash --login' to get a shell into it.~%")
>                      pid)

The comment is still correct: “guix container exec” is more verbose.
:-)

Should we change it so that “guix container exec PID” without additional
arguments runs /bin/sh by default, or something like that?

Thanks,
Ludo’.

Message #11 received at 38720 <at> debbugs.gnu.org (full text, mbox):

From: Efraim Flashner <efraim <at> flashner.co.il>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 38720 <at> debbugs.gnu.org
Subject: Re: [bug#38720] [PATCH] system: linux-container: Recommend guix
 container
Date: Sun, 5 Jan 2020 20:27:29 +0200

[Message part 1 (text/plain, inline)]

On Mon, Dec 30, 2019 at 11:05:02PM +0100, Ludovic Courtès wrote:
> Hi!
> 
> Efraim Flashner <efraim <at> flashner.co.il> skribis:
> 
> > I've been using guix containers on foreign systems to bring some Guixy
> > goodness to the unwashed sysadmins out there. When the container starts
> > up it displays a message like "Run 'sudo nsenter -a -t 65698' to get a
> > shell into it." Sometimes when I try to do that I'll get an error
> > message back about the system's nsenter not knowing about the '-a' flag.
> > I have found that using a 'guix container' command works well for me.
> 
> Oh.  I was conservative and thought that people would rather use
> “standard” tools.
> 
> > From f2cd59c9eb756e243a5a01e6cd3a6a6e58a02be6 Mon Sep 17 00:00:00 2001
> > From: Efraim Flashner <efraim <at> flashner.co.il>
> > Date: Mon, 23 Dec 2019 16:05:04 +0200
> > Subject: [PATCH] system: linux-container: Recommend guix container.
> >
> > * gnu/system/linux-container.scm (container-script)[script]: Recommend
> > using 'guix container' to get a shell inside the running container.
> 
> [...]
> 
> > -              ;; XXX: Should we recommend 'guix container exec'?  It's more
> > -              ;; verbose and doesn't bring much.
> > -              (info (G_ "Run 'sudo nsenter -a -t ~a' to get a shell into it.~%")
> > +              (info (G_ "Run 'sudo guix container exec ~a /run/current-system/profile/bin/bash --login' to get a shell into it.~%")
> >                      pid)
> 
> The comment is still correct: “guix container exec” is more verbose.
> :-)

I can update the comment :)

> Should we change it so that “guix container exec PID” without additional
> arguments runs /bin/sh by default, or something like that?

I've never really used docker, but I'm pretty sure when you enter a
docker container you also need to give it the path to a binary you want
to run.

I've thought about it a bit and now it displays this:

(ins)efraim <at> E5400 ~/workspace/guix$ sudo /gnu/store/7l5qdb0lw4bbghd17cam8pzdaz86zd3l-run-container
system container is running as PID 13663
Run 'sudo guix container exec 13663 /run/current-system/profile/bin/bash --login'
or run 'sudo nsenter -a -t 13663' to get a shell into it.

making '/gnu/store/8rrwm6wdyzl5i4g38va29azxki412nkr-system' the current system...
setting up setuid programs in '/run/setuid-programs'...
populating /etc from /gnu/store/lvxrcy913ga9g4sg549kk06krb8bbq6m-etc...

I think I like it like this with both options.

-- 
Efraim Flashner   <efraim <at> flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[0001-system-linux-container-Recommend-guix-container.patch (text/plain, attachment)]

[signature.asc (application/pgp-signature, inline)]

Message #14 received at 38720 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Efraim Flashner <efraim <at> flashner.co.il>
Cc: 38720 <at> debbugs.gnu.org
Subject: Re: [bug#38720] [PATCH] system: linux-container: Recommend guix
 container
Date: Mon, 06 Jan 2020 10:56:28 +0100

Hello!

Efraim Flashner <efraim <at> flashner.co.il> skribis:

> From 1e85542ad6de76f761a366ba8d83f61b63789384 Mon Sep 17 00:00:00 2001
> From: Efraim Flashner <efraim <at> flashner.co.il>
> Date: Mon, 23 Dec 2019 16:05:04 +0200
> Subject: [PATCH] system: linux-container: Recommend guix container.
>
> * gnu/system/linux-container.scm (container-script)[script]: Recommend
> using 'guix container' to get a shell inside the running container.

OK, looks reasonable to me.

Thanks!

Ludo’.

Message #19 received at 38720-done <at> debbugs.gnu.org (full text, mbox):

From: Efraim Flashner <efraim <at> flashner.co.il>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 38720-done <at> debbugs.gnu.org
Subject: Re: [bug#38720] [PATCH] system: linux-container: Recommend guix
 container
Date: Mon, 6 Jan 2020 12:20:33 +0200

[Message part 1 (text/plain, inline)]

Thanks. Patch pushed

-- 
Efraim Flashner   <efraim <at> flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.