From c27710859c3cb59c439571ddc56cf71c36a1c33c Mon Sep 17 00:00:00 2001 From: Efraim Flashner Date: Mon, 23 Dec 2019 16:05:04 +0200 Subject: 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. --- gnu/system/linux-container.scm | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) (limited to 'gnu/system') diff --git a/gnu/system/linux-container.scm b/gnu/system/linux-container.scm index 2ab679ff3f..c8807398b3 100644 --- a/gnu/system/linux-container.scm +++ b/gnu/system/linux-container.scm @@ -2,6 +2,7 @@ ;;; Copyright © 2015 David Thompson ;;; Copyright © 2016, 2017, 2019 Ludovic Courtès ;;; Copyright © 2019 Arun Isaac +;;; Copyright © 2020 Efraim Flashner ;;; ;;; This file is part of GNU Guix. ;;; @@ -194,11 +195,13 @@ that will be shared with the host system." (define (explain pid) ;; XXX: We can't quite call 'bindtextdomain' so there's actually ;; no i18n. + ;; XXX: Should we really give both options? 'guix container exec' + ;; is a more verbose command. Hard to fail to enter the container + ;; when we list two options. (info (G_ "system container is running as PID ~a~%") pid) - ;; 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'\n") pid) + (info (G_ "or run 'sudo nsenter -a -t ~a' to get a shell into it.~%") pid) (newline (guix-warning-port))) (call-with-container file-systems -- cgit 1.4.1