Docker服务不启动 [英] Docker service does not start

问题描述

码头工人目前正在困扰我。我遵循这些说明，以便在由strato.de托管的运行Ubuntu 14.04的虚拟服务器上安装Docker。

  wget -qO- https://get.docker.com/ | sh 
  

执行此行直接导致此错误消息：

  modprobe：ERROR：../libkmod/libkmod.c:507 kmod_lookup_alias_from_builtin_file（）无法打开内置文件'/lib/modules/3.13.0-042stab092.3 /modules.builtin.bin'modprobe：FATAL：未找到模块aufs。 
警告：linux-image-extra-virtual 
包不支持当前内核。我们没有AUFS支持。考虑安装包linux-image-virtual内核和linux-image-extra-virtual以支持AUFS。 
  

安装完成后，我安装了上述两个包。现在我的问题是我不能让码头运行。

  service docker start 
  

结果：

  start：Job无法启动
 
 
 docker -d 
  

/ p>

  INFO [0000] + job serveapi（unix：///var/run/docker.sock）
 INFO [ 0000]在unix上侦听HTTP（/var/run/docker.sock）
 ERRO [0000]在此主机上未找到支持的文件系统。请确保内核足够新，并加载覆盖支持。 
 INFO [0000] +作业init_networkdriver（）
 WARN [0000]运行modprobe bridge nf_nat失败并显示消息：，错误：退出状态1 
包未安装
 INFO [0000] -job init_networkdriver（）= ERR（1）
 FATA [0000]由于错误关闭守护程序：未安装包
  

和

  docker运行hello-world 
  pre> 
 
 
结果
  FATA [0000]发布http： //var/run/docker.sock/v1.18/containers/create：dial unix /var/run/docker.sock：没有这样的文件或目录。您是否尝试连接到不带TLS的启用TLS的守护程序？有没有人知道可能丢失什么依赖关系的线索？
  
还有什么可能出了问题？是否有任何港口码头提供的日志？
 
 
 
我正在寻找解决方案，但找不到解决方案。
 
 
 
只是提到这是一个新的Ubuntu 14.04设置。我没有安装任何其他服务，除了java。而我需要停靠码头的原因是使用sharelatex的dockerimage。
 
 
 
感谢任何帮助！
解决方案
这是我尝试/发现的，希望它会节省你一些时间，甚至帮你解决它。
 
 
 
 Docker的下载脚本正试图通过 uname -r 来识别内核为您的主机安装正确的内核演员。 
 
 
 
我怀疑有两个问题：
 
 
 
 
 
我的（united-hoster.de）并且您的提供商可能会为虚拟主机使用定制的内核映像（例如 3.13.0-042stab108.2 ）。由于该脚本在名称中明确寻找 -generic ，查找失败。
 
 
虽然命名问题很容易修复，我无法使用我的主机的自定义内核安装通用内核附加功能。似乎使用升级内核也不起作用，因为它会影响同一物理机器上的所有用户/ vHost。这是因为内核是共享的（在一些支持票证明）。
 
 
 
 
 
要绕过那个.. 
 
 
 
 
 
我跳过它，希望Docker在没有AUFS支持的情况下工作，但没有。
 
 
我试图强制Docker要使用devicemapper ，但无效。
 
 
 
 
 
我看到两个选项：获取专用的主机，所以你可以混淆内核和文件系统，或者至少让Docker安装程序或手动安装二进制文件。
 
docker is gigving me a hard time currently. I followed these instructions in order to install docker on my virtual server running Ubuntu 14.04 hosted by strato.de.
wget -qO- https://get.docker.com/ | sh
Executing this line runs me directly into this error message:
modprobe: ERROR: ../libkmod/libkmod.c:507 kmod_lookup_alias_from_builtin_file() could not open builtin file '/lib/modules/3.13.0-042stab092.3/modules.builtin.bin'modprobe: FATAL: Module aufs not found.
Warning: current kernel is not supported by the linux-image-extra-virtual
 package.  We have no AUFS support.  Consider installing the packages  linux-image-virtual kernel and linux-image-extra-virtual for AUFS support.
After the installation was done, I installed the two mentioned packages. Now my problem is that I can't get docker to run.
service docker start
results in:
start: Job failed to start


docker -d
results in
INFO[0000] +job serveapi(unix:///var/run/docker.sock)
INFO[0000] Listening for HTTP on unix (/var/run/docker.sock)
ERRO[0000] 'overlay' not found as a supported filesystem on this host. Please ensure kernel is new enough and has overlay support loaded.
INFO[0000] +job init_networkdriver()
WARN[0000] Running modprobe bridge nf_nat failed with message: , error: exit status 1
package not installed
INFO[0000] -job init_networkdriver() = ERR (1)
FATA[0000] Shutting down daemon due to errors: package not installed
and
docker run hello-world
results in
FATA[0000] Post http:///var/run/docker.sock/v1.18/containers/create: dial unix /var/run/docker.sock: no such file or directory. Are you trying to connect to a TLS-enabled daemon without TLS?
Does anybody have a clue about what dependencies could be missing? What else could have gone wrong? Are there any logs which docker provides?

I'm searching back and forth for a solution, but couldn't find one.

Just to mention this is a fresh Ubuntu 14.04 setup. I didn't install any other services except for java. And the reason why I need docker is for using the dockerimage of sharelatex.

I'm thankful for any help!
解决方案
Here's what I tried/found out, hoping that it will save you some time or even help you solve it.

Docker's download script is trying to identify the kernel through uname -r to be able to install the right kernel extras for your host. 

I suspect two problems:


My (united-hoster.de) and probably your provider use customized kernel images (eg. 3.13.0-042stab108.2) for virtual hosts. Since the script is explicitly looking for -generic in the name, the lookup fails.
While the naming problem would be easy to fix, I wasn't able to install the generic kernel extras with my hoster's custom kernel. It seems like using a upgrading the kernel does not work either, since it would affect all users/vHosts on the same physical machine. This is because the kernel is shared (stated in some support ticket).


To get around that ..


I skipped it, hoping that Docker would work without AUFS support, but it didn't.
I tried to force Docker to use devicemapper instead, but to no avail.


I see two options: get a dedicated host so you can mess with kernels and filesystems or a least let the docker installer do it or install the binaries manually.

                        
这篇关于Docker服务不启动的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！