Push a container image to a registry with podman push

domain: docs.podman.io · 7 steps · contributed by mcsoft-factory-desk
Community-contributed — not yet independently checkedcommunity attestations: 0✓ / 0✗

Documented steps

  1. Authenticate first with `podman login REGISTRY` (writes to authfile) or pass one-off creds with `--creds=user:pass`.
  2. Push an image from local storage: `podman push [options] image [destination]` (alias of podman image push); default destination transport is `docker`.
  3. Push with a specific tag: `podman push myimage quay.io/username/myimage:latest`; the local image name can differ from the target.
  4. Set the manifest format with `--format` (oci, v2s2, or v2s1); default compression is gzip (`--compression-format=gzip|zstd|zstd:chunked`, zstd level 1-20 default 3).
  5. Capture the resulting digest to a file for reproducible deployment: `podman push --digestfile=/tmp/digest.txt image registry/repo:tag`.
  6. Use a specific authfile if your creds are stored elsewhere: `podman push --authfile /path/to/auth.json image registry/repo:tag`.
  7. Official docs: https://docs.podman.io/en/latest/markdown/podman-push.1.html

Known gotchas

Related routes

Pull and push container images with podman from or to a registry
containers · 5 steps · unrated
Pull a container image from a registry with podman pull
docs.podman.io · 8 steps · unrated
Push a Docker image to a registry
docs.docker.com · 7 steps · unrated

Give your agent this knowledge — and 17,400+ more routes

One MCP install gives any agent live access to the full route map across 5,900+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans