unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: James Thomas <jimjoe@gmx.net>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Using Guix inside a Guix container
Date: Mon, 13 Feb 2023 16:51:50 +0530	[thread overview]
Message-ID: <87r0utize9.fsf@gmx.net> (raw)
In-Reply-To: <m1mt5uk7y1.fsf@fastmail.net> (Konrad Hinsen's message of "Fri, 03 Feb 2023 17:52:22 +0100")

Konrad Hinsen wrote:

> Hi Guix,
>
> I have been playing with nested Guix containers recently, with some
> suprising findings, and I am wondering if what I am doing is considered
> officially supported or not.
>
> First: why? My use case is scientific workflows, for example using
> snakemake. I want to run my workflows in Guix containers, for
> reproducibility plus other reasons. But my workflows run other programs
> in their tasks (basically just "shelling out"), and those tasks may use
> their own Guix containers.
>
> Superficially, this works fine if I add the "guix" package to my "outer"
> container and expose the store plus the daemon's socket:
>
>     guix shell -C guix \
>       --expose=/var/guix/daemon-socket/socket \
>       --expose=/gnu/store \
>       -- \
>       guix shell -C coreutils -- ls /
>
> But now for the first surprise:
>
>    $ guix describe
>    Generation 35	janv. 19 2023 12:34:57	(current)
>      guix 8221cb6
>        repository URL: https://git.savannah.gnu.org/git/guix.git
>        branch: master
>        commit: 8221cb6d2ae5624829bf514d25ae234c073e35d5
>
>    $ guix shell -C guix -- guix describe
>      guix 9fe5b49
>        repository URL: https://git.savannah.gnu.org/git/guix.git
>        branch: master
>        commit: 9fe5b490df83ff32e2e0a604bf636eca48b9e240
>
> The Guix in my container is an older one, apparently the 1.4.0 release.
> Why? Can I change this?

Makes sense to me, because the guix package definition was only updated
with the new release (see 'guix edit guix'). Maybe you can try:

  guix shell -C guix --with-version=guix=VERSION -- guix describe

Or --with-commit etc.

>
> My first attempt was time-machine:
>
>     guix shell -C -N guix nss-certs \
>       --expose=/var/guix/daemon-socket/socket \
>       --expose=/gnu/store \
>       -- \
>       guix time-machine -C channels.scm -- describe
>
>    Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'...
>    Authenticating channel 'guix', commits 9edb3f6 to 8221cb6 (331 new commits)...
>    Computing Guix derivation for 'x86_64-linux'... |
>      guix 8221cb6
>        repository URL: https://git.savannah.gnu.org/git/guix.git
>        branch: master
>        commit: 8221cb6d2ae5624829bf514d25ae234c073e35d5
>
> Great! Except that every time I run this command, it does the channel
> update from scratch, so it's prohibitively slow. Sharing
> ${HOME}/.cache/guix seems to fix that. So... finally...
>
>     guix shell -C -N guix nss-certs \
>       --expose=/var/guix/daemon-socket/socket \
>       --expose=/gnu/store \
>       --share=${HOME}/.cache/guix \
>       -- \
>       guix time-machine -C channels.scm \
>       -- \
>       shell -C coreutils \
>       -- \
>       ls /
>
>      guix shell: error: mount: mount "none" on
>      "/tmp/guix-directory.vpOEDC/sys": Operation not permitted

Maybe --expose tmp is needed in the outer container.

--


  parent reply	other threads:[~2023-02-14 11:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03 16:52 Using Guix inside a Guix container Konrad Hinsen
2023-02-03 17:35 ` Wojtek Kosior via Development of GNU Guix and the GNU System distribution.
2023-02-13 11:21 ` James Thomas [this message]
2023-02-13 12:35   ` Jim
2023-02-15  9:49   ` Konrad Hinsen
2023-02-17 15:41     ` Simon Tournier
2023-02-18  9:21       ` Konrad Hinsen
2023-03-13 12:52         ` Simon Tournier
2023-02-21 22:50 ` Ludovic Courtès
2023-02-27 14:27   ` Konrad Hinsen

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=87r0utize9.fsf@gmx.net \
    --to=jimjoe@gmx.net \
    --cc=guix-devel@gnu.org \
    --cc=konrad.hinsen@fastmail.net \
    /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).