OC-IMAGE-SERVE(1)

📦 version 4.19.0, in nixos 26.05

✨ oc image serve(1) ✨

okay bestie, buckle up 💖 this one is from the OpenShift CLI User Manuals — oc image serve, the June 2016 edition, ported from the Kubernetes man-doc generator. Let's get into it 🎀

🌸 NAME 🌸

oc image serve — serve a container registry straight from images you've mirrored to disk. yes. a whole registry. on your laptop. iconic 👑

🦋 SYNOPSIS 🦋

oc image serve [OPTIONS]

💅 DESCRIPTION 💅

okay so this command serves a container registry. literally that's the whole vibe.

It starts up an HTTP or HTTPS server that hosts a local directory full of mirrored images 🫶. To fill that directory up, you use:

oc image mirror --dir=DIR SRC=DST

and the directory must have a v2 folder that contains repository sub directories. no v2 folder, no slay 💀.

🚨 big warning bestie: no authentication or authorization checks are performed — none, zero, nada. So the source directory should only include content you actually want network users to see. like, fr fr. don't put your secrets in there 🙈.

Experimental: this command is under active development and may change without notice. so... vibe check it before you depend on it 😭

✨ OPTIONS ✨

  • --dir="" — the directory to serve images from 💖
  • --listen=":5000" — a host:port to listen on. defaults to *:5000 🎀
  • --tls-crt="" — path to a TLS certificate to secure this server with 🔒
  • --tls-key="" — path to a TLS private key to secure this server with 🔑

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

these are the hand-me-downs from the parent command, and honestly they ate 👑

  • --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
  • --cache-dir="/homeless-shelter/.kube/cache" — default cache directory 🗂️
  • --certificate-authority="" — path to a cert file for the certificate authority
  • --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 😬 (like, actually insecure, not in a cute way)
  • --kubeconfig="" — path to the kubeconfig file to use for CLI requests
  • --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 💀

🎀 SEE ALSO 🎀

🧚 HISTORY 🧚

June 2016 — ported from the Kubernetes man-doc generator. vintage, honestly 🦋

and that's the whole page, bestie 💜 written under Openshift for the Openshift CLI User Manuals, version-flavored OC IMAGE(1), dated June 2016 — go serve that registry, you absolute main character 🌟💅

📦 where this page comes from