艰巨的任务: 每当我尝试停止或终止正在运行的容器时,都会收到Daemon拒绝的权限作为错误响应。
我刚刚开始通过使用Ubuntu18.04 VM学习如何使用docker。我是第一次运行容器。我无法停止它,但至少它正在运行。现在,当我尝试运行另一个图像“ furtuas / daisitory:image_available_first_ms”后,一切都变得更糟了。 两个容器正在运行,我无法停止其中的任何一个。 我尝试重新启动docker,但是容器仍在运行,区别在于localhost不再工作。 也许是因为我和以前一样在同一台主机上跑过
我对docker,ubuntu,终端等不熟悉。我希望为初学者提供详细的答案
$ docker info
Containers: 2
Running: 2
Paused: 0
Stopped: 0
Images: 8
Server Version: 18.09.1
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host 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: 9754871865f7fe2f4e74d43e2fc7ccd237edcbce
runc version: 96ec2177ae841256168fcf76954f7177af9446eb
init version: fec3683
Security Options:
apparmor
seccomp
Profile: default
Kernel Version: 4.15.0-43-generic
Operating System: Ubuntu 18.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 3.83GiB
Name: dai-2
ID: ULKT:IYPB:L6GI:VQWG:FZQX:J6G6:OWOU:DP5M:KQFC:PWBJ:HEMA:VDIT
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Username: icoe
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Product License: Community Engine
WARNING: No swap limit support
$ docker version
Client:
Version: 18.09.1
API version: 1.39
Go version: go1.10.6
Git commit: 4c52b90
Built: Wed Jan 9 19:35:31 2019
OS/Arch: linux/amd64
Experimental: false
Server: Docker Engine - Community
Engine:
Version: 18.09.1
API version: 1.39 (minimum version 1.12)
Go version: go1.10.6
Git commit: 4c52b90
Built: Wed Jan 9 19:02:44 2019
OS/Arch: linux/amd64
Experimental: false
$ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
furtuas/daisitory image_available_first_ms 64b3943856a0 6 days ago 660MB
icoe/dockerimageavailable first_ms 64b3943856a0 6 days ago 660MB
dockerimageavailable latest 64b3943856a0 6 days ago 660MB
my-maven latest 704b027074fb 6 days ago 660MB
dockerimagedetails latest 2da0a7987c2a 6 days ago 643MB
dockerimage latest af97e6623a8c 6 days ago 643MB
maven latest 3bc97dc2e7ba 3 weeks ago 832MB
java 8 d23bdf5b1b1b 2 years ago 643MB
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
66c6c49a95f4 furtuas/daisitory:image_available_first_ms "java -jar /car-pool…" 3 hours ago Up 3 hours first_ms_test
8e0646cc95f8 704b027074fb "java -jar /car-pool…" 6 days ago Up 6 days 0.0.0.0:8080->8080/tcp container_available
$ docker stop first_ms_test
Error response from daemon: cannot stop container: first_ms_test: Cannot kill container 66c6c49a95f499abeb62b1c02e7e9b8ce1739709bb2140ba7b1a61094a9d16f7: unknown error after kill: runc did not terminate sucessfully: container_linux.go:387: signaling init process caused "permission denied"
: unknown
$ docker container rm -f first_ms_test
Error response from daemon: Could not kill running container 66c6c49a95f499abeb62b1c02e7e9b8ce1739709bb2140ba7b1a61094a9d16f7, cannot remove - Cannot kill container 66c6c49a95f499abeb62b1c02e7e9b8ce1739709bb2140ba7b1a61094a9d16f7: unknown error after kill: runc did not terminate sucessfully: container_linux.go:387: signaling init process caused "permission denied"
: unknown
请帮助。
$ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
66c6c49a95f4 furtuas/daisitory:image_available_first_ms "java -jar /car-pool…" 3 hours ago Up 3 hours first_ms_test
8e0646cc95f8 704b027074fb "java -jar /car-pool…" 6 days ago Up 6 days 0.0.0.0:8080->8080/tcp container_available
注销虚拟机后,仍然是相同的响应:
$ docker stop 66c6c49a95f4
Error response from daemon: cannot stop container: 66c6c49a95f4: Cannot kill container 66c6c49a95f499abeb62b1c02e7e9b8ce1739709bb2140ba7b1a61094a9d16f7: unknown error after kill: runc did not terminate sucessfully: container_linux.go:387: signaling init process caused "permission denied"
: unknown
答案 0 :(得分:0)
您尝试过docker stop <container-id>
还是docker kill <container-id>
吗?
注意:使用docker ps -a
获取容器ID
还使用sudo
或以root
身份登录吗?
答案 1 :(得分:0)
我解决了,但不知道为什么。我想我是通过重新启动VM并使用以下命令重新启动docker来解决的
清除更改:$ sudo systemctl daemon-reload
重新启动Docker:$ sudo systemctl restart docker
答案 2 :(得分:0)
答案 3 :(得分:0)
使用技巧:
sudo killall docker-containerd-shim
从停止的容器中释放docker
,像这样
答案 4 :(得分:-1)
我有同样的问题。与apparmor服务存在一些冲突。在Ubuntu上,我可以通过重新安装apparmor来解决此问题:
- sudo apt-get purge apparmor
- sudo apt-get install apparmor
- sudo /etc/init.d/apparmor start