Summary
Currently from CLI it seems we can only set up a "real fs" mountpoint (default) or a readonly mountpoint, not an "overlay" mount point.
This may be a surprising/risky default as the main README says:
Outside your machine doesn't feel a thing. Every sandbox runs on its own copy-on-write filesystem that vanishes when you're done.
Why
overlay mounts are a must for agentic microvm usages, really do not want to risk any mess on the host.
How (optional)
Perhaps a -v hostpath:guestpath:overlay option, but I wonder if for safety and differentiation (from say docker) it should be the other way around maybe, ie:
-v hostpath:guestpath is the safe overlay-powered default in all cases.
and
-v hostpath:guestpath:host_fs (or similar name) to better convey to user the risk of mounting that way when actual sharing is actually needed.
Summary
Currently from CLI it seems we can only set up a "real fs" mountpoint (default) or a readonly mountpoint, not an "overlay" mount point.
This may be a surprising/risky default as the main README says:
Why
overlaymounts are a must for agentic microvm usages, really do not want to risk any mess on the host.How (optional)
Perhaps a
-v hostpath:guestpath:overlayoption, but I wonder if for safety and differentiation (from say docker) it should be the other way around maybe, ie:-v hostpath:guestpathis the safe overlay-powered default in all cases.and
-v hostpath:guestpath:host_fs(or similar name) to better convey to user the risk of mounting that way when actual sharing is actually needed.