Debian

在 Debian 上安裝 docker-ce 時出錯

  • May 4, 2018

我在伺服器上安裝 docker 時遇到問題:

   user@server:/# apt-get install docker-ce
   Reading package lists... Done
   Building dependency tree
   Reading state information... Done
   The following NEW packages will be installed:
     docker-ce
   0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
   Need to get 0 B/30.2 MB of archives.
   After this operation, 152 MB of additional disk space will be used.
   debconf: unable to initialize frontend: Dialog
   debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76, <> line 1.)
   debconf: falling back to frontend: Readline
   Selecting previously unselected package docker-ce.
   (Reading database ... 25607 files and directories currently installed.)
   Preparing to unpack .../docker-ce_17.12.0~ce-0~debian_amd64.deb ...
   Unpacking docker-ce (17.12.0~ce-0~debian) ...
   Processing triggers for systemd (215-17+deb8u7) ...
   Setting up docker-ce (17.12.0~ce-0~debian) ...
   Job for docker.service failed. See 'systemctl status docker.service' and 'journalctl -xn' for details.
   invoke-rc.d: initscript docker, action "start" failed.
   dpkg: error processing package docker-ce (--configure):
    subprocess installed post-installation script returned error exit status 1
   Processing triggers for systemd (215-17+deb8u7) ...
   Errors were encountered while processing:
    docker-ce
   E: Sub-process /usr/bin/dpkg returned an error code (1)
   user@server:/# journalctl -xn
   -- Logs begin at Thu 2018-02-15 11:45:24 CET, end at Thu 2018-02-15 12:05:46 CET. --
   Feb 15 12:05:46 git systemd[1]: Unit docker.service entered failed state.
   Feb 15 12:05:46 git systemd[1]: docker.service holdoff time over, scheduling restart.
   Feb 15 12:05:46 git systemd[1]: Stopping Docker Application Container Engine...
   -- Subject: Unit docker.service has begun shutting down
   -- Defined-By: systemd
   -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
   --
   -- Unit docker.service has begun shutting down.
   Feb 15 12:05:46 git systemd[1]: Stopping Docker Socket for the API.
   -- Subject: Unit docker.socket has begun shutting down
   -- Defined-By: systemd
   -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
   --
   -- Unit docker.socket has begun shutting down.
   Feb 15 12:05:46 git systemd[1]: Starting Docker Socket for the API.
   -- Subject: Unit docker.socket has begun with start-up
   -- Defined-By: systemd
   -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
   --
   -- Unit docker.socket has begun starting up.
   Feb 15 12:05:46 git systemd[1]: Listening on Docker Socket for the API.
   -- Subject: Unit docker.socket has finished start-up
   -- Defined-By: systemd
   -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
   --
   -- Unit docker.socket has finished starting up.
   --
   -- The start-up result is done.
   Feb 15 12:05:46 git systemd[1]: Starting Docker Application Container Engine...
   -- Subject: Unit docker.service has begun with start-up
   -- Defined-By: systemd
   -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
   --
   -- Unit docker.service has begun starting up.
   Feb 15 12:05:46 git systemd[1]: docker.service start request repeated too quickly, refusing to start.
   Feb 15 12:05:46 git systemd[1]: Failed to start Docker Application Container Engine.
   -- 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.
   Feb 15 12:05:46 git systemd[1]: Unit docker.service entered failed state.

系統資訊:

PRETTY_NAME="Debian GNU/Linux 8 (jessie)"
NAME="Debian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=debian

核心:

2.6.32-042stab127.2

Docker 的安裝文件中,所需的最低核心是 3.10,並且您正在執行 2.6.32-042stab127.2 和通常執行 3.16 的 Debian 8。

它似乎是一個 OpenVZ 核心。從它的首頁上看,它已經是一個基於容器的虛擬化。所以這意味著在容器中執行一個容器。雖然這是可能的,但也有一些限制,尤其是對於像 Docker 這樣用於執行和控制容器的應用程序。

這是使環境無法執行 Docker 的兩個原因。您應該嘗試使用更常見的虛擬化的提供商。如果您可以選擇您的核心(甚至在提供的列表中)或更改它,那應該是一個合適的選擇。當然,裸機也是一個合適的選擇。

引用自:https://unix.stackexchange.com/questions/424357