Embedded transplant docker error problem (summary)

After a long period of transplantation and information query, I was able to solve the problems with embedded docker. A lot of information on the Internet is copy and paste, and it is very distressing to not be able to find a suitable solution. I hope that some of the experience I have summarized in solving problems can reduce some burdens for my friends!

1.standard file not found:

Solution:

tar zcvf xtables /usr/lib64/xtables
cp xtables.tar /work/initramfs/

Need to go to another server with the same kernel and system to package and decompress

2. iptables support is required to start docker. Transplant iptables and start docker error:

Solution:

docker --iptables=false
nohup docker --iptables=false >/1.txt 2>&1 & (background start)

3. Lack of network connection module of NAT firewall:

Solution:

 modprobe iptable_nat

4. There is a problem entering the docker image, the veth module is missing, load it directly

Solution:

 modprobe veth

5. The file system of the docker image does not match, pivot root invalid arguments

Solution:

cat >/etc/systemd/system/docker.service.d/10-ramdisk.conf <<EOF
> [Service]
> Environment=DOCKER_RAMDISK=true
> EOF
 export DOCKER_RAMDISK=true
Kill the docker started by the method just now and restart it.

Two additional points: After completing the above steps, the transplanted Docker can be used, but occasionally the following problem may occur.

If there is missing DNS file content, just transfer the resolv.conf file of any machine and it will be OK.

Attached is a picture of the module driver loaded after transplantation:

The above is the full content of this article. I hope it will be helpful for everyone’s study. I also hope that everyone will support 123WORDPRESS.COM.