Repository navigation
How to deal with updates of software inside sandbox? #5760
|
https://docs.nvidia.com/openshell/latest/about/run-your-first-agent and https://docs.nvidia.com/openshell/latest/tutorials/run-pi-with-openrouter#next-steps Is it safe to make it writable to allow easy updates inside sandbox? (given that the binary's path is used to allow access to some url (as in the guide openrouter.ai is allowed for opencode binary)) Safest way is to recreate container image and sandbox? So if an update is needed, the steps for update are: How are you solving this problem? It can be scripted, or you just ignore updates and work on old version until your work is done, then remove sandbox and create a new one for next task? |
Replies: 1 comment
|
I wouldn't make it writable. The network rule is tied to the binary's real path, and OpenShell pins that file's hash the first time it makes a connection, so after an in-place update the next connection from it gets denied as "executable changed" anyway. Your download, new image, The exception is a harness that runs on Node, like Pi in the tutorial. There the rule lists Docs: https://docs.nvidia.com/openshell/latest/how-it-works/policies/network-rules#binary-matching |
I wouldn't make it writable. The network rule is tied to the binary's real path, and OpenShell pins that file's hash the first time it makes a connection, so after an in-place update the next connection from it gets denied as "executable changed" anyway. Your download, new image,
create --fromflow is the right way to update, and a version build arg on the image keeps it to one rebuild per release.The exception is a harness that runs on Node, like Pi in the tutorial. There the rule lists
node, not the package, so/usr/local/bin/nodecan stay read-only while the package itself lives under the working directory (npm install --prefixsomewhere there) and gets updated in place. That needs an…