New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Error resize: Error: bad file descriptor" using docker provided vagrant VM #2683
Comments
Apparently removing '-t' means it doesn't break. |
i'm seeing this with docker 0.7.0 if |
@srid are you using the Vagrant VM as well? Or do you have docker directly installed? |
i'm running docker under vmware fusion VM. |
I'm seeing an issue like this on a VM (running on KVM) with Docker 0.7.2:
|
Seeing the same thing:
lxc version is 0.7.5-3ubuntu69. Also goes away if I drop the -t. |
Definitely still a problem - easily reproducible with the steps in the issue report at the top. |
Less frequently in 0.7.5 (0.7.2 was doing it every time), different error message |
The suggestion from #3595 (install cgroup-lite) hasn't worked for me, it's already installed on the vagrant vm docker comes with. |
Check cgroup fs mount.
solved things for me... |
Please try PR #3557 and let me know if you're still running into problems with those changes. |
I have tried with 0.8.0 (which includes the PR above). It does it (breaks) nearly every time now. jultan's suggestion didn't work on 0.8.0 (even after a VM reboot). I didn't test his suggestion on 0.7.5.
Where 3aa64 is stackbrew/ubuntu:12.04 |
I have started seeing this problem only after installing 0.8.0 recently with boot2docker 0.5.4. |
Docker version 0.8.0, build cc3a8c8 here running on Ubuntu Precise, same error I had to apply jultan fix to get rid of this issue. |
Seeing this on 0.9 after upgrading from 0.8 client.go:2315 Error resize: Error: bad file descriptor |
Can you try running without |
Seeing this as well. Running ubuntu 13.10 64bit in vagrant. Docker version 0.9.0, build 2b3fdf2 [later edit]
|
Anyone/everyone running into this on Ubuntu should test out: sudo wget -O /etc/init/docker.conf https://raw.github.com/dotcloud/docker/master/contrib/init/upstart/docker.conf
sudo service docker restart and comment on #4574 if it fixes the problem for you. If you're on Debian, you should instead use something like: sudo wget -O /etc/init.d/docker https://raw.github.com/dotcloud/docker/master/contrib/init/sysvinit-debian/docker
sudo chmod +x /etc/init.d/docker
sudo service docker restart (SvenDowideit updated the URLs to the new merged version) |
This may have actually broken things for me(edit: when I wrote that, I thought that the merged PR actually effected me, now I see that it only changed the startup scripts which I'm not even running...)(Debian Wheezy, kernel from backports). I had docker working(0.8 something) but I just tried downloading the latest binary and I get the following output:
Without
Here is what it looks like on the server side:
|
@tianon Did you delete the |
I've hacked @tianon 's urls to be the new merged ones @timthelion :) |
has anybody got ride of this error ? Am facing the same problem WARNING: Local (127.0.0.1) DNS resolver found in resolv.conf and containers can't use it. Using default external servers : [8.8.8.8 8.8.4.4] |
Same problem:
|
facing the same issue on ubuntu
@tianon worked with the updated docker.conf script |
I started again from scratch in Ubuntu after kernel upgrade to 3.8.0-19-generic. |
Also try this |
Installing cgroup-lite as per @shafi-codez's recommendation above has solved the problem for me as well. Ubuntu 3.11 on VMWare Fusion 5. |
Installing cgroup-lite fixed the issue for me as well. |
Installing |
Running cgroup-lite fixed the issue for me as well. Original error:
Here's some context:
|
Docker 0.9.1 and Docker built from master shouldn't run into this problem any more. Please feel free to comment if you can still reproduce this problem. |
@unclejack , I'm having the same problem:
Docker v0.9.1 running on Ubuntu x86_64, using docker from the official repository. I'm using the "docker" group to run the client. I have a stopped container, yesterday it worked fine. Today, after reboot, I use |
Ah, this clarifies the situation: I had mysql running locally on 3306 which prevented the container from starting: % docker start app-devel
Error: Cannot start container dignio-devel: listen tcp 0.0.0.0:3306: bind: address already in use
2014/06/03 11:18:35 Error: failed to start one or more containers
% docker start -ai dignio-devel
[error] client.go:2329 Error getting size: bad file descriptor So the only problem is the error message, which becomes useless with (when I stopped local MySQL -- now it works fine) |
Just thought I'd add that I was facing this issue on the Debian derivative SolidK using docker.io version 0.9.0 and managed to resolve it by install the package "cgroup-bin" and then issuing the command "sudo umount cgroup" and finally doing "sudo service docker.io restart". Now docker works as expected. In Debian Jessie as the host I did not experience this issue. Hope this helps someone. |
I'm using docker v0.6.6, Vagrant 1.3.5, virtualbox 4.1.24 and the docker vagrantfile (with some minor modifications to forward some ports).
Steps to reproduce:
the last line just repeats
docker run -t -i -h=test1 8db /bin/bash -c true
.It takes a few (say 10-15) repetitions before it gets there, but when it does:
I've seen other mentions of vaguely similar error message (mainly in relation to upgrading lxc) but this is a fresh docker vagrant VM...shouldn't be any issues I wouldn't think? It wouldn't be so bad it if consistently errored, but this inconsistency is quite unhelpful.
The text was updated successfully, but these errors were encountered: