3 ms·
I thought the idiomatic way of debugging containerized applications was from the host system, not from inside the container. The tooling surely can still be imp
by zokier 11y ago
I thought the idiomatic way of debugging containerized applications was from the host system, not from inside the container. The tooling surely can still be improved, but fundamentally the host has full view to the innards of containers.
- hinkley 11y agoI can't tell if I'm exposing the wrong port(s) (or rather, PORTing the wrong EXPOSES, please shoot whoever inverted that terminology). I also can't easily tell if I'm getting relative paths wrong, and I can't rapidly iterate on fixing the problem. That's where you really feel the debugging problems. The drag of day to day troubleshooting of new configuration or tools can still be pretty challenging. Stuff tends to stay working once you get it working though, so that evens up the score a bit, but I'd really love it if getting there were smoothed out a bit.
- cyphar 11y agoAre you talking about debugging code running a container or debugging Docker? Because we're all talking about the former, not the latter.
- hinkley 11y agoAh, I tend to define "debug" not as "the act of using a debugger tool" but as "diagnosing the broken things". Makes me fairly useful in a crisis, but possibly less so in this thread. I would think a remote debugger would work just fine in a container, at least once you documented how, but to zokier's point the only reason you'd do that is if the problem isn't repeatable outside the container. To me that means a couple possibilities. Bug in the docker scripts, bug in the unikernal generator, or a timing issue, which a debugger won't help you with very much (timing bugs are often also heisenbugs)