6 ms·
docker exec -it <container id> kubectl exec -it pod -c container
by compsciphd 6y ago
docker exec -it <container id>
kubectl exec -it pod -c container
- murkt 6y agoNot sure what do you want to say with this command.
- compsciphd 6y agoyou want to be able to "ssh in and make changes to figure out how to fix things". why doesn't that do that for you?
- reportgunner 6y agoSorry, but did you not forget the --rm option to remove the container once it dies ?
- AkshatM 6y agoI interpret it as a suggestion that you allow developers access to the running container in production to debug the issue There are more sane ways to do this than through raw kubectl access, of course: see e.g. telepresence (https://www.telepresence.io/ https://www.telepresence.io/)
- funcDropShadow 6y agoBy sane, you mean yet another piece of infrastructure that has to be installed, documented, packaged into containers, deployed and updated for a problem that did not exist without containers. For a very large organization (e.g. hundreds of devs) this make sense, but for a medium sized company (> billion EUR turnover per year outside of software business) this soon becomes just another piece of overhead.
- wwright 6y agoThis problem certainly exists without containers. - How do you provide easy visibility into running applications? - How do you prevent inspecting an application from affecting the behavior of an application?
- sseagull 6y agoYou put this fairly succinctly. And I agree wholeheartedly. I think of the phrase “adding epicycles” when this kind of stuff starts happening.