docker容器启动失败

Catalogue

1. 错误一
1. 1.1. 报错信息
2. 1.2. 解决方法
2. 错误二
3. 错误四
4. 参考

错误一

报错信息

docker:Error response from daemon:endpoint with name monitor already exists in network host.

# docker info

Client:
 Debug Mode: false

Server:
 Containers: 250
  Running: 250
  Paused: 0
  Stopped: 0
 Images: 5
 Server Version: 19.03.8
 Storage Driver: overlay2
  Backing Filesystem: <unknown>
  Supports d_type: true
  Native Overlay Diff: true
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 7ad184331fa3e55e52b890ea95e65ba581ae3429
 runc version: dc9208a3303feef5b3839f4323d9beb36df0a9dd
 init version: fec3683
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 5.5.11-1.el7.elrepo.x86_64
 Operating System: CentOS Linux 7 (Core)
 OSType: linux
 Architecture: x86_64
 CPUs: 48
 Total Memory: 125.9GiB
 Name: d1a1e70b5f676226cb7ee2de95a79f79
 ID: V64J:KRRC:C6OI:PR2F:BIKW:XF26:YGPE:O2FW:B6NE:XASJ:TQMM:FUA7
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

解决方法

重启docker或者重启机器

1 2	docker network inspect <network name> docker network disconnect <network name> <container id/ container name>

1 2	docker network disconnect --force bridge monitor (这个好像也可以)

错误二

Error response from daemon:chown /etc/resolv.conf:operation not permitted

看报错是权限不足，ls -l /etv/resolv.conf,权限也没问题
有可能曾经用chattr命令锁定该文件了
查看文件权限

1 2	$ lsattr /etc/resolv.conf ----i----------- /etc/resolv.conf

i：设定文件不能被删除、改名、设定链接关系，同时不能写入或新增内容。

移除权限就可以了

1	$ chattr -i resolv.conf

错误四

container_linux.go:349: starting container process caused “process_linux.go:297:

1
2

# docker start a929869eecf0
Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:297: applying cgroup configuration for process caused \"failed to write 1 to memory.kmem.limit_in_bytes: write /sys/fs/cgroup/memory/kubepods/pod8811d42e-5e5e-11ec-b5c1-3e46384a3f85/a929869eecf0178555180396c57ea19a7f79298224ea0b5265c2585e6623a457/memory.kmem.limit_in_bytes: operation not supported\"": unknown

1
2
3

# cd /sys/fs/cgroup/memory/kubepods/pod8811d42e-5e5e-11ec-b5c1-3e46384a3f85

# mv 71de757cc45ec758615c2d06f335e47610327ba48824a02d0aa57e9c66b88d8c a929869eecf0178555180396c57ea19a7f79298224ea0b5265c2585e6623a457

容器启动过程中需要对某个文件进行读写，报错提示：操作不支持，应为该路径下没有这个文件，docker run里的文件名不对

解决方法，将机器上的文件名修改成docker run里的文件名

参考

https://www.cnblogs.com/yjt1993/p/13223897.html