packaged by Chainguard
Contact our team to test out this image for free. Please also indicate any other images you would like to evaluate.
FIPS-enabled Velero storage-provider plugin for Alibaba Cloud (OSS object store and ECS disk snapshots)
Chainguard Containers are regularly-updated, secure-by-default container images.
For those with access, this container image is available on cgr.dev:
Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.
Chainguard's velero-plugin-for-alicloud-fips ships the same velero-plugin-for-alibabacloud binary as the non-FIPS variant (same upstream AliyunContainerService/velero-plugin v1.0.0 source, same /plugins → /target init-container contract), built against the Microsoft Go FIPS 140-3 toolchain so no changes to Velero manifests or velero install flags are required when switching registries.
The plugin binary is built with go-msft-1.27, which routes Go stdlib crypto through the FIPS 140-3-validated OpenSSL provider. The go-msft toolchain HMACs its own text section at startup and aborts on tamper, which is why this image does not carry xcover instrumentation.
Note that only the plugin executable is copied into Velero at init-container time — the OpenSSL config files and provider shared objects stay in this image's rootfs and do not follow the binary. The running plugin's crypto backend is therefore established by the Velero container image, not by this one. When Velero itself is a FIPS build (for example velero-fips), the plugin links against that container's validated provider; when Velero's base image does not supply one, the go-msft runtime falls back to its validated Go-module implementation. For more detail, see the FIPS-enabled images guide.
See the non-FIPS variant's Getting Started section for the install flow — the two images share the same manifests and configuration; only the Chainguard image reference changes:
Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.
All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.
The main features of Chainguard Containers include:
For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.
In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.
Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.
To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.
To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.
Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.
This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.
Chainguard's container images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" tag of this image:
Apache-2.0
NIST-PD
For a complete list of licenses, please refer to this Image's SBOM.
Software license agreementChainguard Containers are SLSA Level 3 compliant with detailed metadata and documentation about how it was built. We generate build provenance and a Software Bill of Materials (SBOM) for each release, with complete visibility into the software supply chain.
SLSA compliance at ChainguardThis image helps reduce time and effort in establishing PCI DSS 4.0 compliance with low-to-no CVEs.
PCI DSS at ChainguardThis is a FIPS validated image for FedRAMP compliance.
This image is STIG hardened and scanned against the DISA General Purpose Operating System SRG with reports available.
Learn more about STIGsGet started with STIGs