Supported tags and respective
Docker image with uWSGI and Nginx for web applications in Python 3.6, Python 3.5 and Python 2.7 (as Flask) in a single container.
Soon the tag
latest will point to
python3.6 instead of
If you are using in your
you should update it to:
uWSGI with Nginx is one of the best ways to deploy a Python application, so you should have a good performance (check the benchmarks) with this image.
This image was created to be the base image for tiangolo/uwsgi-nginx-flask but could be used as the base image to run any Python web application.
GitHub repo: https://github.com/tiangolo/uwsgi-nginx-docker
Docker Hub image: https://hub.docker.com/r/tiangolo/uwsgi-nginx/
How to use
- You shouldn't have to clone the GitHub repo. You should use it as a base image for other images, using this in your
FROM tiangolo/uwsgi-nginx:python3.6 # Your Dockerfile code...
But, if you need Python 2.7 that line would have to be
By default it will try to find a uWSGI config file in
uwsgi.inifile will make it try to run a Python file in
If you are building a Flask web application you should use instead tiangolo/uwsgi-nginx-flask.
Custom app directory
If you need to use a directory for your app different than
/app, you can override the uWSGI config file path with an environment variable
UWSGI_INI, and put your custom
uwsgi.ini file there.
For example, if you needed to have your application directory in
/application instead of
Dockerfile would look like:
FROM tiangolo/uwsgi-nginx:python3.6 ENV UWSGI_INI /application/uwsgi.ini COPY ./application /application WORKDIR /appapplication
uwsgi.ini file in
./application/uwsgi.ini would contain:
Note: it's important to include the
WORKDIR option, otherwise uWSGI will start the application in
Custom max upload size
In this image, Nginx is configured to allow unlimited upload file sizes. This is done because by default a simple Python server would allow that, so that's the simplest behavior a developer would expect.
If you need to restrict the maximum upload size in Nginx, you can add an environment variable
NGINX_MAX_UPLOAD and assign a value corresponding to the standard Nginx config
For example, if you wanted to set the maximum upload file size to 1 MB (the default in a normal Nginx installation), you would need to set the
NGINX_MAX_UPLOAD environment variable to the value
1m. Then the image would take care of adding the corresponding configuration file (this is done by the
Dockerfile would look something like:
FROM tiangolo/uwsgi-nginx:python3.6 ENV NGINX_MAX_UPLOAD 1m COPY ./app /app
2017-08-09: You can set a custom maximum upload file size using an environment variable
NGINX_MAX_UPLOAD, by default it has a value of
0, that allows unlimited upload file sizes. This differs from Nginx's default value of 1 MB. It's configured this way because that's the simplest experience a developer that is not expert in Nginx would expect.
2017-08-09: Now you can override where to look for the
uwsgi.inifile, and with that, change the default directory from
/appto something else, using the envirnoment variable
2017-08-08: Supervisord now terminates uWSGI on
SIGTERM, so if you run
docker stopor something similar, it will actually stop everything, instead of waiting for Docker's timeout to kill the container.
2017-07-31: There's now an image tag for Python 3.6, based on the official image for Python 3.6.
2016-10-01: Now you can override default
uwsgi.iniparameters from the file in
2016-08-16: There's now an image tag for Python 3.5, based on the official image for Python 3.5. So now you can use this image for your projects in Python 2.7 and Python 3.5.
2016-08-16: Use dynamic a number of worker processes for uWSGI, from 2 to 16 depending on load. This should work for most cases. This helps especially when there are some responses that are slow and take some time to be generated, this change allows all the other responses to keep fast (in a new process) without having to wait for the first (slow) one to finish.
Also, it now uses a base
/etc/uwsgi/with most of the general configurations, so, the
/app(the one you could need to modify) is now a lot simpler.
2016-04-05: Nginx and uWSGI logs are now redirected to stdout, allowing to use
One of the best ways to deploy a Python web application is with uWSGI and Nginx, as seen in the benchmarks.
Nginx is a web server, it takes care of the HTTP connections and also can serve static files directly and more efficiently.
uWSGI is an application server, that's what runs your Python code and it talks with Nginx.
Your Python code has the actual web application, and is run by uWSGI.
This image takes advantage of already slim and optimized existing Docker images (based on Debian as recommended by Docker) and implements Docker best practices.
It uses the official Python Docker image, installs uWSGI and on top of that, with the least amount of modifications, adds the official Nginx image (as of 2016-02-14).
And it controls all these processes with Supervisord.
There's the rule of thumb that you should have "one process per container".
That helps, for example, isolating an app and its database in different containers.
But if you want to have a "micro-services" approach you may want to have more than one process in one container if they are all related to the same "service", and you may want to include your Flask code, uWSGI and Nginx in the same container (and maybe run another container with your database).
That's the approach taken in this image.
This image has a default sample "Hello World" app in the container's
/app directory using the example in the uWSGI documentation.
You probably want to override it or delete it in your project.
It is there in case you run this image by itself and not as a base image for your own
Dockerfile, so that you get a sample app without errors.
This project is licensed under the terms of the Apache license.