<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Integration on</title><link>https://deploy-preview-3996--ornate-narwhal-088216.netlify.app/tags/integration/</link><description>Recent content in Integration on</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><copyright>Copyright (c) 2023 Chainguard</copyright><lastBuildDate>Wed, 09 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://deploy-preview-3996--ornate-narwhal-088216.netlify.app/tags/integration/index.xml" rel="self" type="application/rss+xml"/><item><title>Configure Chainguard Libraries access in container builds</title><link>https://deploy-preview-3996--ornate-narwhal-088216.netlify.app/chainguard/libraries/policies-and-security/build-containers/</link><pubDate>Wed, 09 Sep 2026 00:00:00 +0000</pubDate><guid>https://deploy-preview-3996--ornate-narwhal-088216.netlify.app/chainguard/libraries/policies-and-security/build-containers/</guid><description>&lt;p&gt;When you build a container that installs from Chainguard Libraries, the build must authenticate to Chainguard Libraries — or to a repository manager that proxies it — without baking credentials into the final image.&lt;/p&gt;
&lt;p&gt;The package-manager configuration differs by language, but the container-build pattern is the same: pass the credentials into the build stage only for the install step that needs them. For the credentials file, target filename, and file format expected by each package manager, see the ecosystem-specific build configuration page:&lt;/p&gt;</description></item></channel></rss>