3 ms·
It's not like containers are always easy and always work fine and never introduce problems of their own. If I'm debugging something, the last thing I want to d
by kelnos 2y ago
It's not like containers are always easy and always work fine and never introduce problems of their own.
If I'm debugging something, the last thing I want to do is spin up a container, make sure I've mounted the paths I need inside it, and/or ferry things in and out of it.
I'd much rather just run the binary under a different interpreter.
Granted, this is only useful if I'm already building my own glibc for some reason. If I'm debugging a problem where someone tells me my app is broken on some other version of some other distro, and I've narrowed the problem down to glibc, it is probably easier just to spin up a container image of that version of that other distro, rather than building my own glibc, using the same version as in that other distro.