Push Images

Users can push images (manifests and manifest lists) to repositories hosted by the Container Registry. It is possible to push images that container foreign (non-distributable) layers. Only the users who are logged in to the registry are allowed to perform push operation. Find below a complete example of pushing a tagged image.

Note

Having disabled the token authentication, only users with superuser privileges (i.e., administrators) are allowed to push content to the registry.

The registry supports cross repository blob mounting. When uploading blobs that already exist in the registry as a part of a different repository, the content is not being uploaded but rather referenced from another repository to reduce network traffic.

podman tag d21d863f69b5 localhost:24817/test/this:mytag1.8
podman login -u user -p password localhost:24817
podman push d21d863f69b5 localhost:24817/test/this:mytag1.8

http GET $BASE_ADDR/v2/test/this/tags/list

HTTP/1.1 200 OK
Allow: GET, HEAD, OPTIONS
Connection: close
Content-Length: 40
Content-Type: application/json
Date: Wed, 03 Jun 2020 18:25:46 GMT
Docker-Distribution-API-Version: registry/2.0
Server: gunicorn/20.0.4
Vary: Accept
X-Frame-Options: SAMEORIGIN

{
    "name": "test/this",
    "tags": [
        "mytag1.8"
    ]
}

Note

New registry pushes create a regular ContainerRepository. Older deployments may still have legacy ContainerPushRepository instances. A push repository does not support mirroring of remote content via the Pulp API. Trying to push content with the same name as an existing "regular" repository will fail.

Note

Rollback to the previous repository versions is not possible with a push repository. Its latest version will always be served.

Migrating legacy push repositories

Legacy push repositories can be converted to regular container repositories with the migrate action. Migration changes the repository type in place: the repository primary key, name, metadata, content, version history, and distribution association are preserved. Registry paths and tags stay the same. The repository href path changes from container-push to container; the converted repository is returned in the task result.

http POST $BASE_ADDR/pulp/api/v3/repositories/container/container-push/$PUSH_REPO_PK/migrate/

After migration, the repository is listed under container repositories instead of push repositories. You can continue to push and pull through the same registry path, and you gain standard repository operations such as sync and version management.

Warning

Do not push or upload content to a repository while it is being migrated. In-flight blob uploads tied to the push repository can fail when the repository type changes.

Warning

Image that has been pulled from a registry and then subsequently pushed to another registy can lead to the blobs digest change. Most image layers on registries are compressed. Pull operation decompresses them to get an uncompressed stream, and extracts it to create the local filesystem. Push creates an uncompressed tarball from the local filesystem and recompresses it during upload. The recompression is not at all guaranteed to be reproducible, it is client implementation dependent — push with different compression implementation than the original author used is more likely to result in a different blob digest.