ContainerStack 0.4.2
Immutable
release. Only release title and notes can be modified.
ContainerStack now owns a Docker socket separate from a standalone Socktainer
installation. Upgrading moves the app and its Docker context without stopping or
removing a bridge you run yourself.
Changed
- The app,
cstack, Docker context, and verification tools now use
~/.containerstack/docker.sockinstead of~/.socktainer/container.sock.
An activecontainerstackDocker context is refreshed during the upgrade. If
you setDOCKER_HOSTyourself, update it to the new path. - The bundled bridge explicitly owns startup housekeeping for the shared Apple
Container runtime. Homebrew cleanup removes only ContainerStack's state and
no longer treats~/.socktaineras app-owned data.
Fixed
- Upgrading retires the old bundled bridge before starting its replacement. The
migration matches both the exact helper path inside ContainerStack.app and the
old argument list, waits for that process to exit, and aborts safely if it
cannot confirm retirement. A standalone Socktainer process is left running.
Known limitations
Published ports still require a runtime restart if a bridge-created network's
vmnet helper dies; restarting only the containers does not repair the host route.
The per-container micro-VM architecture also remains slower than OrbStack on the
measured M1 system (4.6x container round trip, 3.6x bind-mount writes).