oowy/glibc repository overview

⁠Quick reference

• Maintained by:
  Oowy team⁠

• Where to get help:
  the Docker Community Slack⁠, Server Fault⁠, Unix & Linux⁠, or Stack Overflow⁠

⁠Supported tags

Based on Alpine 3.20

• latest
• 2.39-alpine3.20

Based on Alpine 3.19

• 2.39-alpine3.19
• 2.38-alpine3.19
• 2.37-alpine3.19
• 2.36-alpine3.19

Based on Alpine 3.18

• 2.39-alpine3.18
• 2.38-alpine3.18
• 2.37-alpine3.18
• 2.36-alpine3.18

Based on Alpine 3.17

• 2.38-alpine3.17
• 2.37-alpine3.17
• 2.36-alpine3.17

⁠Quick reference (cont.)

• Supported architectures: amd64, arm64v8

⁠What is Alpine Linux?

Alpine Linux is a lightweight, security-oriented Linux distribution. It is designed to be small in size (less than 10 MB), highly modular, and optimized for running in resource-constrained environments.

Alpine Linux follows a "musl libc" and "busybox" based approach, which makes it a popular choice for use in containerized applications. It uses its own package management system called "apk" which simplifies package management and reduces the size of the packages.

Alpine Linux has gained popularity in recent years due to its lightweight and secure nature, which makes it ideal for running containerized applications and services.

⁠What's in this image?

This image is built from the official Alpine Linux image with Glibc installed, for efficient container management.

⁠About this image

⁠Platform image

The default (platform) image is a general-purpose image basic tools like Glibc.

The oowy/glibc:2.39-alpine3.19 tag will always point to the latest stable release of the default image.

⁠License

View license information⁠ for the software contained in this image.

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

Some additional license information which was able to be auto-detected might be found in the repo-info repository's alpine/ directory⁠.

As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.