HUB
Sign inSign up
scout-cli logo

sbx/scout-cli

Verified Publisher

By Docker, Inc

•Updated about 5 hours ago

Docker Scout CLI plugin that signs in to Scout with the host's sbx login.

Sandbox Kit
0

971

sbx/scout-cli repository overview

Digest

sha256:e6fac169c567…

Size

50.2 MB

Schema

v3

Pushed

about 5 hours ago

Specificationspec.yaml

MIXIN

Docker Scout CLI plugin that signs in to Scout with the host's sbx login.


Arguments
NameRequiredDefaultDescription
versionRequired—

Docker Scout CLI release carried by the overlay



CapabilitiesExpand a row to see its full configuration. See the full spec for the complete descriptor.
TypeRequiredDescription
com.docker.sandbox/credential@1RequiredDocker Scout API access through the host's sbx login
com.docker.sandbox/network-policy@1Required—
com.docker.sandbox/agent-context@1Optional—
com.docker.sandbox/agent-context@2Optional—

Apply this mixin to a sandbox

sbx run <agent> --kit sbx/scout-cli:latest

Make sure you have docker sbx installed

Run the following command to install sbx on your machine.

macOS
brew install docker/tap/sbx
Windows
winget install Docker.sbx
Learn more about docker sbx⁠

⁠Docker Scout for Docker Sandboxes

This mixin Kit adds the Docker Scout⁠ CLI to a compatible workload and signs it in to Docker Scout with the login of the host's sbx session. It keeps the workload's launch command.

This Kit is built on Docker Hardened Images.

⁠Use

Add --kit sbx/scout-cli:latest when creating a sandbox with a workload such as Shell⁠. Inside the sandbox, run docker scout version, docker scout quickview, or docker scout cves.

The Kit installs Scout as a Docker CLI plugin at /home/agent/.docker/cli-plugins/docker-scout, so docker scout uses the workload's Docker CLI. A launcher at /home/agent/.local/bin/docker-scout runs the same binary on a workload that has no Docker CLI.

⁠Authentication and access

Log in on the host with sbx login. Inside the sandbox, DOCKER_SCOUT_HUB_TOKEN is a proxy-managed sentinel. The proxy injects the host's current login token on requests to api.scout.docker.com and api.dso.docker.com. Do not print or copy the token, and do not run docker login to sign in to Scout. The Kit never puts a real credential in its image layers.

Runtime access covers those two Scout API hosts only. Scanning an image in a registry also requires network access and credentials for that registry; configure them separately. Scanning an existing SBOM file with docker scout cves sbom://<path> needs neither.

⁠References

See the Sandbox Kit v3 specification⁠, Docker Scout documentation⁠, Docker Sandboxes documentation⁠, and Docker Hardened Images documentation⁠.