github docker/sbx-releases v0.54.0

one hour ago

0.54.0

Highlights

Docker Sandboxes v0.54.0 adds dedicated port management commands and a TLS compatibility setting for networks that block post-quantum key exchange. It also strengthens generated SSH configuration and clone-mode Git access, improves cloud sandbox creation, and makes CLI errors and output more consistent.

Breaking changes and upgrade actions

Refresh generated SSH configuration

Generated SSH configuration prevents crafted host or user names from executing shell commands with older OpenSSH clients. After upgrading, rerun sbx setup ssh for local connections and sbx --cloud setup ssh for cloud connections to update existing configuration.

Storage paths when running as root

On Unix, running sbx as root uses root's registered home directory and the default storage, credential, and daemon endpoint locations. Inherited overrides, including HOME, XDG_CONFIG_HOME, XDG_STATE_HOME, XDG_CACHE_HOME, SANDBOXES_STORAGE_ROOT, and DOCKER_SANDBOXES_API, are ignored. Ordinary users retain their existing paths and environment overrides.

Before upgrading, stop any older root daemon that uses custom storage. The custom storage data is left untouched.

Clone-mode Git remote transport

Fetching from a clone-mode sandbox's sandbox-<name> Git remote now uses the daemon socket, restricted to your host user, instead of an unauthenticated localhost TCP port. Starting the sandbox refreshes its remote configuration. Fetching requires the sandbox to be running.

For Git clients that ignore the remote's uploadpack setting, enable TCP compatibility with sbx settings set clone.legacyTcpRemote true. This takes effect the next time the sandbox starts and exposes the repository and its history to other local accounts on the host. Leave the setting disabled to use the daemon socket. Clone-mode sandboxes using the default transport reject publishing sandbox TCP port 9418.

What's new

Port management

Use dedicated subcommands to manage ports on local and cloud sandboxes:

  • sbx port ls <SANDBOX> lists published ports.
  • sbx port publish <SANDBOX> <HOST_PORT>:<SANDBOX_PORT> publishes a port. Omit the host port to assign one automatically.
  • sbx port unpublish <SANDBOX> <SANDBOX_PORT> removes all host mappings for that sandbox port. Specify <HOST_PORT>:<SANDBOX_PORT> to remove a single mapping.

The legacy sbx ports command still works but is deprecated.

Networking and policy

  • Set tls.postQuantumKeyExchange to false if a firewall or TLS-inspecting proxy drops or stalls Sandboxes HTTPS connections because it cannot handle post-quantum key exchange. Run sbx settings set tls.postQuantumKeyExchange false, then sbx daemon restart. The setting defaults to true; restore it and restart the daemon to re-enable post-quantum key exchange.
  • sbx policy check network names the rule that allowed a target. Policy checks explain when further evaluation is needed and how to check a specific HTTP request.
  • sbx policy --help explains hostname-blocking limitations when an allowed and denied host share an IP address.
  • SSH reverse port forwarding no longer consumes a CPU core after its input socket is half-closed.

Sandbox lifecycle, kits, and agents

  • sbx run no longer fails with “network already exists” after an earlier start failed partway.
  • When a saved mount's source resolves to a different directory, startup refuses the mount. Remove it with sbx umount, then mount the intended directory again.
  • Kit installation failures preserve command diagnostics and report network denials observed during installation.
  • Image cleanup preserves assembled images referenced by saved kit locks or containers.
  • Kit validation checks inherited configuration and reports inherited warnings.
  • Existing kit permissions may require confirmation again after upgrading because permission checks use stronger service digests.
  • Reattaching to a Kiro or Cursor sandbox relaunches the agent with the command used by its published kit.

Authentication and MCP

  • sbx login reports failure with diagnostic steps when it cannot reach Docker's sign-in service after browser sign-in. Settings errors suggest signing in when administrator settings are unavailable.
  • OAuth secret sign-in respects --no-input instead of opening browser authorization.
  • Declining secret replacement or environment removal cancels the command with a nonzero exit status.
  • sbx inspect shows a local sandbox's static or dynamic MCP mode and connected servers. These describe the sandbox gateway; use sbx mcp ls to list host registrations.
  • Loading an MCP server into a cloud sandbox prints a success acknowledgment.

Cloud sandboxes

  • Creating a sandbox honors the requested architecture when combining published kits with locally built mixins.
  • A kit's network allow list no longer replaces the account's network policy when neither --allow-network nor --deny-network is supplied.
  • Cloud creation rejects TTL values outside 15 seconds to 24 hours, explicitly empty timeout actions, and explicitly empty sandbox names before provisioning.
  • Declining a sandbox move cancels it with a nonzero exit status. An explicitly empty destination name is rejected before work starts.
  • Cloud API connection failures behind HTTP proxies report that the API is unreachable and suggest sbx --cloud diagnose, instead of returning a generic 500 error.
  • File copies distinguish failed path checks from missing source paths.
  • Cloud exec rejects --detach-keys, matching local exec. Omit this flag for both sbx exec and sbx env exec.
  • Scheduled runs accept --workdir and -w. Schedule durations accept case-insensitive units.
  • Help clarifies cloud template selection, inherited sizing, incompatible launch options, and the supported cloud SSH setup workflow.

CLI and diagnostics

  • sbx diagnose --format json and --format yaml include a stable id for each check. Match checks by id in scripts; name is display text that can change.
  • Diagnostic bundles use unique output files so existing workspace links cannot cause other host files to be overwritten.
  • MCP progress, warnings, client-secret guidance, and secret-list diagnostics go to stderr, preserving stdout for command results.
  • Sandbox and kit inspection report output write failures instead of succeeding silently.
  • Cloud-only commands report the required mode without starting a local daemon.
  • Installed skills can be removed with the sbx skills delete alias.
  • Argument validation, shell completion, and secret-removal help more consistently reflect supported options. Kit signing rejects conflicting credential sources, and kit push rejects signing options unless signing is enabled.

Don't miss a new sbx-releases release

NewReleases is sending notifications on new releases.