readystack/virtexportproxy repository overview

⁠virt-exportproxy

readystack/virtexportproxy:v1.9.1-CE-debian12-r1

Source, recipe and records

• Source and build recipe: https://readystack.dev/products/virtexportproxy/recipe⁠
• Upstream source at this release's pinned commit (v1.9.1): https://github.com/kubevirt/kubevirt/tree/c3d19093f9c7b843b3879b18dc088911c081c39e⁠
• Product page: https://readystack.dev/products/virtexportproxy⁠
• Hermetic Build Kit for this release (free with an account): https://readystack.dev/products/virtexportproxy⁠
• Release history (JSON): https://readystack.dev/api/releases/virtexportproxy⁠
• Defect record: https://readystack.dev/defects.html?product=virtexportproxy⁠
• Today's scan: https://readystack.dev/products/virtexportproxy#pp-grade⁠
• Report an issue: https://github.com/ReadyStackFree/readystack/issues/new?template=bug.yml&product=virtexportproxy⁠
• Signing key (cosign): https://readystack.dev/keys/cosign.pub⁠
• Part of the Kubernetes VM Stack: https://readystack.dev/stacks/kubernetes-vm-stack⁠

A cosign-signed build of KubeVirt v1.9.1 (github.com/kubevirt/kubevirt, commit c3d19093f9c7), Apache-2.0, built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: Cluster administrators who move KubeVirt virtual machines and their disks out of a cluster.

Why: virt-exportproxy is KubeVirt's export proxy. Virtual machine exports are downloaded through it, a dedicated server, so large disk transfers do not load the Kubernetes API server.

Use case: An administrator wants to move a virtual machine into another cluster or system. They create an export for the VM, then download its disk images through the export proxy, which can be reached from outside the cluster through an Ingress or a NodePort service.

About the upstream project, written from its own description: https://kubevirt.io/user-guide/storage/export_api/⁠ · https://github.com/kubevirt/kubevirt⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:6c3f06ae061e8d706757d2635c479b1b012f6876fceecd18479b832f2f872656 on 2026-10-29.

• Scan scores — we scan every image we publish every day (an SBOM made with syft, vulnerabilities matched with grype, scored with cerodeo-v1, the rubric ce.rodeo published until 2026-10-26) and record each scan with how its score was derived. This release's first and latest scan: https://readystack.dev/products/virtexportproxy⁠
• ReadyStack release check — passed at release on 2026-10-29: no fixable critical or high vulnerability (Docker Scout and OSV), a non-root user, SBOM and provenance attached. This is ReadyStack's own test, not a Docker grade; vulnerabilities published since then are in today's result at https://readystack.dev/queue⁠.
• Signed — cosign signature by the ReadyStack release key (fingerprint 04daa92344a52dbc) on this release's index digest sha256:6c3f06ae061e8d706757d2635c479b1b012f6876fceecd18479b832f2f872656; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/virtexportproxy:v1.9.1-CE-debian12-r1.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (1001).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is v1.9.1-CE-debian12-r1 — the release listed at readystack.dev. Release tags use the pattern <upstream-version>-CE-<base-os>-r<N>; the current one is signed, attested (SBOM + provenance), and is provided under the ReadyStack Agreement⁠.

• Earlier release tags (an older version or revision in the same pattern) are superseded. They stay pullable so existing deployments can pin them, but they are no longer re-graded, and fixes appear only in newer releases: move to the current release. For a superseded release's build kit, ask support.

• Release tags never move, so pulling the same tag again never changes the image. To be offered each new release automatically (a new revision r<N+1>, or a new upstream version), use the ReadyStack Renovate preset: https://readystack.dev/updates.html⁠

• Any tag beginning with internal- is an engineering-pipeline artifact published for build observability. It is unsupported, may change or disappear without notice, and must not be used in production.

# ✓ current release
docker pull readystack/virtexportproxy:v1.9.1-CE-debian12-r1

# ✗ unsupported (do not pull)
docker pull readystack/virtexportproxy:internal-...

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/virtexportproxy:v1.9.1-CE-debian12-r1 (the signature is recorded in the public Sigstore transparency log). Support: [email protected]⁠, as set out in the ReadyStack Agreement⁠.

⁠Deployment

the export proxy: it serves VirtualMachineExport downloads (disk images, manifests) from outside the cluster over TLS, on paths of the form /api/export.kubevirt.io/v1beta1/namespaces//virtualmachineexports//. virt-operator v1.9.1 deploys it unconditionally and reports KubeVirt Available only once it runs, so the stack ships it even though nothing in the stack exports a VM. virt-exportserver, which serves one export, starts only when a VirtualMachineExport is created and is not part of the stack.

This image runs only inside a Kubernetes cluster, started by its stack's manifests (the admin guide shows how); started on its own it exits. Its one-run check, which VERIFY_OFFLINE.sh also runs: docker run --rm --network none readystack/virtexportproxy:v1.9.1-CE-debian12-r1 --help prints --listen.

⁠The full ReadyStack Hermetic Build Kit

The complete --network=none build kit for this image — plus admin/DB/API handbooks, the build's validation records, and its build provenance records — is a free download for any registered account at readystack.dev/products/virtexportproxy⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:3bb06b5880899bf2955da20fb6c47810f0a863a9057c0c9ec13f61a3a624322b on 2026-10-29.

— ReadyStack · readystack.dev