Hi Konrad, On mer., 15 févr. 2023 at 10:49, Konrad Hinsen <konrad.hin...@fastmail.net> wrote:
> That would create a container from the Guix profile. Not sure if this > works at all, but it's very probably not what I want because I have to > add other packages to my container, to get some real work done :-) I am sure you have good reasons for doing this and I am lacking imagination to find them. :-) Which part of Guix do you need inside the containerized shell that you cannot do outside? Basically, you are authorizing the inside Guix to behave with the same permissions as the outside Guix; therefore, why this dance? Well, I understand the needs for running inside a containerized shell: restricted permissions on filestystem, use of --emulate-fhs for allowing untrusted binaries, etc. But I miss what is the need to run Guix inside a containerized shell where it has the permissions as the non-containerized shell. Considering your use-case with Snakemake, what I am doing is to wrap each rule with one containerized Guix shell which controls the permissions, rule by rule; or a big containerized shell: guix shell -C -m manifest.scm --expose=… where manifest.scm contains the tools of each rule and snakemake. Could you provide some details about why you also need Guix? Cheers, simon