奇异性使用了哪种TMPSF分区？如何增加它
我想知道如何增加tmpfs singularity sif图像以及它与主机系统上的tmpfs的关系。根据A post
奇异性具有用于从sif图像文件呈现容器的标志。 - 可偿还的tmpfs将为此目的分配少量RAM（由SYS Admins配置，默认情况下仅一堆MB）
）
在我的主机系统上我具有以下tmpfs：
$ df -h | grep tmpfs
tmpfs 13G 2,9M 13G 1% /run
tmpfs 63G 84M 63G 1% /dev/shm
tmpfs 5,0M 0 5,0M 0% /run/lock
tmpfs 63G 0 63G 0% /sys/fs/cgroup
而内部容器内部。我有：
overlay 16M 12K 16M 1% /
...
tmpfs 63G 84M 63G 1% /dev/shm
tmpfs 16M 12K 16M 1% /.singularity.d/libs
tmpfs 13G 2.9M 13G 1% /run/nvidia-persistenced/socket
我只能在我的容器中写小文件（几个kb，否则“没有空间错误”），哪种tmpfs可以使用奇异性，为什么？我该如何增加它？
I'm wondering how can I increase tmpfs size in singularity sif image and how it relates to tmpfs on host system. According to a post by Pawsey Centre:
Singularity has a flag for rendering containers from SIF image files ephemerally writable. --writable-tmpfs will allocate a small amount of RAM for this purpose (configured by the sys admins, by default just a bunch of MB)
On my host system I have the following tmpfs:
$ df -h | grep tmpfs
tmpfs 13G 2,9M 13G 1% /run
tmpfs 63G 84M 63G 1% /dev/shm
tmpfs 5,0M 0 5,0M 0% /run/lock
tmpfs 63G 0 63G 0% /sys/fs/cgroup
While inside container I have:
overlay 16M 12K 16M 1% /
...
tmpfs 63G 84M 63G 1% /dev/shm
tmpfs 16M 12K 16M 1% /.singularity.d/libs
tmpfs 13G 2.9M 13G 1% /run/nvidia-persistenced/socket
I can only write small files in my container (couple of KB, otherwise "no space error" is thrown) Which tmpfs does singularity use and why? How can I increase it?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
TMPFS分区的大小由管理员使用
sessiondir max size配置条目。它默认为16MB，但是您可以通过sudo singularity config global-get“ sessiondir max size”或如果没有足够的权限，请直接检查配置文件：grep sessiondir，请直接检查配置文件。 /USR/local/etc/singularity/singularity.conf。您可以更改配置值（或要求您的管理员这样做）将其增加到所需的尺寸。如果不是一个选项，则需要确保主机文件系统安装在编写数据的位置。无论如何，如果您要编写大量数据，这可能是一个好主意。使用卷时，Docker还会在幕后进行此操作。
The size of the tmpfs partition is set by the admin using the
sessiondir max sizeconfig entry. It defaults to 16MB, but you can check it viasudo singularity config global --get "sessiondir max size"or check the config file directly if you don't have sufficient permissions:grep sessiondir /usr/local/etc/singularity/singularity.conf.You can change the config value (or ask your admins to do it) to increase it to the desired size. If that's not an option, you'll need to make sure the host filesystem is mounted at locations where the data is being written. This is likely a good idea anyway if you'll be writing a lot of data. Docker also does this behind the scenes when using volumes.