Home >Operation and Maintenance >Nginx >What is the method to install nginx plug-in files under Docker?
What is the method to install nginx plug-in files under Docker?
- WBOYforward
- 2023-05-13 15:04:121815browse
The purpose of the plug-in file:
-
The file is not bound by the docker image file. It can be modified, the container can be restarted, and the updated file can be used. It will not be restored by the image
Files such as logs and other information recorded during the running of the container can be automatically saved on external storage and will not be lost due to restarting the container
There are two ways to run a container:
docker run command
docker-compose command
The docker run command method uses the -v parameter to mount the external host directory to the path within the container. If there are multiple mount points, specify them through multiple -v parameters, and only absolute paths can be used; the docker-compose command uses The service method is easy to describe. To be precise, a service can contain multiple containers, and the mounting configuration of the external path is also configured through the -v parameter. The advantage is that you can use a relative path, which is of course relative to the path of the docker-compose.yml file. . Another advantage is that the command to start the container with docker-compose is relatively simple.
Assume that the image packaging path structure is as follows:
├── build.sh ├── docker-compose.yml ├── Dockerfile ├── mynginx.conf ├── nginx-vol │ ├── conf.d │ │ └── mynginx.conf │ ├── html │ │ └── index.html │ └── logs │ ├── access.log │ └── error.log └── run.sh
Dockerfile is the configuration file for building the image, and the content is as follows:
FROM nginx
LABEL maintainer="xxx" email="<xxx@xxx.com>" app="nginx test" version="v1.0"
ENV WEBDIR="/data/web/html"
RUN mkdir -p ${WEBDIR}
EXPOSE 5180Based on nginx, specify the new data file path as /data/web/html, the exposed port is 5180.
Compile a new image through the following command:
docker build -t nginx:test-v1 .
The compiled image tag is test-v1, you can view the local image:
docker images REPOSITORY TAG IMAGE ID CREATED SIZE nginx test-v1 d2a0eaea3fac 56 minutes ago 141MB nginx latest 605c77e624dd 9 days ago 141MB
You can see that the TAG is test- The v1 image is a new image that has just been compiled.
Create nginx external volume nginx-vol and related conf.d, logs, html folders, and put the corresponding contents into their corresponding directories. For example, the content of iindex.html in the html folder is as follows:
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
<title>系统时间</title>
<body>
<div id="datetime">
<script>
setInterval("document.getElementById('datetime').innerHTML=new Date().toLocaleString();",1000);
</script>
</div>
</body>
</head>
</html>is actually just a page that displays the current time.
The logs section is empty. The purpose is to write the logs when the container is running to external storage. Even if the container is stopped or the image is destroyed, the running logs can still be retained.
conf.d below is nginx personalized configuration, the content is as follows:
server {
listen 5180;
#listen [::]:5180;
server_name localhost;
#access_log /var/log/nginx/host.access.log main;
location / {
root /data/web/html;
index index.html index.htm;
}
#error_page 404 /404.html;
# redirect server error pages to the static page /50x.html
#
error_page 500 502 503 504 /50x.html;
location = /50x.html {
root /usr/share/nginx/html;
# proxy the PHP scripts to Apache listening on 127.0.0.1:80
#location ~ \.php$ {
# proxy_pass http://127.0.0.1;
#}
# pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
# root html;
# fastcgi_pass 127.0.0.1:9000;
# fastcgi_index index.php;
# fastcgi_param SCRIPT_FILENAME /scripts$fastcgi_script_name;
# include fastcgi_params;
# deny access to .htaccess files, if Apache's document root
# concurs with nginx's one
#location ~ /\.ht {
# deny all;
}In fact, the port and root path are modified based on nginx's default default.conf, the purpose is to illustrate nginx The configuration file can also be stored externally. If your own program can modify the configuration file, then in this way, the configuration file can be modified while the container is running; the modified configuration file is actually stored on the external storage, so it will not change anytime. It disappears when the container stops running, and will not be restored to the files inside the image.
docker run mode
For convenience, you can write the running command into a shell script, such as run.sh, the content is as follows:
docker run --name nginx-v1 -p 15180:5180 -v /home/project/nginx-test/nginx-vol/logs:/var/log/nginx -v /home/project/nginx-test/nginx-vol/conf.d:/etc/nginx/conf.d -v /home/project/nginx-test/nginx-vol/html:/data/web/html -d nginx:test-v1
You can see that there are 3 in the command Each -v corresponds to different external storage mounts and is mapped to different directories in the container. The ports after
-p (note that it is lowercase) are the host port and the container port respectively, that is, the host's 15180 port is mapped to the container's 5180 port, so that the nginx service port 5180 started by the container can be accessed through The host's port 15180 is mapped.
View running containers:
docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES cf2275da5130 nginx:test-v1 "/docker-entrypoint.…" 6 seconds ago Up 5 seconds 80/tcp, 0.0.0.0:15180->5180/tcp, :::15180->5180/tcp nginx-v1
Detailed mapping view:
docker inspect nginx-v1
Complete information will be displayed, in which the complete storage mount mapping can be seen in the "Mounts" section Condition.
Look directly under nginx-vol/logs on the host. You can see that the nginx running log in the container is automatically written to the storage of the external host.
ls -l nginx-vol/logs/ total 12 -rw-r--r-- 1 root root 1397 1月 8 15:08 access.log -rw-r--r-- 1 root root 4255 1月 8 15:59 error.log
Stop container:
docker stop nginx-v1
Delete container:
docker rm nginx-v1
docker-compose mode
Install docker-compose
apt-get install docker-compose
Write docker -compose.yml file
version: "3"
services:
nginx:
container_name: mynginx
image: nginx:test-v1
ports:
- 80:5180
volumes:
- ./nginx-vol/html:/data/web/html
- ./nginx-vol/logs:/var/log/nginx
- ./nginx-vol/conf.d:/etc/nginx/conf.d
restart: alwayscontainer_name: Specify the container name
image: The image to be used and the corresponding label
ports: Host port and container port mapping
volumes: External storage mount mapping
Start the container
docker-compose up -d Creating network "nginxtest_default" with the default driver Creating mynginx ... Creating mynginx ... done
View the container
docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 635e2999c825 nginx:test-v1 "/docker-entrypoint.…" 24 seconds ago Up 22 seconds 80/tcp, 0.0.0.0:80->5180/tcp, :::80->5180/tcp mynginx
You can see that the container is running according to the docker-compose.yml configuration, port, name , mounting are all normal. Accessing port 80 of the host corresponds to the container's 5180 service.
Stop the container
docker-compose down Stopping mynginx ... done Removing mynginx ... done Removing network nginxtest_default
As you can see, it is simpler to use docker-compose.
The above is the detailed content of What is the method to install nginx plug-in files under Docker?. For more information, please follow other related articles on the PHP Chinese website!