Repository navigation
Fixes for Lima hosts reached over ssh, and for running the test suite in a terminal. Also adds an experimental OpenShell backend. No upgrade steps beyond the usual boxery upgrade-host.
Fixes
- Lima on a remote Mac with Node from fnm or nvm.
boxery newfailed with onlylimactl start … failed, because the Lima backend ran barenode, which isn't onPATHin the non-interactive ssh session the controller uses. Backend scripts now always use the host's own Node, the oneinitrecorded (#146, #158, fixes #143). - Lima on a remote Mac with Homebrew. Over non-interactive ssh,
limactlfrom/opt/homebrew/binwasn't found, andboxery newwrongly reportedno base image; run: boxery-host build-base. On macOS, backend calls (and the sshProxyCommand) now add/opt/homebrew/bin:/usr/local/binto the end ofPATH. If a backend can't tell whether the base exists, it now says why, instead of reporting that the base is missing (#157). - The Lima ssh port with
FORCE_COLORset. The free-port helper printed the port withconsole.log, which wraps it in colour codes whenFORCE_COLORis set. The port was then rejected, and a confined Lima start failed withno free port. This also madenpm test(and sonpm publish) fail when run in a terminal, since the test runner setsFORCE_COLORthere (#156).
New: OpenShell backend (experimental)
boxery can now drive headless sandboxes on an OpenShell gateway, where OpenShell's policy limits what each sandbox can read and reach on the network (#152, #153):
boxery setup local --backend openshell
boxery --host restricted new demo --headlessIt supports the shell, file, copy and background-job tools. Desktops, snapshots, forks, resize, pools and boxery grants aren't supported and are refused with an error. OpenShell manages credentials and network access itself. It has been tested on Linux only. See docs/openshell.md.
Upgrading
boxery upgrade-host, then update the controllers. The image layers haven't changed since 0.10.0, so desktop bases and existing VMs don't need a rebuild or a patch.