Tag and push

--tag is where the finished image goes. It is required, and you give at least one of --push or --output. Pushing uses your existing docker login or cloud IAM; the CLI adds no registry of its own.

# --tag is where the finished image goes; --push sends it there
fleetwide embed --app my-app --image ghcr.io/acme/my-app:1.4.2 --start latest \
  --tag ghcr.io/acme/my-app-fw:1.4.2 --push

# build the Dockerfile first and keep that build under a name you chose
fleetwide embed --app my-app --dockerfile ./Dockerfile --build-tag ghcr.io/acme/my-app:1.4.2 \
  --start latest --tag ghcr.io/acme/my-app-fw:1.4.2 --push

# air-gapped site: a docker-load tarball instead of a push (one platform)
fleetwide embed --app my-app --image ghcr.io/acme/my-app:1.4.2 --start embedded \
  --tag acme/my-app-fw:1.4.2 --output my-app.tar

With --dockerfile the CLI runs docker build first. --build-tag names that build and keeps it, which is what you want when the pre-embed image is also something you ship or cache. Without it the build gets a temporary tag that is removed once the embed has read it, so nothing accumulates in the daemon.

--platform takes several, comma separated, and pushes one multi-platform tag; --all-platforms covers every platform the source image has. Several platforms need --push: a tarball is one image, so name the platform you want with --output.

The image you pushed is what you publish as a release. Nothing else needs to know it came from the CLI.

← Install the CLI fleetwide embed →