3 ms·
If you run a single process in a Docker container, have it output logs over STDOUT, and have no meaningful way to interact with it other than shutting it down,
by jerf 5y ago
If you run a single process in a Docker container, have it output logs over STDOUT, and have no meaningful way to interact with it other than shutting it down, you don't have much need for a shell. It can't do anything in the container anyhow. By contrast, if you've basically got a full OS in there, then yeah, a shell is really useful.
- pageandrew 5y agoI would say most of my Go projects involve what you described (logs to stdout, simple interface) but I often find myself needing a shell to debug my docker build, like ensuring that files have ended up in the correct place, and have the correct contents, within the docker container.
- oweiler 5y agoUse Dive for inspecting the image https://github.com/wagoodman/dive&ved=2ahUKEwips5OH0Lr1AhW977sIHeVsDXwQFnoECAUQAQ&usg=AOvVaw3itrNjHxmGPoA6o5sq3NQ0 https://github.com/wagoodman/dive&ved=2ahUKEwips5OH0Lr1AhW97...
- hajhatten 5y agoYour link is busted, https://github.com/wagoodman/dive https://github.com/wagoodman/dive