all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Robert Smith" <robertsmith@posteo.net>
To: "Ludovic Courtès" <ludo@gnu.org>, luhux <luhux@outlook.com>
Cc: guix-devel@gnu.org
Subject: Re: Provide an option to specify the tmpfs size of the container
Date: Mon, 21 Dec 2020 21:57:06 -0800	[thread overview]
Message-ID: <C7Z30470ONBH.3SMMFXBPYKBEW@amber> (raw)
In-Reply-To: <87mtygvhgy.fsf@gnu.org>

Hi Ludo,

On Mon Dec 14, 2020 at 10:56 AM Ludovic Courtès wrote:
> Hi,
> 
> luhux <luhux@outlook.com> skribis:
> 
> > I am using guix environment --container to containerize my programming environment and runtime environment, but I found that the container / created by this command uses tmpfs and cannot be resized.
> >
> > When a file in the container outputs a lot of logs to the tmpfs of the container, the memory usage of the host will be very high (this is usually something I did not expect)
> >
> > So can provide an option to specify the size of tmpfs?
> 
> Sure, why not.  Would you like to give it a try?

This feature caught my interest and I wanted to investigate a bit :)
tmpfs defaults to half of the available RAM, with the 'size=' option to
the mount command we can increase this limit but I believe that the
upper bound is the sum of the available RAM + swap space. Would it be
worthwhile to allow for the container filesystem to be stored in a
non-temporary filesystem, for example allowing the user to specify the
parent directory of the container root? This would let the container fs
grow as large as the computer storage allows.

-Robert



  reply	other threads:[~2020-12-22  5:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-09 13:58 Provide an option to specify the tmpfs size of the container luhux
2020-12-14  9:56 ` Ludovic Courtès
2020-12-22  5:57   ` Robert Smith [this message]
2021-01-21 11:02     ` 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

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

  git send-email \
    --in-reply-to=C7Z30470ONBH.3SMMFXBPYKBEW@amber \
    --to=robertsmith@posteo.net \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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.