完美解决systemctl start docker.service启动容器报错

安装docker容器后，启动时报错如下：

[root@joinApp2 ~]# systemctl start docker.service
Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details.
[root@joinApp2 ~]#
[root@joinApp2 ~]#
[root@joinApp2 ~]#
[root@joinApp2 ~]# systemctl status docker.service
● docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Thu 2016-02-25 17:26:11 CST; 16s ago
Docs:
http://docs.docker.com Process: 16384 ExecStart=/usr/bin/docker daemon $OPTIONS $DOCKER_STORAGE_OPTIONS $DOCKER_NETWORK_OPTIONS $ADD_REGISTRY $BLOCK_REGISTRY $INSECURE_REGISTRY (code=exited, status=1/FAILURE)
Main PID: 16384 (code=exited, status=1/FAILURE)
Feb 25 17:26:10 joinApp2 systemd[1]: Failed to start Docker Application Container Engine.
Feb 25 17:26:10 joinApp2 systemd[1]: Unit docker.service entered failed state.
Feb 25 17:26:10 joinApp2 systemd[1]: docker.service failed.
Feb 25 17:26:11 joinApp2 systemd[1]: docker.service holdoff time over, scheduling restart.
Feb 25 17:26:11 joinApp2 systemd[1]: start request repeated too quickly for docker.service
Feb 25 17:26:11 joinApp2 systemd[1]: Failed to start Docker Application Container Engine.
Feb 25 17:26:11 joinApp2 systemd[1]: Unit docker.service entered failed state.
Feb 25 17:26:11 joinApp2 systemd[1]: docker.service failed.

解决方法：

在/etc/docker/目录下创建daemon.json，添加如下内容：

{
"insecure-registries" : ["$your_registry:$your_registry_port"],
"registry-mirrors": ["$your_registry_url"],
"runtimes": {
"nvidia": {
"path": "nvidia-container-runtime",
"runtimeArgs": []
}
}
}

再运行systemctl start docker.service命令进行重启即可。

完美解决systemctl start docker.service启动容器报错相关推荐

docker 启动容器报错及解决办法
docker 启动容器报错:Error response from daemon: oci runtime error: container_linux.go:247: starting contai ...
在docker中启动服务报错：New main PID 558 does not belong to service
在docker中启动服务报错: New main PID 558 does not belong to service, and PID file is not owned by root. Refu ...
ssm启动不报错_解决idea导入ssm项目启动tomcat报错404的问题
用idea写ssm项目,基于之前一直在用spring boot 对于idea如何运行ssm花费了一番功夫启动tom act一直在报404 我搜了网上各种解决办法都不行,花费一天多的时间解决不了就是 ...
如何覆盖docker.service文件中的配置，解决一次docker.service启动不成功的问题
一.问题服务器重启之后systemctl restart docker始终不成功,网上各种方法都试了一遍,依然没有解决问题. systemctl restart docker 报错信息: [root ...
docker之阿里云centos 7.x 启动容器报错处理办法
最近阿里云服务器(操作系统centOS 7.x) 安装docker,参照阿里云帮助文档https://help.aliyun.com/document_detail/51853.html?spm=a2 ...
关闭或启动linux防火墙后，docker启动容器报错
# docker启动报错 # 解决办法:重建docker0网络恢复 #按照进程名杀死docker进程 [root@localhost mysqlconf]# pkill docker #清空防火墙规则 ...
win10 docker运行sqlserver容器报错：This program requires a machine with at least 2000 megabytes of memory.
前言由于docker安装sqlserver需要至少2G的内存,而docker容器默认内存不到2G,所以启动会遇到内存不足的错误. 因为 windows docker 是在Hyper-V隔离沙箱中运行 ...
解决Client.Timeout exceeded while awaiting headers报错
在进行docker pull 拉取镜像时,出现过下面的错误: net/http: request canceled while waiting for connection (Client.Timeo ...
探讨Docker不能启动容器的原因和解决方法
Docker是一种虚拟化容器技术,能够提供一种快速.高效.可靠的容器化解决方案,广泛应用于云计算.大数据.微服务架构等场景.但是,有时候在使用Docker的过程中,我们会遇到一些问题,比如容器不能启动 ...

完美解决systemctl start docker.service启动容器报错

完美解决systemctl start docker.service启动容器报错相关推荐

最新文章

热门文章