https://deploy-preview-3174--ornate-narwhal-088216.netlify.app/tags/packages/Recent content in Packages onHugo -- gohugo.ioen-USThu, 23 Oct 2025 11:07:52 +0200https://deploy-preview-3174--ornate-narwhal-088216.netlify.app/chainguard/chainguard-images/about/package-name-mappings/Thu, 23 Oct 2025 11:07:52 +0200https://deploy-preview-3174--ornate-narwhal-088216.netlify.app/chainguard/chainguard-images/about/package-name-mappings/When migrating to Chainguard Containers, you may notice that some package and image names differ from their upstream counterparts. This guide explains why these mappings exist and provides a comprehensive reference of how Chainguard maps image and package names to our container ecosystem. Why Chainguard Remaps Package Names Different Linux distributions often use different names for the same software. For example, Debian calls its C compiler package build-essential, while Alpine calls the equivalent package build-base and Fedora uses gcc and related packages.