From: Ricardo Wurmus <rekado@elephly.net>
To: 37161@debbugs.gnu.org
Cc: ludovic.courtes@inria.fr
Subject: bug#37161: ‘guix pack -f docker’ creates an image without /tmp
Date: Fri, 23 Aug 2019 22:12:19 +0200 [thread overview]
Message-ID: <875zmnk5ek.fsf@elephly.net> (raw)
In-Reply-To: <871rxc53qs.fsf@inria.fr>
> One can work around it by asking Docker to create /tmp:
>
> docker run --tmpfs /tmp …
>
> However, it seems easier to just create /tmp upfront in the image.
If /tmp exists in the image can a user still overwrite it to either map
an outside directory to /tmp in the container or to use a tmpfs? If
this is still possible, I agree that /tmp should exist in the generated
image – even if it’s just a plain mount point.
--
Ricardo
next prev parent reply other threads:[~2019-08-23 20:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 14:57 bug#37161: ‘guix pack -f docker’ creates an image without /tmp Ludovic Courtès
2019-08-23 20:12 ` Ricardo Wurmus [this message]
2019-08-27 10:47 ` Ludovic Courtès
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=875zmnk5ek.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=37161@debbugs.gnu.org \
--cc=ludovic.courtes@inria.fr \
/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).