docker exec fails with exit code 255 #15713
Labels
kind/bug
Bugs are bugs. The cause may or may not be known at triage time so debugging may be needed.
Comments
|
I have exactly the same issue |
|
This looks like the container is stopped but only after the exec instance is actually attempted to be started? |
|
closing because OP didn't respond, but I'm happy to reopen after |
|
FWIW, I'm running into this in RancherOS 0.4.0: [root@ip-10-1-1-242 ~]# docker exec -it consul-server /bin/bash
[root@ip-10-1-1-242 ~]# echo $?
255
[root@ip-10-1-1-242 ~]# docker info
Containers: 2
Images: 21
Storage Driver: overlay
Backing Filesystem: extfs
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.2.3-rancher
Operating System: RancherOS (containerized)
CPUs: 1
Total Memory: 1.956 GiB
Name: ip-10-1-1-242.ec2.internal
ID: NHHC:FZ63:MUX4:4YSA:CLBF:HCMN:SBRX:PC22:V3JS:MIKX:O6LL:RFLF
[root@ip-10-1-1-242 ~]# docker version
Client:
Version: 1.8.3
API version: 1.20
Go version: go1.4.2
Git commit: 5eab58c
Built: Wed Oct 14 13:42:27 UTC 2015
OS/Arch: linux/amd64
Server:
Version: 1.8.3
API version: 1.20
Go version: go1.4.2
Git commit: 5eab58c
Built: Wed Oct 14 13:42:27 UTC 2015
OS/Arch: linux/amd64 |
|
Oh - also, the container is not stopped. It appears to be running just fine. One (perhaps relevant) detail is this particular container was initially run before the last reboot, so it's been automatically restarted (because |
|
So, for the record, I'm a total moron - there is no |
|
LOL |
|
I've hit the exact same as the original issue: Info: However, this issue may be a symptom, as I think the container was deadlocked at the time - docker kill was hanging, docker attach was hanging and I had to restart the daemon. |
|
Argh, I've just come across this error again on a different machine, searched for the error and ended up back here. Except now I'm on docker 1.9.1. Again, kill is hanging. |
Yuck. Edit: this is 3.13.0-55-generic on Ubuntu 14.04.3 LTS. |
|
Thanks @aidanhs, yuk indeed. I'll reopen this one |
thaJeztah
added
the
kind/bug
|
I just faced this issue and, by digging a bit, I found out that the last command in my Dockerfile was and that command was failing internally with: so I changed the path to the correct one ( If you want to try and reproduce the issue, you can use the Dockerfile from here. The commit that fixes the issue (and that allows me to use I don't know how useful this is, I hope it helps 😄 |
|
I am getting this behavior on one of my containers (Below). I am able to get in at some point but is hard to do some times, just have to keep at it, and once you get it never exit if you can help it. |
|
Pretty sure this was fixed in libcontainer some time ago (1.9-1.10 ish). @wil93 Not sure how this applies to this issue. |
|
@cpuguy83 that seems to have fixed things for me, updated to 1.10 and now I can get in predictably. Thanks! |
|
Awesome! Thanks for reporting @lockwobr |
|
I made some edits on the docker-compose.yml file to add a new service and my containers don't start anymore. I get a 255 error message. Is there any way to get to a log file? Not a container log file, since the docker ps output is empty. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sometimes when I issue docker exec, it fails without printing any error messages and just exits with error code 255.
The image I am using is docker-in-docker (dind) and there are some docker containers running inside this container which is probably relevant.
in docker.log I see:
This happens in the parent container so it is bug in docker, not in dind.
uname -a
docker version
docker -D info
The error code is the same as issue #9680, but this is a newer kernel.
The text was updated successfully, but these errors were encountered: