dhi.io/telepresence
Telepresence
Telepresence connects a local development machine to a remote Kubernetes cluster, so you can run and debug one service locally while it talks to the rest of the cluster. This image is the client, used as the daemon container for telepresence connect --docker.
pushed 6 hours ago
linux/amd64, linux/arm64
31.94 MB
for linux/amd64
204
for linux/amd64
Active support
-
Build Level 3
Tamper-evident proof of how and from what sources this image was built. Build Level 3 is the highest the SLSA build track defines.
CycloneDX SBOM + SPDX SBOM
A software bill of materials in both CycloneDX and SPDX formats so it drops straight into your existing tooling. Audit exactly what you're shipping.
A Vulnerability Exploitability exchange document, Docker's assessment of which CVEs actually affect this image and which don't apply, so you can focus on real risk instead of chasing false positives.
Available
A link to everything used to build the image, package source code, Git repos, and build files, so you can audit or reproduce the build and stay compliant with open source licenses.
Every known vulnerability in this image, shown in full rather than hidden. The VEX data flags which ones actually apply, so you can tell real exposure from noise before you ship.
-
Exactly what changed in this build, down to the package bumps and fixes behind the version you're pulling.
Verifies no keys, tokens, or credentials were accidentally baked into the image.
The image layers were scanned for known malware signatures before publishing.
About Telepresence
Telepresence is a Cloud Native Computing Foundation (CNCF) project that connects a developer workstation to a remote Kubernetes cluster. You can run and debug one service locally with your own tools while it receives real traffic from the cluster, without a container build, push, and deploy cycle. The project is published at https://telepresence.ioā .
This Docker Hardened Image is the Telepresence client image. The telepresence connect --docker command starts it as
the daemon container on the host, and it also runs the telepresence CLI. It is the hardened stand-in for the upstream
image ghcr.io/telepresenceio/telepresence. It does not contain the cluster-side traffic manager or traffic agent.
About Docker Hardened Images
Docker Hardened Images are built to meet the highest security and compliance standards. They provide a trusted foundation for containerized workloads by incorporating security best practices from the start.
Why use Docker Hardened Images?
These images are published with near-zero known CVEs, include signed provenance, and come with a complete Software Bill of Materials (SBOM) and VEX metadata. They're designed to secure your software supply chain while fitting seamlessly into existing Docker workflows.
Trademarks
Telepresenceā¢ is a trademark of the Linux Foundation. All rights in the mark are reserved to the Linux Foundation. Any use by Docker is for referential purposes only and does not indicate sponsorship, endorsement, or affiliation.
KubernetesĀ® is a registered trademark of The Linux Foundation. Any use by Docker is for referential purposes only and does not indicate sponsorship, endorsement, or affiliation.