3 ms·

I can’t express how many times htop has made my life easy by giving me this nice interactive UX. There is a reason it’s part of every docker image I create.

• seneca 6y ago
  > There is a reason it’s part of every docker image I create. You really shouldn't put troubleshooting tools in your container images. You can join a "toolbox" container to a running container's namespace to get your tools there when you need them. That avoids unnecessarily large images, extra build time, and extra dependencies in your image.
  • reed1 6y ago
    sorry for being ignorant to learn myself, but how do I do this?
    • seneca 6y ago
      No need to apologize, this stuff isn't always easy to find. In docker, it's done by passing --pid=container:$TARGETCONTAINER to docker run Here's the docs on it: https://docs.docker.com/engine/reference/run/#pid-settings---pid https://docs.docker.com/engine/reference/run/#pid-settings--...
  • robotresearcher 6y ago
    > That avoids unnecessarily large images, extra build time, and extra dependencies All of these are mandatory for containers, though... ? </joke>