moby: can not remove a container

can not stop container using docker rm -f loki-server or sudo kill -9

infra@huangchengkai-FFFFFFF:~$ docker rm -f loki-server
Error response from daemon: Could not kill running container 455980de7979471a2d1f869068f89854f13a6e6d7f04865a4cb87bc66cef3e0b, cannot remove - Cannot kill container 455980de7979471a2d1f869068f89854f13a6e6d7f04865a4cb87bc66cef3e0b: unknown error after kill: runc did not terminate sucessfully: container_linux.go:378: signaling init process caused "permission denied"
: unknown
infra@huangchengkai-FFFFFFF:~$ ps aux | grep loki
infra    15535 10.2 53.8 41371944 35538272 ?   Ssl  1月02 126:21 /bin/loki -config.file=/etc/loki/local-config.yaml
infra    20376  0.0  0.0  17480   812 pts/1    S+   16:15   0:00 grep loki
infra@huangchengkai-FFFFFFF:~$ sudo kill -9 15535
kill: (15535): Permission denied
infra@huangchengkai-FFFFFFF:~$

Describe the results you received:

Describe the results you expected:

Additional information you deem important (e.g. issue happens only occasionally):

Output of docker version:

infra@huangchengkai-FFFFFFF:~$ docker version
Client:
 Version:           18.09.1-rc1
 API version:       1.39
 Go version:        go1.10.5
 Git commit:        bca0068
 Built:             Fri Dec  7 05:30:15 2018
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.1-rc1
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.5
  Git commit:       bca0068
  Built:            Fri Dec  7 04:59:10 2018
  OS/Arch:          linux/amd64
  Experimental:     false
infra@huangchengkai-FFFFFFF:~$

Output of docker info:

infra@huangchengkai-FFFFFFF:~$ docker info
Containers: 1
 Running: 1
 Paused: 0
 Stopped: 0
Images: 11
Server Version: 18.09.1-rc1
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: de1f167ab96338a9f5c2b17347abf84bdf1dd411
runc version: 10d38b660a77168360df3522881e2dc2be5056bd
init version: fec3683
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.18.0-13-generic
Operating System: Ubuntu 18.10
OSType: linux
Architecture: x86_64
CPUs: 24
Total Memory: 62.88GiB
Name: huangchengkai-FFFFFFF
ID: FSA4:O4Y4:MZDD:NZ7F:DQZK:SD5U:K76H:J6HV:RJTQ:IPBP:GD2A:JTNW
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 xxxx
 127.0.0.0/8
Registry Mirrors:
 https://xxxxx/
Live Restore Enabled: false
Product License: Community Engine

WARNING: No swap limit support

uname -a

Linux huangchengkai-FFFFFFF 4.18.0-13-generic #14-Ubuntu SMP Wed Dec 5 09:04:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

About this issue

Original URL
State: open
Created 5 years ago
Comments: 15 (6 by maintainers)

Most upvoted comments

sudo killall docker-containerd-shim

This seems to do the trick. But can someone please explain to me why this is happening.

parthvenkatesh on Mar 15, 2019

I have the same issue with ubuntu 18.04. sudo does not work. neither does docker stop or docker kill.

runc did not terminate sucessfully: container_linux.go:387: signaling init process caused “permission denied”

pblin on Mar 14, 2019

I had the same issue. Rebooting the server (not just the VM if running in a VM) solved the issue…

cesar3030 on Feb 18, 2019

i also run into the same issue with apparmor

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

[260156.934273] audit: type=1400 audit(1549276633.864:254875): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=3457 comm=504D322076332E322E343A20476F64 requested_mask="tracedby" denied_mask="tracedby" peer="docker-default"

yuklia on Feb 4, 2019

I’m also running into the same issue.

Error response from daemon: cannot stop container: e39c554e9d15: Cannot kill container e39c554e9d15fd1e48d28286fd3ebd12e81c43b2cbf60a624242fa779809657a: unknown error after kill: runc did not terminate sucessfully: container_linux.go:387: signaling init process caused "permission denied"
: unknown

Containers: 2
 Running: 2
 Paused: 0
 Stopped: 0
Images: 9
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: 2
Total Memory: 3.759GiB
Name: cld06
ID: SKQP:CJDY:ZRM5:EDTR:WQVI:PYI3:Q6GQ:ZQ3Q:EOT2:APRG:RLHU:6LQR
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
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

Torgian on Jan 24, 2019

Yes it made it into 18.09.1, so wondering what’s remaining that causes this issue

@kolyshkin @cyphar any ideas?

thaJeztah on Jan 23, 2019