Supported tags and respective
Where to file issues:
the Docker Community
Supported Docker versions:
the latest release (down to 1.6 on a best-effort basis)
What is Python?
Python is an interpreted, interactive, object-oriented, open-source programming language. It incorporates modules, exceptions, dynamic typing, very high level dynamic data types, and classes. Python combines remarkable power with very clear syntax. It has interfaces to many system calls and libraries, as well as to various window systems, and is extensible in C or C++. It is also usable as an extension language for applications that need a programmable interface. Finally, Python is portable: it runs on many Unix variants, on the Mac, and on Windows 2000 and later.
How to use this image
Dockerfile in your Python app project
FROM python:3 WORKDIR /usr/src/app COPY requirements.txt ./ RUN pip install --no-cache-dir -r requirements.txt COPY . . CMD [ "python", "./your-daemon-or-script.py" ]
or (if you need to use Python 2):
FROM python:2 WORKDIR /usr/src/app COPY requirements.txt ./ RUN pip install --no-cache-dir -r requirements.txt COPY . . CMD [ "python", "./your-daemon-or-script.py" ]
You can then build and run the Docker image:
$ docker build -t my-python-app . $ docker run -it --rm --name my-running-app my-python-app
Run a single Python script
For many simple, single file projects, you may find it inconvenient to write a complete
Dockerfile. In such cases, you can run a Python script by using the Python Docker image directly:
$ docker run -it --rm --name my-running-script -v "$PWD":/usr/src/myapp -w /usr/src/myapp python:3 python your-daemon-or-script.py
or (again, if you need to use Python 2):
$ docker run -it --rm --name my-running-script -v "$PWD":/usr/src/myapp -w /usr/src/myapp python:2 python your-daemon-or-script.py
python images come in many flavors, each designed for a specific use case.
This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of. This tag is based off of
buildpack-deps is designed for the average user of docker who has many images on their system. It, by design, has a large number of extremely common Debian packages. This reduces the number of packages that images that derive from it need to install, thus reducing the overall size of all images on your system.
This image does not contain the common packages contained in the default tag and only contains the minimal packages needed to run
python. Unless you are working in an environment where only the
python image will be deployed and you have space constraints, we highly recommend using the default image of this repository.
This image is based on the popular Alpine Linux project, available in the
alpine official image. Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
This variant is highly recommended when final image size being as small as possible is desired. The main caveat to note is that it does use musl libc instead of glibc and friends, so certain software might run into issues depending on the depth of their libc requirements. However, most software doesn't have an issue with this, so this variant is usually a very safe choice. See this Hacker News comment thread for more discussion of the issues that might arise and some pro/con comparisons of using Alpine-based images.
To minimize image size, it's uncommon for additional related tools (such as
bash) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the
alpine image description for examples of how to install packages if you are unfamiliar).
ONBUILD image variants are deprecated, and their usage is discouraged. For more details, see docker-library/official-images#2076.
This image feeds your
requirements.txt file automatically to
pip in order to make building derivative images easier. For most use cases, creating a
Dockerfile in the base of your project directory with the line
FROM python:onbuild will be enough to create a stand-alone image for your project.
onbuild variant is really useful for "getting off the ground running" (zero to Dockerized in a short period of time), it's not recommended for long-term usage within a project due to the lack of control over when the
ONBUILD triggers fire (see also
Once you've got a handle on how your project functions within Docker, you'll probably want to adjust your
Dockerfile to inherit from a non-
onbuild variant and copy the commands from the
Dockerfile (moving the
ONBUILD lines to the end and removing the
ONBUILD keywords) into your own file so that you have tighter control over them and more transparency for yourself and others looking at your
Dockerfile as to what it does. This also makes it easier to add additional requirements as time goes on (such as installing more packages before performing the previously-
This image is based on Windows Server Core (
microsoft/windowsservercore). As such, it only works in places which that image does, such as Windows 10 Professional/Enterprise (Anniversary Edition) or Windows Server 2016.
For information about how to get Docker running on Windows, please see the relevant "Quick Start" guide provided by Microsoft:
All tags listed on the same line at the top of the README will get you the same image right now.
In the future 2.7-onbuild might give you a newer image since it's not pinned with it's micro version.
2-onbuild will give you the currently latest 2.x.y image
2.7-onbuild will give you the currently latest 2.7.y image
2.7.13-onbuild will always give you the 2.7.13 image
I don't understand what is differenct between 2 images:
2.7.13-onbuild and 2.7-onbuild.
The Docker files both of them are the same:
Python 3.6 was released. When can we expect the update for this image from maintainers?
I'm trying to upload to my primate pypi from a process without tty, but it's not working.
docker run --rm -i -v $HOME/.pypirc:/root/.pypirc:ro -v $HOME/.pip/pip.conf:/root/.pip/pip.conf:ro my-image-from-python-3.5.2 python setup.py sdist upload -r private-pypi
... after sdist ... running upload /usr/local/lib/python3.5/getpass.py:92: GetPassWarning: Can not control echo on the terminal. passwd = fallback_getpass(prompt, stream) Warning: Password input may be echoed.
how to fix it ?
The latest image with 2.7.12 breaks installation of several system packages for two reasons:
docker run -it --rm python:2.7.12 /bin/bash
> apt-get update > apt-get install -y lsb-release > lsb_release bash: /usr/bin/lsb_release: /usr/bin/python: bad interpreter: No such file or directory > ls /usr/bin/python ls: cannot access /usr/bin/python: No such file or directory
of course we can fix it with symlink:
ln -s /usr/local/bin/python /usr/bin/python > lsb_release Traceback (most recent call last): File "/usr/bin/lsb_release", line 28, in <module> import lsb_release ImportError: No module named lsb_release
Since new python version does not include
"/usr/lib/python2.7/dist-packages/" in the sys.path, so lsb_release.py cannot be found.
there's a bug in the latest 2.7 version
docker pull python:2.7 # official python image docker run -it --rm python:2.7 bash -c 'apt-get update && apt-get install -y supervisor && supervisord —help' # install supervisord and get help ... Processing triggers for systemd (215-17+deb8u4) ... bash: /usr/bin/supervisord: /usr/bin/python: bad interpreter: No such file or directory
Warning to anyone using this, the python2 docker file has an old openssl which will break with some sites:
root@c1cf6ed65b86:/app# python -c 'import ssl; print ssl.OPENSSL_VERSION'#
OpenSSL 1.0.1k 8 Jan 2015
Python 2.7.11 (default, Mar 9 2016, 02:49:37)
[GCC 4.9.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/local/lib/python2.7/site-packages/requests/api.py", line 71, in get
return request('get', url, params=params, kwargs)
File "/usr/local/lib/python2.7/site-packages/requests/api.py", line 57, in request
return session.request(method=method, url=url, kwargs)
File "/usr/local/lib/python2.7/site-packages/requests/sessions.py", line 475, in request
resp = self.send(prep, send_kwargs)
File "/usr/local/lib/python2.7/site-packages/requests/sessions.py", line 585, in send
r = adapter.send(request, kwargs)
File "/usr/local/lib/python2.7/site-packages/requests/adapters.py", line 477, in send
raise SSLError(e, request=request)
requests.exceptions.SSLError: ("bad handshake: Error([('SSL routines', 'SSL3_GET_SERVER_CERTIFICATE', 'certificate verify failed')],)",)
Tried 2.7, could not find any text editor.
Does this work with Docker Toolbox on Windows?
Anyone else seeing issues with
docker pull python:2.7.10? This specific version is reproducing an AUFS error with a specific layer for me...
It happens from multiple hosts and across multiple Docker versions (1.7 and 1.9), on which I've docker rmi'd all existing images. I'm repeatedly hitting:
Error pulling image (2.7.10) from python, Driver aufs failed to create image rootfs dc921aeac8d06e7bd5b2d85b8684bb7c94ed08db3f18a9b6e897827810b289de: open /mnt/docker/aufs/layers/4c0cc976b7bbefe9abdfd8f0aae1bb3759004d3c9888c3164b38909b862c0cdf: no such file Error pulling image (2.7.10) from python, Driver aufs failed to create image rootfs dc921aeac8d06e7bd5b2d85b8684bb7c94ed08db3f18a9b6e897827810b289de: open /mnt/docker/aufs/layers/4c0cc976b7bbefe9abdfd8f0aae1bb3759004d3c9888c3164b38909b862c0cdf: no such file or directory
$ docker pull python:2.7.10
2.7.10: Pulling from python
16d3472bba11: Pull complete
16d3472bba11: Download complete
21845f98d5b6: Download complete
371b8d572221: Download complete
dc921aeac8d0: Pulling metadata
dc921aeac8d0: Error downloading dependent layers
a58e59632917: Download complete
25d6f9a46cb2: Download complete
13b09d8e7429: Download complete
e27c2341abc4: Download complete
e667d6ef2385: Download complete
37241fff5cc3: Download complete
aff5fe6ff082: Download complete
aff5fe6ff082: Pulling dependent layers
aff5fe6ff082: Error pulling image (2.7.10) from python, endpoint: https://registry-1.docker.io/v1/, Driver aufs failed to create image raff5fe6ff082: Error pulling image (2.7.10) from python, Driver aufs failed to create image rootfs dc921aeac8d06e7bd5b2d85b8684bb7c94ed08db3f18a9b6e897827810b289de: open /mnt/docker/aufs/layers/4c0cc976b7bbefe9abdfd8f0aae1bb3759004d3c9888c3164b38909b862c0cdf: no such file Error pulling image (2.7.10) from python, Driver aufs failed to create image rootfs dc921aeac8d06e7bd5b2d85b8684bb7c94ed08db3f18a9b6e897827810b289de: open /mnt/docker/aufs/layers/4c0cc976b7bbefe9abdfd8f0aae1bb3759004d3c9888c3164b38909b862c0cdf: no such file or directory