Editing CommunityData:Klone
From CommunityData
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 130: | Line 130: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
The <code>.sif</code> container is immutable, but you can modify it by converting it to a sandbox. | The <code>.sif</code> container is immutable, but you can modify it by converting it to a sandbox. | ||
Line 150: | Line 148: | ||
The <code>cdsc_base_sandbox</code> is mutable, so we can continue working on that environment and installing more software as we like. We just need to build it as a <code>.sif</code> file to use it on klone. It's also possible to convert the container back into sandbox mode and then modify non-root parts of the container on klone, but this requires running the container in a way that makes the outside klone system invisible! This is useful for installing R or Python packages in userspace within the container. It's not that useful for working with data outside of the container. | The <code>cdsc_base_sandbox</code> is mutable, so we can continue working on that environment and installing more software as we like. We just need to build it as a <code>.sif</code> file to use it on klone. It's also possible to convert the container back into sandbox mode and then modify non-root parts of the container on klone, but this requires running the container in a way that makes the outside klone system invisible! This is useful for installing R or Python packages in userspace within the container. It's not that useful for working with data outside of the container. | ||
So in summary, the workflow is: | So in summary, the workflow is: | ||