<span id="Label3"></p><p><p>found that a Docker container could not be connected remotely, using Docker stop could not stop, and later found that all the Docker containers could not be connected and then restarted Docker to see if it could return to normal, the system is centos 7 start command systemctl start Docker keeps stuck, kill the Docker process docker-d start again or fail to start on the web by deleting rm-fr/var/lib/docker/* all content</p></p><p><p>I'm Docker-d. I want to delete the Docker container I press CTRL + C should stop the process, but never thought that Ctrl + C seems to have not been effective and can not be deleted/var/lib/docker/inside the file Office display resource consumption</p></p><p><p>650) this.width=650; "src=" Http://s5.51cto.com/wyfs02/M00/83/2C/wKiom1dsjoaxBhwMAAASEZrfnXE675.png-wh_500x0-wm_3 -wmp_4-s_4169014458.png "title=" docker1.png "alt=" wkiom1dsjoaxbhwmaaasezrfnxe675.png-wh_50 "/></p></p><p><p>Execute the command to view the resource consumption is also stuck there.</p></p> <blockquote> <blockquote> <pre class="brush:bash;toolbar:false">Fuser-cm/var/lib/docker/devicemapper</pre> <p><br></p> </blockquote> </blockquote><p><p>See how two Docker processes kill and kill, which is how the zombie process restarts the server, and what kills the parent process has been tried.</p></p><p><p>Start Docker again with command Systemctl start Docker does not start, start with docker-d</p></p><p><p><strong>Docker-d</strong></p></p><p><p>Error message<strong><br></strong>Warning: '-d ' is deprecated, it'll be removed Soon. See Usage.<br>warn[0000] please use ' Docker daemon ' instead.<br>warn[0000] Usage of loopback devices is strongly discouraged for production Use. Please use the ' –storage-opt Dm.thinpooldev ' or use the ' man Docker ' to Refer-dm.thinpooldev Section.<br>info[0000] [graphdriver] using prior storage driver "devicemapper"<br>info[0000] Firewalld Running:false<br>fata[0000] Error starting Daemon:error initializing network controller:error creating default "bridge" network:failed t O Parse pool request for address space "localdefault" pool "" Subpool "": could not find a available predefined network</p></p><p><p>Error initiating daemon: error initializing network controller: creating default "bridge" network Error: Unable to resolve pool request address space "localdefault" Pool "sub-library": Unable to find an available pre-defined network</p></p><p><p>The solution is found in the gooogle of the domestic search is the same to find out the solution is the same point can not solve the problem!</p></p><p><p>It's still Google.</p></p><p><p>Workaround:</p></p> <blockquote> <blockquote> <pre class="brush:bash;toolbar:false">Docker-d–bip=172.17.42.1/16</pre> <p><br></p> </blockquote> </blockquote><p><p>Specify a docker network segment to start successfully</p></p> <blockquote> <blockquote> <p>650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/83/2B/wKioL1dsjtfR9CcDAACaU8oSBvE944.png-wh_500x0-wm_3 -wmp_4-s_3570355210.png "title=" docker3.png "alt=" wkiol1dsjtfr9ccdaacau8osbve944.png-wh_50 "/></p> </blockquote> </blockquote><p><p><br></p></p><p><p>This article is from the "TYP" blog, make sure to keep this source http://typ520.blog.51cto.com/9201592/1792448</p></p><p><p>Docker Start Network Error solution</p></p></span>
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.
A Free Trial That Lets You Build Big!
Start building with 50+ products and up to 12 months usage for Elastic Compute Service