all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: luhux <luhux@outlook.com>
Cc: 42996@debbugs.gnu.org
Subject: bug#42996: icecat can escape from `guix environment --container`
Date: Sun, 23 Aug 2020 12:55:05 -0400	[thread overview]
Message-ID: <20200823165505.GA3636@jasmine.lan> (raw)
In-Reply-To: <20200823164533.GA1897@jasmine.lan>

[-- Attachment #1: Type: text/plain, Size: 861 bytes --]

I believe that this is expected given the specification of `guix
environment`, which is its chapter in the manual. [0]

It says, "For containers, the default behavior is to share the current
working directory with the isolated container and immediately change to
that directory within the container. If this is undesirable, --no-cwd
will cause the current working directory to not be automatically shared
and will change to the user’s home directory within the container
instead."

For this command, the word "share" means that the shared directories
will be read-write.

Did you use the --no-cwd option? If not, were you able to access any
files outside of the current working directory of the `guix environment
...` command invocation?

[0] https://guix.gnu.org/manual/en/html_node/Invoking-guix-environment.html#Invoking-guix-environment

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2020-08-23 16:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-23 10:18 bug#42996: icecat can escape from `guix environment --container` luhux
2020-08-23 15:38 ` Julien Lepiller
     [not found]   ` <PSXP216MB013647CD5DB04CD7F1A49873A0560@PSXP216MB0136.KORP216.PROD.OUTLOOK.COM>
2020-08-24 11:17     ` Julien Lepiller
2020-08-23 16:45 ` Leo Famulari
2020-08-23 16:55   ` Leo Famulari [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200823165505.GA3636@jasmine.lan \
    --to=leo@famulari.name \
    --cc=42996@debbugs.gnu.org \
    --cc=luhux@outlook.com \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.