moby: [1.8.0-rc1] Cannot kill or stop daemon containers before a reboot

Description of problem: Cannot kill or stop daemon containers on the current docker experimental

docker version:

Client:
 Version:      1.8.0-rc1
 API version:  1.20
 Go version:   go1.4.2
 Git commit:   4f1c66a
 Built:        Sat Jul 25 05:54:28 UTC 2015
 OS/Arch:      linux/amd64

Server:
 Version:      1.8.0-rc1
 API version:  1.20
 Go version:   go1.4.2
 Git commit:   4f1c66a
 Built:        Sat Jul 25 05:54:28 UTC 2015
 OS/Arch:      linux/amd64

docker info:

Containers: 2
Images: 3
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 7
 Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.16.0-41-generic
Operating System: Ubuntu 14.04 LTS
CPUs: 1
Total Memory: 3.66 GiB
Name: mechjeb
ID: 5OBA:PPB3:SK7K:YVNU:Y5KR:E36L:Q55E:G66W:F7Z5:UO6D:JNLO:ZQQY
WARNING: No swap limit support

uname -a:

Linux mechjeb 3.16.0-41-generic #57-Ubuntu SMP Thu Jun 18 08:44:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Environment details (AWS, VirtualBox, physical, etc.): Running on Ubuntu 14.04 on AWS

How reproducible: Always

Steps to Reproduce:

root@mechjeb:~# wget -qO- https://experimental.docker.com/ | sh
<<Install successfull>>
root@mechjeb:~# docker run -d busybox top
Unable to find image 'busybox:latest' locally
latest: Pulling from library/busybox
cf2616975b4a: Pull complete 
6ce2e90b0bc7: Pull complete 
8c2e06607696: Already exists 
Digest: sha256:38a203e1986cf79639cfb9b2e1d6e773de84002feea2d4eb006b52004ee8502d
Status: Downloaded newer image for busybox:latest
67d23cabe882a20a93f4bf08d84347f240cf64886764507b935a17ca9b3a1f47
root@mechjeb:~# docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
67d23cabe882        busybox             "top"               3 seconds ago       Up 3 seconds                            lonely_tesla
root@mechjeb:~# docker stop 67d23
Error response from daemon: Cannot stop container 67d23: permission denied
Error: failed to stop containers: [67d23]
root@mechjeb:~# docker kill 67d23
Error response from daemon: Cannot kill container 67d23: permission denied
Error: failed to kill containers: [67d23]
root@mechjeb:~# docker rm -f 67d23
Error response from daemon: Cannot destroy container 67d23: Could not kill running container, cannot remove - permission denied
Error: failed to remove containers: [67d23]
root@mechjeb:~#

Actual Results: Container not removed/killed/stopped (Until a reboot is issued)

Expected Results: Container killed/removed/stopped

About this issue

Original URL
State: closed
Created 9 years ago
Comments: 29 (22 by maintainers)

Commits related to this issue

Most upvoted comments

Just as an update on this. I sent a number of hours investigating, looking in the docker code but couldn’t see anything. This was happening on 15.04, potentially a systemd issue.

Changing docker directories didn’t resolve issue.
Rolling back to 1.6.2 didn’t resolve issue.
If I launched the daemon from the command line it would be fine. Even when pointed to existing data directory.
I could stop the containers with systemctl directly.
If I launched a container using docker -d -t ubuntu bash it was unable to be stopped. Other containers running non-bash commands could be stopped. I think this was something to do with how the underlying process handled SIGKILL commands, it was the same with a Golang process too.

Sadly I’ve since destroyed the instance as being unable to remove containers had knock-on effects to the rest of the system.

BenHall on Aug 8, 2015

A kill -9 on the PID of the container will then allow you to delete it.

BenHall on Aug 7, 2015

I have met the same problem, but I can’t reproduce after reboot my system

coolljt0725 on Jul 29, 2015