-
Notifications
You must be signed in to change notification settings - Fork 38.8k
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
sidecar exec #27464
Comments
I'm pretty sure this is a duplicate request... Not sure how to find the other issue though. I'll leave this open because it's a well written clear feature request, thanks. |
docker 1.12 has this implemented: Which I think would be a prereq. |
I am very interested in this feature. |
I also think this would be a great feature to have |
Similar to #27140 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Say I keep my containers as light weight as possible, perhaps using alpine or some other light weight distro.
When something goes wrong in a pod, it can be difficult to exec in and debug sometimes because there are no debugging tools in the container.
It would be awesome if you could temporarily attach a new sidecar container to the specified pod for debugging purposes.
something like:
kubectl exec -it mypod -s mydebugcont /bin/bash
It could even perhaps take a -c flag and attach to the same pid namespace of the specified container so stuff like running strace -p would work.
The text was updated successfully, but these errors were encountered: