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
Hitting panic() in lxc/driver.go:288 #4295
Comments
Can you post the panic? |
|
I'm seeing this as well (also with the btrfs backend). I'm not sure, but I think it may have started happening after I went from 3.12 to 3.13. I'm on Arch. |
FWIW, I've been previously running docker on 3.13.1 for a while, and this one is triggered on 3.13.4. I don't feel that it's somehow related to kernel though. |
I had the same issue on Arch Linux. It has to do with the version of lxc. The problem was fixed when I downgraded from lxc-1.0 to lxc-0.9. |
Oh, interesting. It's not the only docker/lxc 1.0 interaction regression: #4298. |
@farcaller can you post the commit id you are using, your title says line |
The correct line is 282 at cc3a8c8, others were added by me to do On Mon, Feb 24, 2014 at 11:04 PM, Victor Vieux notifications@github.comwrote:
Sincerely, |
@farcaller the panic was removed by #4013 could you try with docker 0.8.1 ? |
Yes, I noticed that I'm not running on the bleeding edge. I guess, this issue is not relevant now. |
I got a docker with btrfs backend.
After stopping docker with a live running container via
systemctl stop docker
it never comes up again, hitting the panic() in lxc driver.Context:
Returned output/error from lxc-info:
0e8982087f82bc2017fc0de3e6102718dde24b3d31dc65dab02516fe3b62d21c doesn't exist
, exit code 1.Config from the corresponding container (
/var/lib/docker/containers/0e8982087f82bc2017fc0de3e6102718dde24b3d31dc65dab02516fe3b62d21c/config.json
):I'm not sure why docker expects it to be running at this state (I guess docker doesn't tear container down, but systemd kills everything in the docker cgroup). Anyway, it must not panic on docker-lxc state inconsistency.
The text was updated successfully, but these errors were encountered: