Repository navigation
Run mirai daemons with bubblewrap
#659
Unanswered
king-of-poppk
asked this question in
Q&A
Replies: 1 comment
|
You can use the cfg <- remote_config(
command = "bwrap",
args = c("--ro-bind / /", "--dev /dev", "--tmpfs /tmp", "--unshare-pid", "."),
rscript = "Rscript --vanilla"
)
daemons(4, url = local_url(), remote = cfg)On Linux, the default
Filesystem (ro-binds, tmpfs, hiding
I haven't tested the exact setup above, so feedback welcome! |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
The docs describes how to customize the daemon command using
rscriptandcommandfromremote_config. For instance, to runRscript --vanillainstead of the defaultRscript. There is alsoargs. Not clear to me whether it is the."daemon launch command" that needs to be wrapped with bubblewrap, or whether it is the "Rscript" command that needs wrapping.How could one reliably exploit this feature to start
Rscriptwithbubblewrapwhile still being able to customizeRscriptcommand line arguments (--vanilla, etc.)? How much can we isolate a local mirai daemon from its host? I suppose for instance that--share-netis necessary?!All reactions