Share feedback
Answers are generated based on the documentation.

sbx port unpublish

DescriptionUnpublish ports
Usagesbx port unpublish SANDBOX SPEC... [flags]

Description

Unpublish sandbox ports from the host.

A SPEC is [[HOST_IP:]HOST_PORT:]SANDBOX_PORT[/PROTOCOL]. If HOST_IP is omitted, the port is bound on loopback, expanded based on PROTOCOL and the sandbox's address families: tcp/udp binds both 127.0.0.1 and ::1 (or only 127.0.0.1 if the sandbox is IPv4-only); tcp4/udp4 binds only 127.0.0.1; tcp6/udp6 binds only ::1. Supported protocols: tcp, tcp4, tcp6, udp, udp4, udp6.

When unpublishing without a HOST_PORT, mappings matching HOST_IP and PROTOCOL are removed from every host port.

When unpublishing without a PROTOCOL, the mapping is removed whether it was published with that same default or as dual-stack tcp. Name the protocol to remove a tcp6 or udp mapping; anything left behind is reported.

With --cloud: Remove exposed ports from a cloud sandbox given by ID (sbx_*) or name.

A SPEC is the sandbox port number alone or with a /tcp suffix; UDP and host bindings are refused.

Options

OptionDefaultDescription
--formatOutput format: table, json or yaml
--jsonOutput in JSON format

Global options

OptionDefaultDescription
--cloudDispatch to Docker Cloud Sandboxes API instead of local sandboxd (supported by a growing set of verbs — run 'sbx --cloud --help' for the current list)
-D, --debugEnable debug logging
--no-inputNever prompt; commands that need an answer fail with the command to run instead

Examples

# Unpublish a port
sbx port unpublish my-sandbox 3000:8080

# Unpublish a sandbox port from every host port
sbx port unpublish my-sandbox 8080

# Remove an exposed port from a cloud sandbox
sbx --cloud port unpublish sbx_abc123 8080