Skip to main content
Pushes an image to a registry. The flags mirror those for image pull with the addition of specifying a platform for multi-platform images.

Usage

container image push [--scheme <scheme>] [--progress <type>] [--arch <arch>] [--os <os>] [--platform <platform>] [--debug] <reference>

Arguments

reference
string
required
Image reference to push

Options

--scheme
string
default:"auto"
Scheme to use when connecting to the container registry. One of (http, https, auto)When auto is selected, the target registry is considered internal/local if the registry host matches any of these criteria:
  • The host is a loopback address (e.g., localhost, 127.*)
  • The host is within the RFC1918 private IP ranges: 10.*.*.*, 192.168.*.*, 172.16.*.* through 172.31.*.*
  • The host ends with the machine’s default container DNS domain
For internal/local registries, the client uses HTTP. Otherwise, it uses HTTPS.
--progress
string
default:"ansi"
Progress type (format: none|ansi)
-a, --arch
string
Limit the push to the specified architecture
--os
string
Limit the push to the specified OS
--platform
string
Limit the push to the specified platform (format: os/arch[/variant], takes precedence over —os and —arch)

Build docs developers (and LLMs) love