OC-IMAGE-INFO(1)

πŸ“¦
version 4.22.0 Β· 2 versions
, in nixpkgs unstable

okay bestie, welcome to oc image info, aka the OC IMAGE(1) manual page. This is the command that shows you information about an image in a remote image registry, and by the end you're gonna know every flag. no cap. ✨

πŸ’… NAME πŸ’…

oc image info β€” display information about an image. periodt. πŸ‘‘

πŸ¦‹ SYNOPSIS πŸ¦‹

oc image info [OPTIONS]

✨ DESCRIPTION ✨

Okay so picture this: you want metadata about container images in a remote image registry. That's literally this command. You may specify images by tag or digest, and you can specify multiple at a time. iconic. πŸ’–

Images in manifest list format will be shown for your current operating system. Wanna see the image for a particular OS? Use the --filter-by-os=OS/ARCH flag. tiny caveat: when --filter-by-os is used against an image that is not in manifest list format, the --filter-by-os flag will be ignored. iykyk. πŸ™ˆ

✨ OPTIONS ✨

  • --certificate-authority="" β€” path to a certificate authority bundle to use when communicating with the managed container image registries. If --insecure is used, this flag will be ignored. 🫢
  • --dir="" β€” the directory on disk that file:// images will be read from.
  • --filter-by-os="" β€” a regular expression to control which images are considered when multiple variants are available. Images will be passed as '<platform>/<architecture>[/<variant>]'.
  • --icsp-file="" β€” path to an ImageContentSourcePolicy file. If set, data from this file will be used to find alternative locations for images. πŸ”₯
  • --insecure=false β€” allow push and pull operations to registries to be made over HTTP.
  • -o, --output="" β€” print the image in an alternative format: json.
  • -a, --registry-config="" β€” path to your registry credentials. Alternatively REGISTRY_AUTH_FILE env variable can be also specified. Defaults to ${XDG_RUNTIME_DIR}/containers/auth.json, /run/containers/${UID}/auth.json, ${XDG_CONFIG_HOME}/containers/auth.json, ${DOCKER_CONFIG}, /.docker/config.json, /.dockercfg. The order can be changed via the REGISTRY_AUTH_PREFERENCE env variable (deprecated) to a "docker" value to prioritizes Docker credentials over Podman's. πŸ’–
  • --show-multiarch=false β€” show information even if the image is a multiarch image. If not set, an error is thrown for multiarch images. 😭
  • --skip-verification=false β€” skip verifying the integrity of the retrieved content. This is not recommended, but may be necessary when importing images from older image registries. Only bypass verification if the registry is known to be trustworthy. 🚨

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

These came from the parent commands β€” they're still invited to the group chat. πŸ’…

  • --as="" β€” username to impersonate for the operation. User could be a regular user or a service account in a namespace. 🫢
  • --as-group=[] β€” group to impersonate for the operation; this flag can be repeated to specify multiple groups. 🌸
  • --as-uid="" β€” UID to impersonate for the operation.
  • --as-user-extra=[] β€” user extras to impersonate for the operation; this flag can be repeated to specify multiple values for the same key. ✨
  • --cache-dir="/homeless-shelter/.kube/cache" β€” default cache directory. πŸ’€
  • --client-certificate="" β€” path to a client certificate file for TLS.
  • --client-key="" β€” path to a client key file for TLS.
  • --cluster="" β€” the name of the kubeconfig cluster to use.
  • --context="" β€” the name of the kubeconfig context to use.
  • --disable-compression=false β€” if true, opt-out of response compression for all requests to the server.
  • --insecure-skip-tls-verify=false β€” if true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure. 🚨
  • --kubeconfig="" β€” path to the kubeconfig file to use for CLI requests.
  • --kuberc="" β€” path to the kuberc file to use for preferences. This can be disabled by exporting KUBECTL_KUBERC=false feature gate or turning off the feature KUBERC=off.
  • --match-server-version=false β€” require server version to match client version.
  • -n, --namespace="" β€” if present, the namespace scope for this CLI request.
  • --profile="none" β€” name of profile to capture. One of (none|cpu|heap|goroutine|threadcreate|block|mutex).
  • --profile-output="profile.pprof" β€” name of the file to write the profile to.
  • --request-timeout="0" β€” the length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. ⏳
  • -s, --server="" β€” the address and port of the Kubernetes API server.
  • --tls-server-name="" β€” server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used.
  • --token="" β€” bearer token for authentication to the API server.
  • --user="" β€” the name of the kubeconfig user to use.
  • --warnings-as-errors=false β€” treat warnings received from the server as errors and exit with a non-zero exit code.

πŸŽ€ EXAMPLE πŸŽ€

Copy-paste these, bestie β€” they're literally the examples: πŸ’–

# Show information about an image
oc image info quay.io/openshift/cli:latest

# Show information about images matching a wildcard
oc image info quay.io/openshift/cli:4.*

# Show information about a file mirrored to disk under DIR
oc image info --dir=DIR file://library/busybox:latest

# Select which image from a multi-OS image to show
oc image info library/busybox:latest --filter-by-os=linux/arm64

πŸ‘‘ SEE ALSO πŸ‘‘

oc-image(1), obviously β€” go give it a read too. 🫢

⭐ HISTORY ⭐

June 2016, Ported from the Kubernetes man-doc generator. 🧚


okay that's the whole lore, bestie 🫢 this page is from Openshift, under the Openshift CLI User Manuals, manual OC IMAGE(1), dated June 2016. mwah πŸ’‹

πŸ“¦ where this page comes from