https://deploy-preview-3155--ornate-narwhal-088216.netlify.app/chainguard/chainguard-images/features/Recent content in Chainguard Containers Features onHugo -- gohugo.ioen-USThu, 19 Dec 2024 08:49:15 +0000https://deploy-preview-3155--ornate-narwhal-088216.netlify.app/chainguard/chainguard-images/features/eol-gp-overview/Wed, 14 May 2025 08:49:31 +0000https://deploy-preview-3155--ornate-narwhal-088216.netlify.app/chainguard/chainguard-images/features/eol-gp-overview/Typically, specific versions of software receive updates on a schedule for a set amount of time. Eventually, though, every version of software will stop receiving support. When project maintainers stop providing updates, it’s known as the End-of-Life (EOL) stage. It’s recommended that when a software version reaches the EOL phase, users should migrate their projects to a later version, as EOL software is known to accumulate vulnerabilities. However, there are cases where an organization may want to continue using a container image after it has reached end-of-life.https://deploy-preview-3155--ornate-narwhal-088216.netlify.app/chainguard/chainguard-images/features/image-stigs/Thu, 13 Jun 2024 15:56:52 -0700https://deploy-preview-3155--ornate-narwhal-088216.netlify.app/chainguard/chainguard-images/features/image-stigs/The practice of using Security Technical Implementation Guides, or “STIGs,” to secure various technologies originated with the United States Department of Defense (DoD). If an organization uses a certain kind of software, say MySQL 8.0, they must ensure that their implementation of it meets the requirements of the associated Security Requirements Guides (SRG) in order to qualify as a vendor for the DoD. More recently, other compliance frameworks have begun acknowledging the value of STIGS, with some going so far as to require the use of STIGs in their guidelines.https://deploy-preview-3155--ornate-narwhal-088216.netlify.app/chainguard/chainguard-images/features/request-resources/Thu, 26 Feb 2026 11:07:52 +0200https://deploy-preview-3155--ornate-narwhal-088216.netlify.app/chainguard/chainguard-images/features/request-resources/The Chainguard Console includes the Requests section where customers can submit and track requests for resources that Chainguard doesn’t currently offer. This improves transparency around which technologies Chainguard is working to build and helps minimize duplicate build requests. This guide provides an overview of how to submit a request for a new resource to Chainguard, as well as the limitations on what resources can be built. Note: As of this writing, the Requests section is in beta.https://deploy-preview-3155--ornate-narwhal-088216.netlify.app/chainguard/chainguard-images/features/using-the-tag-history-api/Fri, 26 May 2023 08:49:31 +0000https://deploy-preview-3155--ornate-narwhal-088216.netlify.app/chainguard/chainguard-images/features/using-the-tag-history-api/Chainguard Containers have automated nightly builds, which ensures our container images are always fresh including any recent patches and updated software. Even though it is important to keep your base images always updated, there will be situations where you’ll want to keep using an older build to make sure nothing will change in your container environment until you feel it’s safe to update. For cases like this, it is useful to point your Dockerfile to use a specific container image digest as base image.https://deploy-preview-3155--ornate-narwhal-088216.netlify.app/chainguard/chainguard-images/features/cve_visualizations/Thu, 19 Dec 2024 11:07:52 +0200https://deploy-preview-3155--ornate-narwhal-088216.netlify.app/chainguard/chainguard-images/features/cve_visualizations/Chainguard provides CVE Visualizations for all of its container images. This feature creates reports with CVE comparisons between Chainguard Containers and popular alternatives, as well as historical CVE remediation metrics. CVE Visualizations provide insight into image health and can help teams measure the engineering, security, and economic benefits gained from using Chainguard Containers. This guide outlines how you can access a container image’s CVE Visualization in both the Chainguard Console and in the Containers Directory.https://deploy-preview-3155--ornate-narwhal-088216.netlify.app/chainguard/chainguard-images/features/incert-custom-certs/Mon, 03 Jul 2023 11:07:52 +0200https://deploy-preview-3155--ornate-narwhal-088216.netlify.app/chainguard/chainguard-images/features/incert-custom-certs/NOTE: If you are looking for a way to add certificates to existing Chainguard images, check out our doc on adding custom certificates with Custom Assembly. In many enterprise settings, an organization will have its own certificate authority which it uses to issue certificates for its internal services. This is often for security or control reasons but could also be related to regulatory requirements. If you’re using a container that needs to communicate with your organization’s services and your organization has its own certificate authority, you’ll need to add a valid certificate into your container.https://deploy-preview-3155--ornate-narwhal-088216.netlify.app/chainguard/chainguard-images/features/unique-tags/Thu, 29 Feb 2024 08:49:31 +0000https://deploy-preview-3155--ornate-narwhal-088216.netlify.app/chainguard/chainguard-images/features/unique-tags/Chainguard’s Unique Tags feature provides unique timestamped tags for every container image build, addressing enterprise requirements for precise version tracking and automated deployment workflows. Many organizations rely on distinct tags to trigger automated deployments and maintain audit trails, making traditional floating tags like ’latest’ unsuitable for production use. To help with cases like this, Chainguard offers Unique Tags for private registries. Unique Tags are ideal for organizations that require a strict tag per release or update of their images.