Docker:未安装设备cgroup(Ubuntu 16.04)

时间:2017-03-05 18:16:14

标签: docker ubuntu-16.04

我正在尝试在远程网络服务器上的Ubuntu 16.04上安装docker。但是,我收到一个令我很沮丧的错误。我已经很多次安装了docker,也就是在这个操作系统上,但这种情况从未发生过。

我无法安装docker-engine时遇到sudo apt-get install -y docker-engine

~# systemctl status docker.service
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since So 2017-03-05 17:47:20 CET; 32s ago
     Docs: https://docs.docker.com
 Main PID: 18194 (code=exited, status=1/FAILURE)

dockerd[18194]: time="2017-03-05T17:47:20.567753592+01:00" level=error msg="'overlay' not found as a supported filesystem on this host. Please e
dockerd[18194]: time="2017-03-05T17:47:20.569299675+01:00" level=error msg="'overlay' not found as a supported filesystem on this host. Please e
dockerd[18194]: time="2017-03-05T17:47:20.591796895+01:00" level=info msg="Graph migration to content-addressability took 0.00 seconds"
dockerd[18194]: time="2017-03-05T17:47:20.592394882+01:00" level=warning msg="Your kernel does not support oom control"
dockerd[18194]: time="2017-03-05T17:47:20.592410368+01:00" level=warning msg="Your kernel does not support memory swappiness"
dockerd[18194]: time="2017-03-05T17:47:20.592421460+01:00" level=warning msg="Your kernel does not support kernel memory limit"
dockerd[18194]: time="2017-03-05T17:47:20.592427398+01:00" level=warning msg="Unable to find cpu cgroup in mounts"
dockerd[18194]: time="2017-03-05T17:47:20.592458649+01:00" level=warning msg="Unable to find cpuset cgroup in mounts"
dockerd[18194]: time="2017-03-05T17:47:20.592490516+01:00" level=warning msg="mountpoint for pids not found"
dockerd[18194]: Error starting daemon: Devices cgroup isn't mounted

我在组中添加了root,同时我找到了将GRUB_CMDLINE_LINUX="cgroup_enable=memory swapaccount=1"添加到文件/ etc / default / grub的建议,但该文件不存在!

我也试过sudo apt-get install cgroupfs-mount但没有成功: - (

感谢您的帮助!

1 个答案:

答案 0 :(得分:8)

所以,伙计们。不幸的是,没有解决方案。原因是远程Web服务器的体系结构,即托管VM。 我的提供商告诉我所有虚拟机在一个环境中使用相同的内核,因此dokker无法访问它。

现在唯一的选择是切换到另一台服务器。