OPopenshift
Image

Push an image

Changed on

Push an image to a registry.

If you wish to push an image on to a private registry, that image must already have a tag which references the registry. For example, registry.example.com/myimage:latest.

The push is cancelled if the HTTP connection is closed.

post/images/{name}/push

Request

  • Base URL
    /v1.49 (relative, and the document was published on a file host, not at the API’s origin)
  • URL
    /v1.49/images/{name}/push
  • Auth
    none declared. Required headers: X-Registry-Auth

Path parameters

namestring required

Name of the image to push. For example, registry.example.com/myimage. The image must be present in the local image store with the same name.

The name should be provided without tag; if a tag is provided, it is ignored. For example, registry.example.com/myimage:latest is considered equivalent to registry.example.com/myimage.

Use the tag parameter to specify the tag to push.

Query parameters

tagstring

Tag of the image to push. For example, latest. If no tag is provided, all tags of the given image that are present in the local image store are pushed.

platformstring

JSON-encoded OCI platform to select the platform-variant to push. If not provided, all available variants will attempt to be pushed.

If the daemon provides a multi-platform image store, this selects the platform-variant to push to the registry. If the image is a single-platform image, or if the multi-platform image does not provide a variant matching the given platform, an error is returned.

Example: {"os": "linux", "architecture": "arm", "variant": "v5"}

Headers

X-Registry-Authstring required

A base64url-encoded auth configuration.

Refer to the authentication section for details.

Response

No error

Changes