unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 38720@debbugs.gnu.org
Subject: [bug#38720] [PATCH] system: linux-container: Recommend guix container
Date: Mon, 30 Dec 2019 23:05:02 +0100	[thread overview]
Message-ID: <87v9pxzcz5.fsf@gnu.org> (raw)
In-Reply-To: <20191223140758.GS1115@E5400> (Efraim Flashner's message of "Mon, 23 Dec 2019 16:07:58 +0200")

Hi!

Efraim Flashner <efraim@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@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’.

  reply	other threads:[~2019-12-30 22:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-23 14:07 [bug#38720] [PATCH] system: linux-container: Recommend guix container Efraim Flashner
2019-12-30 22:05 ` Ludovic Courtès [this message]
2020-01-05 18:27   ` Efraim Flashner
2020-01-06  9:56     ` Ludovic Courtès
2020-01-06 10:20       ` bug#38720: " Efraim Flashner

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=87v9pxzcz5.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=38720@debbugs.gnu.org \
    --cc=efraim@flashner.co.il \
    /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 public inbox

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

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).