Docker builds python Flask+ nginx+uwsgi container

Install Nginx

First pull the centos image docker pull centos centos

We install the latest nginx1.19 version: Download address

Run the centos image and enter:

docker run --name ver -d -p 8051:80 -it nginx_start

Put the nginx-1.19.0.tar.gz package into the container:

docker cp nginx-1.19.0.tar.gz 10e87af84c05:/root (10e87af84c05 is the centos container id)

Before installing nginx, install some dependencies:

yum -y install gcc gcc-c++ autoconf automake make
yum -y install zlib zlib-devel openssl openssl-devel pcre pcre-devel

Unzip:

tar -zxvf nginx-1.19.0.tar.gz

#Enter nginx-1.10.1 and configure nginx
 cd nginx-1.19.0
 #Configure nginx
 #--prefix specifies the installation directory#/usr/local/nginx is the installation directory and cannot be the same as the directory of the downloaded file#./configure --prefix=/usr/local/nginx
 
 #With ssl stub_status module add strem module –with-stream, so that tcp protocol can be transmitted #http_stub_status_module status monitoring #http_ssl_module configure https
 #stream configure tcp to forward #http_gzip_static_module compression #http_sub_module replace request ./configure --prefix=/usr/local/nginx --with-http_stub_status_module --with-http_ssl_module --with-stream

Note:

Here I have the error that pcre and zlib are missing. You can use yum -y install zlib zlib-devel openssl openssl--devel pcre pcre-devel command to install all dependencies.

Then make & make install to compile and install

After successful installation, four files will be generated in the directory specified by ./configure --prefix=/usr/local/nginx . We only need to enter /usr/local/nginx/sbin/nginx to start the nginx service.

To verify success, you can enter curl localhost to see whether it is started successfully.

Generate an image

10. Package the centos container with nginx as a mirror docker commit ba5ba0d81912 nginx_centos (ba5ba0d81912 is the container ID, renamed to nginx_centos)
11. Re-run the new image: docker run --name ver -d -p 8051:80 -it nginx_centos
12. At this time, the image has our installed nginx, so we can use it to do whatever we want and perform some other fancy operations.

Install Python 2.7 environment

yum install gcc openssl-devel bzip2-devel

Download Python 2.7 with wget and unzip it

yum -y install wget　

Enter the directory /usr/src and use wget to download python 2.7

cd /usr/src
wget https://www.python.org/ftp/python/2.7.15/Python-2.7.15.tgz

Unzip python2.7 again

tar -zxvf Python-2.7.15.tgz

Install Python 2.7

Enter the Python-2.7.15 unzipped above and use the following command line to install it in the unzipped file

cd Python-2.7.15
./configure --enable-optimizations
make altinstall

Install PIP

curl "https://bootstrap.pypa.io/get-pip.py" -o "get-pip.py"
python2.7 get-pip.py

Because the version is 2.7, and there is a MYSQL-python library in requirements.txt, an error will be reported that libmysqlclient-dev cannot be found. This can be solved by executing yum install mysql-devel .

Install UWSGI

When pip install uwsgi an error will be reported:

plugins/python/uwsgi_python.h:2:20: fatal error: Python.h: No such file or directory
#include <Python.h>

Run yum install python-devel.x86_64 to solve the problem, and re-pip install to download it.

Configure uWSGI server

The relevant uwsgi.ini file contents are as follows:

[uwsgi]
socket = /tmp/uwsgi.sock
chown-socket = nginx:nginx
chmod-socket = 664
# Graceful shutdown on SIGTERM, see https://github.com/unbit/uwsgi/issues/849#issuecomment-118869386
hook-master-start = unix_signal:15 gracefully_kill_them_all

Create the uwsgi.ini file in the project directory/app/:

[uwsgi]

uwsgi-socket = /tmp/uwsgi.sock
chmod-socket = 777
callable = app
wsgi-file = main.py
buffer-size = 65535
processes = %(%k * 2)
threads = %(%k * 20

The meaning of each parameter is:

uwsgi-socket: The uwsgi-socket configuration item specifies a file, which is a Unix socket, that is, a socket that is addressed and accessed through the file system (rather than a network address). After configuring uwsgi-socket, you also need to configure chmod-socket.
Unix socket is a file, so it will be subject to the permissions of the Unix system and can be configured to 660 or 777.
Enable the uwsgi client to access this Unix socket file, which is configured as 777 here.

callable: Sets which variable in the module loaded by uwsgi will be called when a request is received. The default is the variable named "application".

wsgi-file: Load the specified wsgi file.

buffer-size: Sets the internal buffer size used for uwsgi packet parsing. The default is 4k.

processes and threads are the number of processes and threads opened, respectively, and %k is a magic number variable, representing the number of CPU cores. If we have a dual-core CPU,
The processes and threads here are 4 and 40 respectively, that is, there are 4 processes and each process has 40 threads.

Install Supervisor (Optional)

Direct yum installation will report an error " No package supervisor available. " This is because CentOS is compiled from RedHat Enterprise Edition, removing all copyright issues. Just execute yum install epel-release to solve the problem. After installation, the following directory will be generated:

Now we will configure supervisor so that it listens to nginx and uwsgi services.

First, create the supervisor file in the /etc directory, then create the supervisord.conf file and the conf.d directory:

The supervisord.conf directory is configured as follows:

; supervisor config file

[unix_http_server]
file=/var/run/supervisor/supervisor.sock ; (the path to the socket file)
chmod=0700 ; sockef file mode (default 0700)

[supervisord]
logfile=/var/log/supervisor/supervisord.log ; (main log file; default $CWD/supervisord.log)
pidfile=/var/run/supervisord.pid ; (supervisord pidfile;default supervisord.pid)
childlogdir=/var/log/supervisor ; ('AUTO' child log dir, default $TEMP)

; the below section must remain in the config file for RPC
; (supervisorctl/web interface) to work, additional interfaces may be
; added by defining them in separate rpcinterface: sections
[rpcinterface:supervisor]
supervisor.rpcinterface_factory = supervisor.rpcinterface:make_main_rpcinterface

[supervisorctl]
serverurl=unix:///var/run/supervisor.sock ; use a unix:// URL for a unix socket

; The [include] section can just contain the "files" setting. This
; setting can list multiple files (separated by whitespace or
; newlines). It can also contain wildcards. The filenames are
; interpreted as relative to this file. Included files *cannot*
; include files themselves.

[include]
files = /etc/supervisor/conf.d/*.conf

Then create the supervisord.conf file in the conf.d directory and edit it:

[supervisord]
nodaemon=true

[program:uwsgi]
command=/usr/bin/uwsgi --ini /etc/uwsgi/uwsgi.ini --die-on-term --need-app
stdout_logfile=/dev/stdout
stdout_logfile_maxbytes=0
stderr_logfile=/dev/stderr
stderr_logfile_maxbytes=0

[program:nginx]
command=/usr/local/nginx/sbin/nginx
stdout_logfile=/dev/stdout
stdout_logfile_maxbytes=0
stderr_logfile=/dev/stderr
stderr_logfile_maxbytes=0
# Graceful stop, see http://nginx.org/en/docs/control.html
stopsignal=QUIT

The above paths are all actual directory configurations. If they are different, they need to be changed.

Then start the supervisor:

After the above configuration is completed, we repackage the container to generate a new image, recorded as base_v3 , and write a Dockerfile to package the docker application:

FROM base_v3
 
# Create a working directory RUN mkdir /app
 
# Specifies that all commands executed when the container is started are executed in the app directory WORKDIR /app
 
# Replace nginx configuration COPY nginx.conf /etc/nginx/nginx.conf
 
# Copy the contents of the local app directory to the container's app directory COPY ./app/ /app/

Here, create another nginx.conf file in the same directory as Dockerfile and app, and modify the content of nginx.conf as follows:

user nginx;
worker_processes 1;
error_log /usr/local/nginx/logs/error.log warn;
pid /usr/local/nginx/logs/nginx.pid;
worker_rlimit_nofile 20480;


events {
 use epoll;
 worker_connections 20480;
 multi_accept on;
}


http {
  include /usr/local/nginx/conf/mime.types;
  default_type application/octet-stream;

  log_format main '$remote_addr - $remote_user [$time_local] "$request" '
           '$status $body_bytes_sent "$http_referer" '
           '"$http_user_agent" "$http_x_forwarded_for"';
  #For large request volumes, it is recommended to close access_log
  #access_log /var/log/nginx/access.log main;

  sendfile on;
  #tcp_nopush on;

  keepalive_timeout 300s;
  client_header_timeout 300s;
  client_body_timeout 300s;

  gzip on;
  gzip_min_length 1k;
  gzip_buffers 4 16k;
  gzip_types text/html application/javascript application/json;

  include /usr/local/nginx/conf.d/*.conf;

  server {
   listen 6666;
   charset utf-8;
   client_max_body_size 75M;
   location / {
    include uwsgi_params;
    uwsgi_pass unix:///tmp/uwsgi.sock;
    uwsgi_send_timeout 300;
    uwsgi_connect_timeout 300;
    uwsgi_read_timeout 300;
   }
  }
}

Next, you only need to docker build -t new_project . and docker run --name test -d -p 8055:6666 -v /root/web/mim_backend/data:/app/static -v /root/logs/mim_backend:/app/log -it new_project .
Of course, at this time, nginx and uwsgi are not started automatically and need to be started manually. If you want to start the service automatically, you can use supervisor or add an ENTRYPOINT nginx -g "daemon on;" && uwsgi --ini /app/uwsgi.ini

Then run an interface test at random:

This is the end of this article about building python Flask + nginx + uwsgi container with Docker. For more related content about building Flask + nginx + uwsgi with Docker, please search for previous articles on 123WORDPRESS.COM or continue to browse the following related articles. I hope you will support 123WORDPRESS.COM in the future!