Repository navigation
AviBackToBlack
Avi Back To Black
ContainerBin v2.0.0
Stable release adding the native WSL2 amd64 frontend with Docker Desktop integration while preserving native Windows functionality.
Source commit: 3cfc259f96c78a27dd417afd8dd8c64206c752ca, identical to the qualified v2.0.0-rc.2 source. Stable artifacts are built afresh by the repository release workflow with the stable version injected; RC assets and tags are not moved or replaced.
Highlights
- Native WSL2 managed-tool execution in normal user distributions: piped stdin/EOF, separate stdout/stderr, terminal sizing and resize, interrupt forwarding, exact tool exit codes, and proof-bound crash cleanup.
- Persistent, isolated WSL project state and shared caches without adopting native Windows state. Mixed-storage, external/symlink boundaries, literal Windows path spellings and unsafe mount roots fail closed.
- Fix pipx launcher-cache interpreter alias normalization while retaining exact approved-target validation. Regression coverage includes traversal order and invalid aliases.
- Deterministic Windows amd64/ARM64 and Linux amd64 bundles, independent byte-for-byte reproduction, checksum manifests and GitHub-hosted build provenance. The existing three-entry Windows checksum contract is preserved.
Qualification
The exact RC.2 source passed Windows 11 x64 with Docker Desktop 4.94.0 / Engine 29.8.2 and 4.93.0 / Engine 29.8.1, in Windows PowerShell 5.1, PowerShell 7.x and cmd.exe: six cells, 90 self-test checks, zero failures/skips. Previous-stable testing also passed pip/requests, Terraform validation and complete pinned pipx exposure cycles in every shell. No Docker-version waiver was used.
WSL2 qualification covered distribution-local and default Windows-backed storage, real PTY/resize/signals, state persistence/isolation, rejected paths and controlled crash recovery. Cleanup ended with zero active/orphan containers or lease residue; pre-existing native Windows volumes were preserved. The published self-update harness verifies candidate-source code with an injected prior version, not the historical v1.1.0 implementation.
Before stable publication, the exact freshly built v2.0.0 artifacts additionally passed all three current-Docker Windows shell cells (45 checks, zero failures/skips), pipx install/exposure/invocation/cleanup and the full WSL runtime corpus on both storage modes. Stable WSL cleanup ended with zero active/orphan containers or lease residue; all 62 pre-existing native Windows managed volumes were preserved.
After publication, isolated self-update to the exact stable release passed checksum/provenance verification, helper handoff, transactional replacement, version smoke, shim reconciliation and zero private-artifact residue. Default stable-channel selection resolves to v2.0.0. Stable artifact hashes and complete verification evidence.
Upgrade notes and support boundaries
Existing registries embed their pipx wrapper. Updating the binary or running install does not silently rewrite a customized/signed [tools.pipx] profile. Back up the registry and explicitly refresh only that profile from a fresh v2.0.0 default registry, preserving deliberate customizations; signed registries require administrator re-signing. Do not delete persistent pipx state as a workaround.
The pinned Python cowsay==6.1 example requires cowsay -t "hello from pipx"; the README's positional-text pipx example is a known documentation issue. This does not affect the separate npm cowsay CLI. A restricted inherited PowerShell module path can make the diagnostic ACL probe indeterminate; this is reported as a warning, not successful permission verification. Permanent installations should use a private, appropriately permissioned shim directory.
The Linux archive supports the native WSL2 amd64 frontend, not standalone Linux/macOS. Docker Desktop private distributions are not supported. Windows ARM64 binaries have native CI/build/provenance coverage but not real ARM64 Docker Desktop end-to-end qualification. Authenticode provisioning remains outside this release; GitHub build provenance is provided. Do not treat these artifacts as broader platform support claims.