c6090c290e
New functionality in hack/man-page-checker: start cross- referencing the man page 'Synopsis' line against the output of 'podman foo --help'. This is part 1, flag/option consistency. Part 2 (arg consistency) is too big and will have to wait for later. flag/option consistency means: if 'podman foo --help' includes the string '[flags]' in the Usage message, make sure the man page includes '[*options*]' in its Synopsis line, and vice-versa. This found several inconsistencies, which I've fixed. While doing this I realized that Cobra automatically includes a 'Flags:' subsection in its --help output for all subcommands that have defined flags. This is great - it lets us cross-check against the usage synopsis, and make sure that '[flags]' is present or absent as needed, without fear of human screwups. If a flag-less subcommand ever gets extended with flags, but the developer forgets to add '[flags]' and remove DisableFlagsInUseLine, we now have a test that will catch that. (This, too, caught two instances which I fixed). I don't actually know if the new man-page-checker functionality will work in CI: I vaguely recall that it might run before 'make podman' does; and also vaguely recall that some steps were taken to remedy that. Signed-off-by: Ed Santiago <santiago@redhat.com>
2.3 KiB
% podman-manifest-push(1)
NAME
podman-manifest-push - Push a manifest list or image index to a registry
SYNOPSIS
podman manifest push [options] listnameorindexname transport:details
DESCRIPTION
Pushes a manifest list or image index to a registry.
RETURN VALUE
The list image's ID and the digest of the image's manifest.
OPTIONS
--all
Push the images mentioned in the manifest list or image index, in addition to the list or index itself.
--authfile=path
Path of the authentication file. Default is ${XDG_RUNTIME_DIR}/containers/auth.json, which is set using podman login.
If the authorization state is not found there, $HOME/.docker/config.json is checked, which is set using docker login. (Not available for remote commands)
Note: You can also override the default path of the authentication file by setting the REGISTRY_AUTH_FILE
environment variable. export REGISTRY_AUTH_FILE=path
--cert-dir=path
Use certificates at path (*.crt, *.cert, *.key) to connect to the registry. Default certificates directory is /etc/containers/certs.d. (Not available for remote commands)
--creds=creds
The [username[:password]] to use to authenticate with the registry if required. If one or both values are not supplied, a command line prompt will appear and the value can be entered. The password is entered without echo.
--digestfile=Digestfile
After copying the image, write the digest of the resulting image to the file.
--format, -f=format
Manifest list type (oci or v2s2) to use when pushing the list (default is oci).
--purge
Delete the manifest list or image index from local storage if pushing succeeds.
--quiet, -q
When writing the manifest, suppress progress output
--remove-signatures
Don't copy signatures when pushing images.
--sign-by=fingerprint
Sign the pushed images using the GPG key that matches the specified fingerprint.
--tls-verify
Require HTTPS and verify certificates when talking to container registries (defaults to true) (Not available for remote commands)
EXAMPLE
podman manifest push mylist:v1.11 docker://registry.example.org/mylist:v1.11
SEE ALSO
podman(1), podman-manifest(1), podman-manifest-add(1), podman-manifest-create(1), podman-manifest-inspect(1), podman-manifest-remove(1), podman-rmi(1)