From 0a6d19e96a6dae1be530e134a1680a0b38d12bb0 Mon Sep 17 00:00:00 2001 From: Garry Ing Date: Fri, 13 Sep 2024 11:19:00 -0500 Subject: [PATCH] Fix glibc vs. musl article link (#1812) https://edu.chainguard.dev/chainguard/chainguard-images/working-with-images/images-compiled-programs/compiled-programs/#what-about-musl --- .../images-compiled-programs/compiled-programs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/chainguard/chainguard-images/working-with-images/images-compiled-programs/compiled-programs.md b/content/chainguard/chainguard-images/working-with-images/images-compiled-programs/compiled-programs.md index 39ba4e357b..9ac93fbfe9 100644 --- a/content/chainguard/chainguard-images/working-with-images/images-compiled-programs/compiled-programs.md +++ b/content/chainguard/chainguard-images/working-with-images/images-compiled-programs/compiled-programs.md @@ -130,7 +130,7 @@ You can find the complete inventory of packages for the `glibc-openssl` Chaingua At the time of this writing, no Chainguard Images come packaged with `musl`. Chainguard builds `glibc`-based images because `glibc` is commonly used, which makes it easier for most developers to start consuming Chainguard Images in their environments. Additionally, `glibc` is widely tested, making it a dependable choice for a C standard library implementation. As `glibc` is a well-established option, choosing to use `glibc` ensures more applications will be compatible with new images. -Though `musl` is sometimes chosen because of its minimal footprint, Chainguard’s distroless approach based on [Wolfi](https://www.chainguard.dev/unchained/introducing-wolfi-the-first-linux-un-distro) often results in a container image of comparable (or smaller) size than official `musl` based images. For more information, please refer to our [glibc vs. musl](/chainguard/chainguard-images/working-with-images/compiled-programs/glibc-vs-musl) article. +Though `musl` is sometimes chosen because of its minimal footprint, Chainguard’s distroless approach based on [Wolfi](https://www.chainguard.dev/unchained/introducing-wolfi-the-first-linux-un-distro) often results in a container image of comparable (or smaller) size than official `musl` based images. For more information, please refer to our [glibc vs. musl](/chainguard/chainguard-images/working-with-images/images-compiled-programs/glibc-vs-musl) article. ## Next Steps