Record the pit I met with docker

• About build

$  docker build -t php-fpm:5.6 .
......
......
Step 10/10 : CMD ["php-fpm56"," --nodaemonize"]
 ---> Running in f30821a06bd9
Removing intermediate container f30821a06bd9
 ---> 2b718d2cc43b
Successfully built 2b718d2cc43b
Successfully tagged php-fpm:5.6
SECURITY WARNING: ... Windows ... '-rwxr-xr-x' permissions......  directories.

• About run

$ docker run -p 9056:9056 --name php5.6 -v D:\wwwroot:/data -d php-fpm:5.6
161d51b8d7cdbbebf4315d222d7553f0417cc1f357b2fa66e3f238ff773bb8ea
or 
$ docker run -p 9066:9056 --name YourName -v D:\www:/data -p 0.0.0.0:8066:80 -itd php-fpm:5.6
161d51b8d7cdbbebf4315d222d7553f0417cc1f357b2fa66e3f238ff773bb8ea

• About starting

Docker must be a "foreground process", otherwise docker will stop immediately after startup, there are usually several ways to deal with it. As follows:

1. When using php-fpm, add --nodaemonize parameters, such as: php-fpm56 --nodaemonize
2. Use top/tail type commands, such as: tail -f /dev/null
3. Install and use the supervisor tool, which is written in Python, so install Python and python-setuptools first.
4. When performing docker run, run a loop at the back, such as: docker run -d php-fpm:5.6 /bin/sh -c "while true; do echo 123; sleep 1; done"

• About network

In addition, the problem of network port mapping is sometimes normal, but it can not be accessed.

1. Replace 127.0.0.0:9000 in php-fpm.conf with [::]: 9056,such as:sed -i 's/127.0.0.1:9000/[::]:9056/' ./php-fpm.conf
2. We used to use php -S 127.0.0.1:80 before, and now we can: php -S [::]:80
3. In a word, it can't appear 127.0.0.1,5555.In this way, you can play: netstat -ano, docker port a3a0cfd83232, setenforce 0 and so on.

• About nginx

When nginx and php-fpm are not in one place, the configuration of nginx is different from the traditional configuration.

1. Do not use UNIX socket communication mode. You should use TCP socket mode.
2. Pay attention to configuring the script path, the SCRIPT_FILENAME parameter should take the file root path, such as:fastcgi_param SCRIPT_FILENAME /data/XXX/$real_script_name;, of course, you can also use $document_root, such as: fastcgi_param SCRIPT_FILENAME $document_root/$fastcgi_script_name;.

• Other misc

In the course of using, we will encounter various problems. What I write may not solve the problem, but at least it solves my problem.

1. On the problem of terminal Chinese chaotic code, you can usually set LANG environment variables to solve the problem, such as: export LANG= "zh_CN.UTF-8", set up, remember source or . ,Let it take effect.
2. As for the size of the mirror, like MYSQL's official mirror only a few hundred m, and we have a few g, why are there such a big difference? There are several common statements on the Internet. I tried to write all the RUN into 1 parts, and && or join, and finally clear the cache of Yum or apt-get, and it really reduced the image by several hundred M.
3. If you encounter such an error in the construction process，Error: Cannot retrieve repository metadata (repomd.xml) for repository: extras. Please verify its path and try again Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=extras&infra=stock error was 14: PYCURL ERROR 52 - "Empty reply from server" please re execute the build command.
4. As for macos running docker very slow, that's because of the hard disk I/O problem. The solution is to turn on the cached option. Such as：$ docker run -d --name yourname -v /local/webdir:/docker/webdir:cached 161d51b8d7cdb,Note that this option is only useful for macos, not for other platforms.
5. ERROR: for data_dir_web_1 Cannot start service web: error while creating mount source path '/host_mnt/d/data_dir': mkdir /host_mnt/d: f ile exists ERROR: for web Cannot start service web: error while creating mount source path '/host_mnt/d/data_dir': mkdir /host_mnt/d: file exist s ERROR: Encountered errors while bringing up the project. (Windows 10 and Docker 18.06.1-ce-win73 (19507)) 5.1 Restart the docker 5.2 The credentials for the mount have expired, reset them

6. About Centos 6 YUM invalidation. The error message: Loaded plugins: fastestmirror Setting up Install Process Determining fastest mirrors YumRepo Error: All mirror URLs are not using ftp, http[s] or file. Eg. Invalid release/repo/arch combination/ removing mirrorlist with no valid mirrors: /var/cache/yum/x86_64/6/base/mirrorlist.txt Error: Cannot find a valid baseurl for repo: base. If you encounter such an error, delete all the *.repo in /etc/yum.repos. D directory and then download a Tencent Cloud Yum repo

7. About files, *.tar.gz type files should use COPY instead of ADD.