3 ms·
Maybe Docker stinks? > lxc-execute command will run the specified command into the container via an intermediate process, lxc-init. This lxc-init after launchi
by smegel 10y ago
Maybe Docker stinks?
> lxc-execute command will run the specified command into the container via an intermediate process, lxc-init. This lxc-init after launching the specified command, will wait for its end and all other reparented processes. (to support daemons in the container). In other words, in the container, lxc-init has the pid 1 and the first process of the application has the pid 2.
https://linuxcontainers.org/fr/lxc/manpages/man7/lxc.7.html https://linuxcontainers.org/fr/lxc/manpages/man7/lxc.7.html
- xahrepap 10y agoOr maybe, more likely, Docker isn't interested in solving the problem. But it doesn't mean docker stinks just because another similar tool decided to solve this problem. And it doesn't take away from all the problems docker does solve.
- smegel 10y ago> Docker isn't interested in solving the problem Or Docker is creating the problem by doing it wrong.
- xahrepap 10y agoOk. So they're doing this one thing wrong (or in other words, you don't like it). However, every project has its pros and cons. Docker definitely has its cons, but for my use cases the pros far outweigh the cons. In this particular case, the work arounds are numerous and very easy to use.