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
Pipework Re-assigning IP to existing container kills host / Segfault #7627
Comments
Execute pipework twice on the SAME INTERFACE with new IPs or same and segfaults and throws a kernel error. ifconfig inside the container will hang the container and throw docker into disk wait mode. Impossible to restart docker process. Shutdown even hangs. This requires a power cycle to resolve. Note: Running pipework twice on DIFFERENT interfaces works just fine as long as you don't rerun pipework on them once they are up. How to reproduce: Dmesg output after incident: |
root@docker:~# lspci |
This doesn't really belong here as it's a pipework thing. |
Environment
Ubuntu 14.04 LTS (GNU/Linux 3.13.0-30-generic x86_64)
Docker 1.1.1
Latest Pipework
Method to replicate issue:
Bring up a container with an ip using pipework:
ie. root@docker:~# pipework eth0 -i eth1 0b3 1.1.1.1/24@1.1.1.254
Then run the same command again after the container is up:
root@docker:~# pipework eth0 -i eth1 0b3 1.1.1.1/24@1.1.1.254
Segmentation fault
It segfaults the container, leaves docker in a disk wait mode and hoses the physical host. The only method to get the host to do anything is to hard boot it. It will not respond to a restart inside of linux.
The text was updated successfully, but these errors were encountered: