‘guix pack -f docker’ creates an image without /tmp

DoneSubmitted by Ludovic Courtès.
Details
2 participants
  • Ludovic Courtès
  • Ricardo Wurmus
Owner
unassigned
Severity
normal
L
L
Ludovic Courtès wrote on 23 Aug 2019 16:57
(address . bug-Guix@gnu.org)
871rxc53qs.fsf@inria.fr
Hi Guix!

Currently ‘guix pack -f docker’ creates an image that lacks /tmp, but
some programs fail to run when /tmp is missing.

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.

Ludo’.
R
R
Ricardo Wurmus wrote on 23 Aug 2019 22:12
Re: bug#37161: ‘guix pack -f docker ’ creates an image without /tmp
(address . 37161@debbugs.gnu.org)(address . ludovic.courtes@inria.fr)
875zmnk5ek.fsf@elephly.net
Toggle quote (6 lines)
> 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
L
L
Ludovic Courtès wrote on 27 Aug 2019 12:47
(name . Ricardo Wurmus)(address . rekado@elephly.net)(address . 37161-done@debbugs.gnu.org)
87sgpmq405.fsf@inria.fr
Hi,

Ricardo Wurmus <rekado@elephly.net> skribis:

Toggle quote (9 lines)
>> 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?

Yes I think so.

Toggle quote (3 lines)
> If this is still possible, I agree that /tmp should exist in the
> generated image – even if it’s just a plain mount point.

Done in commit 7979a287f8eb84cbbfa44629951572408939a756.

Thanks,
Ludo’.
Closed
?
Your comment

This issue is archived.

To comment on this conversation send email to 37161@debbugs.gnu.org