4 ms·
I think there is a mix of things being bandied about under the "container" banner. On the one hand it is about getting more bang for your hardware buck. On th
by digi_owl 11y ago
I think there is a mix of things being bandied about under the "container" banner.
On the one hand it is about getting more bang for your hardware buck.
On the other it is about someone getting so deep into netsec that they have developed gills.
In the bang for bucks category you have a chain of one box pr database etc.
Then noticing that the hardware sits idle most of the time, so virtualization is depolyed to pack more server on a single box to keep it in use.
Then noticing that virtualization comes with a performance overhead, so it gets replaced chroot/containerization to give the impression of unshared box.
In the netsec category it is really about namespace. Limiting the view of the world the processes gets.
This has a superficial similarity to chroot, but can go much much deeper.
And if one go deep enough, every server ends up looking like a digital fort Knox...
- icebraining 11y agoYeah, but none of that actually needs docker and images and such. If you want to take advantage of the whole server, you can simply run more regular processes on it, and you can launch them on different namespaces using systemd or other process manager. You don't need the whole workflow that comes with these new tools.
- digi_owl 11y agoFrom a traditional sysadmins point of view, thats true. these days though you are looking at devops... Never mind that more recent systemd releases can grok docker containers.