-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
funannotate_annotate: run with --writable-tmpfs
#1246
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be fine. Hopefully, none of the tools we have in the containers misbehaves.
Currently we use Maybe it is safer to use that one? |
How do you interpret the above error? I thought its not writable at all? |
I interpret it the same way. The docker is configured to use -- Edit --- |
To avoid storage problems and arbitrary mount points, can we use the |
+ 💯 This would be best imo. For security reasons I do not think you want jobs to share Edit: I see actually you are enabling |
Yes. This is really just for tools that have |
We should just keep in mind that OOM killer can then kill the jobs if we not provision enough memory for the extra tmp. Maybe I am blind here, but why do we not mount in the |
It's not either this or mounting centos@vgcnbwc-worker-c36m100-0013:~$ singularity shell /cvmfs/singularity.galaxyproject.org/f/u/funannotate\:1.8.13--pyhdfd78af_0
Singularity> df -h
Filesystem Size Used Available Use% Mounted on
overlay 64.0M 12.0K 64.0M 0% /
devtmpfs 4.0M 0 4.0M 0% /dev
tmpfs 48.9G 0 48.9G 0% /dev/shm
/dev/vda1 49.9G 8.9G 41.0G 18% /etc/localtime
/dev/vda1 49.9G 8.9G 41.0G 18% /etc/hosts
/dev/vda1 49.9G 8.9G 41.0G 18% /home/centos
/dev/vda1 49.9G 8.9G 41.0G 18% /tmp
/dev/vda1 49.9G 8.9G 41.0G 18% /var/tmp
tmpfs 64.0M 12.0K 64.0M 0% /etc/resolv.conf
tmpfs 64.0M 12.0K 64.0M 0% /etc/passwd
tmpfs 64.0M 12.0K 64.0M 0% /etc/group
Singularity> echo a > /test
bash: /test: Read-only file system
Singularity> exit
centos@vgcnbwc-worker-c36m100-0013:~$ singularity shell --writable-tmpfs /cvmfs/singularity.galaxyproject.org/f/u/funannotate\:1.8.13--pyhdfd78af_0
Singularity> df -h
Filesystem Size Used Available Use% Mounted on
fuse-overlayfs 64.0M 12.0K 64.0M 0% /
devtmpfs 4.0M 0 4.0M 0% /dev
tmpfs 48.9G 0 48.9G 0% /dev/shm
/dev/vda1 49.9G 8.9G 41.0G 18% /etc/localtime
/dev/vda1 49.9G 8.9G 41.0G 18% /etc/hosts
/dev/vda1 49.9G 8.9G 41.0G 18% /home/centos
/dev/vda1 49.9G 8.9G 41.0G 18% /tmp
/dev/vda1 49.9G 8.9G 41.0G 18% /var/tmp
tmpfs 64.0M 12.0K 64.0M 0% /etc/resolv.conf
tmpfs 64.0M 12.0K 64.0M 0% /etc/passwd
tmpfs 64.0M 12.0K 64.0M 0% /etc/group
Singularity> echo a > /test
Singularity> Björn is suggesting to enable this for |
--writable-tmpfs
Thank you, I think I understand this now better was confused, because I thought it is only about |
Thanks for merging. Can I redeploy this? We just got one bug report again with this tool and the NFS lock issue today :( |
@sanjaysrikakulam @mira-miracoli anything against this?
I see some read-only /tmp in the logs: