Summary of error reporting problems in embedded porting docker

After a long time of transplant and query information, to solve the problems of embedded docker, a lot of online materials are all copy-paste copy-paste, can not find a suitable solution is very distressing, hope that they summed up some of the problem-solving experience to the majority of friends to reduce some burden!

The 1.standard file cannot be found:

Solution:

Tar zcvf xtables / usr/lib64/xtables cp xtables.tar / work/initramfs/ needs to be packaged and decompressed to another server with the same kernel and system.

two。 Iptables support is required to start docker. Porting iptables has an error when starting docker:

Solution:

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

3. Missing network connection module for 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. Entering the docker image file system does not match, pivot root invalid argumen

Solution:

Cat > / etc/systemd/system/docker.service.d/10-ramdisk.conf Environment=DOCKER_RAMDISK=true > EOF export DOCKER_RAMDISK=true drops the docker started by the method in kill, and restarts the OK.

After completing the above steps, the migrated docker can be used, but occasionally one of the following problems occurs.

If the missing DNS file content appears, send the resolv.conf file of any one to OK.

A module driver loaded after transplantation is attached: