-
Where to get help:
the Docker Community Slack, Server Fault, Unix & Linux, or Stack Overflow
bookworm,bookworm-20240513,12.5,12,latestbookworm-backportsbookworm-slim,bookworm-20240513-slim,12.5-slim,12-slimbullseye,bullseye-20240513,11.9,11bullseye-backportsbullseye-slim,bullseye-20240513-slim,11.9-slim,11-slimbuster,buster-20240513,10.13,10buster-slim,buster-20240513-slim,10.13-slim,10-slimexperimental,experimental-20240513oldoldstable,oldoldstable-20240513oldoldstable-slim,oldoldstable-20240513-slimoldstable,oldstable-20240513oldstable-backportsoldstable-slim,oldstable-20240513-slimrc-buggy,rc-buggy-20240513sid,sid-20240513sid-slim,sid-20240513-slimstable,stable-20240513stable-backportsstable-slim,stable-20240513-slimtesting,testing-20240513testing-backportstesting-slim,testing-20240513-slimtrixie,trixie-20240513trixie-backportstrixie-slim,trixie-20240513-slimunstable,unstable-20240513unstable-slim,unstable-20240513-slim
-
Where to file issues:
https://github.com/debuerreotype/docker-debian-artifacts/issues -
Supported architectures: (more info)
amd64,arm32v5,arm32v7,arm64v8,i386,mips64le,ppc64le,riscv64,s390x -
Published image artifact details:
repo-info repo'srepos/debian/directory (history)
(image metadata, transfer size, etc) -
Image updates:
official-images repo'slibrary/debianlabel
official-images repo'slibrary/debianfile (history) -
Source of this description:
docs repo'sdebian/directory (history)
Debian is an operating system which is composed primarily of free and open-source software, most of which is under the GNU General Public License, and developed by a group of individuals known as the Debian project. Debian is one of the most popular Linux distributions for personal computers and network servers, and has been used as a base for several other Linux distributions.
The debian:latest tag will always point the latest stable release. Stable releases are also tagged with their version (ie, debian:11 is an alias for debian:bullseye, debian:10 is an alias for debian:buster, etc).
The rolling tags (debian:stable, debian:testing, etc) use the rolling suite names in their /etc/apt/sources.list file (ie, deb http://deb.debian.org/debian testing main).
The mirror of choice for these images is the deb.debian.org CDN pointer/redirector so that it's as reliable as possible for the largest subset of users (and is also the default mirror for debootstrap as of 2016-10-20). See the deb.debian.org homepage for more information.
If you find yourself needing a Debian release which is EOL (and thus only available from archive.debian.org), you should check out the debian/eol image, which includes tags for Debian releases as far back as Potato (Debian 2.2), the first release to fully utilize APT.
Given that it is a faithful "minbase" install of Debian, this image only includes the C, C.UTF-8, and POSIX locales by default. For most uses requiring a UTF-8 locale, C.UTF-8 is likely sufficient (-e LANG=C.UTF-8 or ENV LANG C.UTF-8).
For uses where that is not sufficient, other locales can be installed/generated via the locales package. PostgreSQL has a good example of doing so, copied below:
RUN apt-get update && apt-get install -y locales && rm -rf /var/lib/apt/lists/* \
&& localedef -i en_US -c -f UTF-8 -A /usr/share/locale/locale.alias en_US.UTF-8
ENV LANG en_US.utf8The rootfs tarballs for this image are built using the reproducible-Debian-rootfs tool, debuerreotype, with an explicit goal being that they are transparent and reproducible. Using the same toolchain, it should be possible to regenerate (clean-room!) the same tarballs used for building the official Debian images. The examples/debian.sh script in that debuerreotype repository (and the debian-all.sh companion/wrapper) is the canonical entrypoint used for creating the artifacts published in this image (via a process similar to the docker-run.sh included in the root of that repository).
Additionally, the scripts in https://github.com/debuerreotype/docker-debian-artifacts are used to create each tag's Dockerfile and collect architecture-specific tarballs into dist-ARCH branches on the same repository, which also contain extra metadata about the artifacts included in each build, such as explicit package versions included in the base image (rootfs.manifest), the exact snapshot.debian.org timestamp used for debuerreotype invocation (rootfs.debuerreotype-epoch), the sources.list found in the image (rootfs.sources-list) and the one used during image creation (rootfs.sources-list-snapshot), etc.
For convenience, the SHA256 checksum (and full build command) for each of the primary rootfs.tar.xz artifacts are also published at docker.debian.net.
These tags are an experiment in providing a slimmer base (removing some extra files that are normally not necessary within containers, such as man pages and documentation), and are definitely subject to change.
See the debuerreotype-slimify script (debuerreotype linked above) for more details about what gets removed during the "slimification" process.
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 debian/ 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.