3 ms·
No the correct solution is to debug the issue not just reboot/restart/reinit the damn thing. This mentality is WHY Linux/docker/containers/Linux worlds NIH syn
by X86BSD 10y ago
No the correct solution is to debug the issue not just reboot/restart/reinit the damn thing.
This mentality is WHY Linux/docker/containers/Linux worlds NIH syndrome, is such a tire fire.
- chewchew 10y agoIt's not one or the other. Restarting might save you some downtime if you're running a single IRC container. That doesn't mean you shouldn't find and resolve the root issue. Normally I just rollback to the previous version container if I have a recurring issue. Windows containers are now available, if you can't stand linux: https://msdn.microsoft.com/en-us/virtualization/windowscontainers/about/about_overview https://msdn.microsoft.com/en-us/virtualization/windowsconta... Anyway, don't use containers if you don't want to. I'm glad I invested the time since I understand them very well and use them to my advantage. But I did have to learn a lot and experiment with a bunch of tools, and maybe that's not worth it to you.