Supported tags and respective
Where to file issues:
Supported Docker versions:
the latest release (down to 1.6 on a best-effort basis)
What is Debian?
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.
About this image
debian:latest tag will always point the latest stable release (which is, at the time of this writing,
debian:jessie). Stable releases are also tagged with their version (ie,
debian:8 is an alias for
debian:7 is an alias for
The rolling tags (
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
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.utf8
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.
debuerreotype-slimify script (
debuerreotype linked below) for more details about what gets removed during the "slimification" process.
How It's Made
The 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.
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 a single place (for placement 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).
Same problem here,
W: There is no public key available for the following key IDs: EF0F382A1A7B6500 and the build fails. Is there a workaround or do we have to wait for a fix?
Due to the new release of Debian yesterday, the stable image fails on
apt-get update with:
root@25d5efcb7087:/# apt-get update Get:1 http://security.debian.org stable/updates InRelease [62.9 kB] Ign http://deb.debian.org stable InRelease Get:2 http://deb.debian.org stable-updates InRelease [88.5 kB] Get:3 http://deb.debian.org stable Release.gpg [3108 B] Get:4 http://deb.debian.org stable Release [113 kB] Get:5 http://security.debian.org stable/updates/main amd64 Packages [35.0 kB] Get:6 http://deb.debian.org stable-updates/main amd64 Packages [20 B] Get:7 http://deb.debian.org stable/main amd64 Packages [9497 kB] Fetched 9800 kB in 4s (2116 kB/s) Reading package lists... Done W: There is no public key available for the following key IDs: EF0F382A1A7B6500
This breaks our automated setup
when I try to create a new image I get this error $ docker build -t bubba9er/debian .
Error checking context: 'can't stat '\?\C:\Users\BDMAS\AppData\Local\Applicatio
n Data''. can some one tell me what the problem I look for the path and did not find the \AppData\Local\Application, but when I try to make the \AppData...it ask me if I want to merge the folder I was trying to create.
@phillo Interesting approach. Usually, I would expect the image to be what is distributed. To answer your question though, you can add whatever packages are needed in your Dockerfile. This is just a base image.
@ikit maybe because your dockerhost is a ubuntu ;)
The list of packages installed is very small. It's actually missing the less package, which is surprising, because that appears to be included in the base system (at important priority). Am I mistaken about less being in the base system, or is this image some subset of base?
And another, related question: are there other, larger debian images (like desktop) either in existence, or planned? I'm testing software for end users, which I'll distribute to them directly (as an AppImage), and I know that the base install doesn't have enough packages. So it's useful for me to test on desktop images, to see if it works there out of the box.
Hi, Why when I build my container from this hub when I connect to my container and run the command uname -a, I got an Ubuntu .....
root@dbedbe4ea6f4:/# uname -a
Linux dbedbe4ea6f4 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 GNU/Linux
I tried to build
- FROM debian:jessie
- FROM debian:latest
- FROM debian:8.5
- FROM debian:8
and for each I got an ubuntu :-(
Is it normal ?
@m10141 use 'ip addr'
The command ifconfig returns command not found
If I use FROM debian:jessie as the basis of an image that is part of a commercial project, what does that imply from a licensing point of view? Is it equivalent to redistributing debian on a CD for instance...