GNU bug report logs - #37161
‘guix pack -f docker’ creates an image without /tmp

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 37161 in the body.
You can then email your comments to 37161 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludovic.courtes <at> inria.fr>
To: bug-Guix <at> gnu.org
Subject: ‘guix pack -f docker’
 creates an image without /tmp
Date: Fri, 23 Aug 2019 16:57:15 +0200

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’.

Message #8 received at 37161 <at> debbugs.gnu.org (full text, mbox):

From: Ricardo Wurmus <rekado <at> elephly.net>
To: 37161 <at> debbugs.gnu.org
Cc: ludovic.courtes <at> inria.fr
Subject: Re: bug#37161: ‘guix pack -f docker’ creates an image without /tmp
Date: Fri, 23 Aug 2019 22:12:19 +0200

> 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

Message #13 received at 37161-done <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludovic.courtes <at> inria.fr>
To: Ricardo Wurmus <rekado <at> elephly.net>
Cc: 37161-done <at> debbugs.gnu.org
Subject: Re: bug#37161: ‘guix pack -f docker’ creates an image without /tmp
Date: Tue, 27 Aug 2019 12:47:22 +0200

Hi,

Ricardo Wurmus <rekado <at> elephly.net> skribis:

>> 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.

> 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’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.