boxlite-cli currently does not expose the RootfsPath capability that already exists in the core runtime / REST layer. Today, boxlite run
and boxlite create only accept an image reference and always go through RootfsSpec::Image, with no CLI option like --rootfs or --bundle.
This is limiting for a few practical use cases:
- Running from a pre-exported local OCI bundle in offline / air-gapped environments
- Reusing images that were prepared ahead of time, without requiring a registry pull at runtime
- Testing custom or locally built root filesystems
- Using BoxLite in environments where registry access is slow, restricted, or undesirable
It would be useful if the CLI could expose this directly, for example with something like:
boxlite run --rootfs /path/to/rootfs-or-oci-bundle ...
boxlite create --rootfs /path/to/rootfs-or-oci-bundle
This would make the CLI consistent with the runtime capabilities and improve offline/local-image workflows significantly.
boxlite-clicurrently does not expose theRootfsPathcapability that already exists in the core runtime / REST layer. Today,boxlite runand
boxlite createonly accept an image reference and always go throughRootfsSpec::Image, with no CLI option like--rootfsor--bundle.This is limiting for a few practical use cases:
It would be useful if the CLI could expose this directly, for example with something like:
This would make the CLI consistent with the runtime capabilities and improve offline/local-image workflows significantly.