Skip to content
Discussion options

You must be logged in to vote

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 --from flow 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/node can stay read-only while the package itself lives under the working directory (npm install --prefix somewhere there) and gets updated in place. That needs an…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by zeronumbers
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants