3 ms·
I thought there was a way to enter a namespace (googled this as I write the comment). Basically you have your shell and debug bits outside the container and mak
by WestCoastJustin 12y ago
I thought there was a way to enter a namespace (googled this as I write the comment). Basically you have your shell and debug bits outside the container and make it appear as if it was inside it via nsenter [1]. I have not tested this, but will do that in a second. This might correct the situation you are thinking of.
+--------------------+
| docker container |
| w/ static bin |
| <----- nsenter + bash/debug bits (on host machine)
+--------------------+
[1] http://www.kevssite.com/2014/08/05/console-access-into-a-running-docker-container/ http://www.kevssite.com/2014/08/05/console-access-into-a-run...
- shykes 12y agoAs of Docker 1.3 you can simply 'docker exec' :)
- drdaeman 12y agoHe is actually talking about the case where bash binary (or gdb or whatever you're going to exec) does not exist in container. So the hassle of loading bash from the parent, then moving the process into container's namespace with nsentry. So, nope, docker exec just wouldn't work.
- shykes 12y agoYou're right, we're still missing dynamic volume mounts to do the same thing in Docker. My bad.