Docker 自定義網橋後,無法正常啟動問題
週末用docker設定固定ip之後,再次輸入啟動命令之後,都報錯誤,具體如下:
root@ubuntu:~# docker version
Client:
Version: 1.12.6
API version: 1.24
Go version: go1.6.2
Git commit: 78d1802
Built: Tue Jan 31 23:35:14 2017
OS/Arch: linux/amd64
Cannot connect to the Docker daemon. Is the docker daemon running on this host?
root@ubuntu:~# service docker start
Job for docker.service failed because the control
process exited with error code. See "systemctl status
docker.service" and "journalctl -xe" for details.
root@ubuntu:~# systemctl status docker.service
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: e
Active: failed (Result: exit-code) since Mon 2017-03-06 16:59:47 CST; 29s ago
Docs: https://docs.docker.com
Process: 9757 ExecStart=/usr/bin/dockerd -H fd:// $DOCKER_OPTS (code=exited, s
Main PID: 9757 (code=exited, status=1/FAILURE)
Mar 06 16:59:47 ubuntu dockerd[9757]: time="2017-03-06T16:59:47.326263971+08:00"
Mar 06 16:59:47 ubuntu dockerd[9757]: time="2017-03-06T16:59:47.326847904+08:00"
Mar 06 16:59:47 ubuntu dockerd[9757]: time="2017-03-06T16:59:47.327433829+08:00"
Mar 06 16:59:47 ubuntu dockerd[9757]: ........time="2017-03-06T16:59:47.34000826
Mar 06 16:59:47 ubuntu dockerd[9757]: time="2017-03-06T16:59:47.378659103+08:00"
Mar 06 16:59:47 ubuntu dockerd[9757]: time="2017-03-06T16:59:47.401407972+08:00"
Mar 06 16:59:47 ubuntu systemd[1]: docker.service: Main process exited, code=exi
Mar 06 16:59:47 ubuntu systemd[1]: Failed to start Docker Application Container
Mar 06 16:59:47 ubuntu systemd[1]: docker.service: Unit entered failed state.
Mar 06 16:59:47 ubuntu systemd[1]: docker.service: Failed with result 'exit-code
root@ubuntu:~# journalctl -xe
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.socket has finished starting up.
--
-- The start-up result is done.
Mar 06 17:07:38 ubuntu systemd[1]: Starting Docker Application Container Engine.
-- Subject: Unit docker.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has begun starting up.
Mar 06 17:07:38 ubuntu dockerd[9944]: time="2017-03-06T17:07:38.217987846+08:00"
Mar 06 17:07:39 ubuntu kernel: audit: type=1400 audit(1488791259.311:58): apparm
Mar 06 17:07:39 ubuntu audit[9980]: AVC apparmor="STATUS" operation="profile_rep
Mar 06 17:07:39 ubuntu dockerd[9944]: time="2017-03-06T17:07:39.327277215+08:00"
Mar 06 17:07:39 ubuntu dockerd[9944]: time="2017-03-06T17:07:39.330977072+08:00"
Mar 06 17:07:39 ubuntu dockerd[9944]: time="2017-03-06T17:07:39.331639712+08:00"
Mar 06 17:07:39 ubuntu dockerd[9944]: time="2017-03-06T17:07:39.332261285+08:00"
Mar 06 17:07:39 ubuntu dockerd[9944]: ........time="2017-03-06T17:07:39.34310685
Mar 06 17:07:39 ubuntu dockerd[9944]: time="2017-03-06T17:07:39.365163611+08:00"
Mar 06 17:07:39 ubuntu dockerd[9944]: time="2017-03-06T17:07:39.388542420+08:00"
Mar 06 17:07:39 ubuntu systemd[1]: docker.service: Main process exited, code=exi
Mar 06 17:07:39 ubuntu systemd[1]: Failed to start Docker Application Container
-- Subject: Unit docker.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has failed.
--
-- The result is failed.
Mar 06 17:07:39 ubuntu systemd[1]: docker.service: Unit entered failed state.
Mar 06 17:07:39 ubuntu systemd[1]: docker.service: Failed with result 'exit-code
通過查詢系統日誌:
root@ubuntu:/var/log# cd
root@ubuntu:~# cd /var/log
root@ubuntu:/var/log# ls
alternatives.log dpkg.log lastlog vmware-vmsvc.log
apt faillog lightdm wtmp
auth.log fontconfig.log speech-dispatcher Xorg.0.log
bootstrap.log fsck syslog Xorg.0.log.old
btmp gpu-manager.log syslog.1 yum.log
cups hp unattended-upgrades
dist-upgrade installer upstart
dmesg kern.log vmware
root@ubuntu:/var/log# cat syslog
//或者通過
root@ubuntu:/var/log# vim syslog
可以看到具體錯誤資訊如下:
Mar 6 17:07:38 ubuntu dockerd[9944]: time="2017-03-06T17:07:38.217987846+08:00" level=info msg="libcontainerd: new containerd process, pid: 9960"
Mar 6 17:07:39 ubuntu kernel: [21284.569382] audit: type=1400 audit(1488791259.311:58): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="docker-default" pid=9980 comm="apparmor_parser"
Mar 6 17:07:39 ubuntu dockerd[9944]: time="2017-03-06T17:07:39.327277215+08:00" level=info msg="[graphdriver] using prior storage driver \"aufs\""
Mar 6 17:07:39 ubuntu dockerd[9944]: time="2017-03-06T17:07:39.330977072+08:00" level=info msg="Graph migration to content-addressability took 0.00 seconds"
Mar 6 17:07:39 ubuntu dockerd[9944]: time="2017-03-06T17:07:39.331639712+08:00" level=warning msg="Your kernel does not support swap memory limit."
Mar 6 17:07:39 ubuntu dockerd[9944]: time="2017-03-06T17:07:39.332261285+08:00" level=info msg="Loading containers: start."
Mar 6 17:07:39 ubuntu dockerd[9944]: ........time="2017-03-06T17:07:39.343106854+08:00" level=info msg="Firewalld running: false"
//注意下面這段錯誤資訊
Mar 6 17:07:39 ubuntu dockerd[9944]: time="2017-03-06T17:07:39.365163611+08:00" level=warning msg="could not create bridge network for id d6f9d6b857030363444f5dc8fcc8b131831f13b440fa317e10f82bf07e6a8f5d bridge name docker_new0 while booting up from persistent state: bridge device with non default name docker_new0 must be created manually"
Mar 6 17:07:39 ubuntu dockerd[9945]: time="2017-03-06T17:07:39.388542420+08:00" level=fatal msg="Error starting daemon: Error initializing network controller: Error creating default \"bridge\" network: bridge device with non default name docker_new0 must be created manually"
Mar 6 17:07:39 ubuntu systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Mar 6 17:07:39 ubuntu systemd[1]: Failed to start Docker Application Container Engine.
Mar 6 17:07:39 ubuntu systemd[1]: docker.service: Unit entered failed state.
Mar 6 17:07:39 ubuntu systemd[1]: docker.service: Failed with result 'exit-code'.
~
方法一:新建自定義網橋docker_new0
brctl addbr docker_new0
方法二:修改/etc/default/docker檔案
修改成
這樣再次登入使用的就是預設網橋docker0了。
再次執行docker啟動命令正常:
sudo systemctl start docker
該問題報出的異常有如下這些:
//錯誤資訊一
Cannot connect to the Docker daemon. Is the docker daemon running on this host?
//錯誤資訊二
Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details.
作者:jiankunking 出處:http://blog.csdn.net/jiankunking
相關文章
- mongoDB非正常關閉後無法啟動問題MongoDB
- qt6 QtOpcUa無法正常啟動問題QT
- 懷疑私網網路卡多播問題導致crs無法正常啟動
- MAC電腦出現問題,無法正常啟動怎麼辦?Mac
- 解決hyper v導致docker無法啟動問題Docker
- 修改daemon.json重新載入後docker無法啟動問題記錄JSONDocker
- 資料庫shutdown之後無法啟動的問題資料庫
- 關於win平臺下,oracleservice<sid>無法正常啟動的問題Oracle
- Eclipse非正常死亡後無法啟動的處理方法Eclipse
- docker 不能正常啟動Docker
- 針對VM從掛機-啟動後,docker相關服務的無法使用問題!Docker
- 解決ASM無法啟動問題ASM
- mac下mysql無法啟動問題MacMySql
- docker Redis 自定義配置檔案啟動DockerRedis
- win10 ituns無法正常啟動怎麼辦_win10 ituns無法正常啟動解決方法Win10
- Webphser Applcation Server Dmgr無法正常啟動WebAPPServer
- 怎麼解決SOLIDWORKS文件無法正常開啟的問題!Solid
- 解決vscode安裝後無法啟動的問題VSCode
- 【Python】jupyter notebook啟動後網頁無法訪問Python網頁
- Oracle Haip無法啟動問題學習OracleAI
- ASM無法啟動的問題分析(一)ASM
- ASM無法啟動的問題分析(二)ASM
- LnixuAS3Mysql無法啟動問題S3MySql
- 運維該如何解決 Linux 伺服器重啟後命令無法正常使用的問題?運維Linux伺服器
- ES和kibana docker啟動成功後瀏覽器卻顯示無法訪問Docker瀏覽器
- 【ASM】ASM啟動無法找到spfile問題原因ASM
- 某個Eclipse無法啟動的問題Eclipse
- C++6.0(應用程式無法正常啟動0xc0000142) 關於win10週年版更新後無法正常使用vc6.0問題的解決方法C++Win10
- win10安裝程式無法正常啟動怎麼辦_win10安裝程式無法正常啟動如何解決Win10
- 適合最新版docker自定義啟動配置Docker
- MacOS Monterey 12.0.1 下無法正常啟動 vagrant upMac
- 學習四:jobtracker和tasktracker無法正常啟動
- 主機名改名後oracle database control 無法啟動的問題OracleDatabase
- Windows10安裝vc6.0綠色版後無法正常啟動,提示0x0000142的問題。Windows
- open in live server無法正常開啟Server
- win10系統映象安裝後無法正常啟動怎麼解決Win10
- 使用Docker部署Nacos 2.3.2開啟鑑權後無法訪問控制檯Docker
- 解決ORACLE無法啟動安裝的問題Oracle