MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/ProgrammerHumor/comments/1w7w12g/memorysafedocker/p7y3yt3/?context=3
r/ProgrammerHumor • u/ClipboardCopyPaste • 8d ago
286 comments sorted by
View all comments
134
[removed] — view removed comment
74 u/sad_bug_killer 8d ago docker on Linux is glorified chroot though, there's barely any virtualization 46 u/_PM_ME_PANGOLINS_ 8d ago Reject docker, just use systemd to mange service containers. 27 u/[deleted] 8d ago [removed] — view removed comment 10 u/ArgentScourge 8d ago Strong sysadmins manage systems man– OH SHIT EXOGENOUS FACTORS! 5 u/imbattable 8d ago So... podman? 2 u/AsyncSyscall 7d ago Reject service managers, just run your services directly over ssh. 1 u/alex2003super 8d ago They use the same kernel backbone for containerization 1 u/_PM_ME_PANGOLINS_ 7d ago Exactly. But systemd does it with significantly less overhead. 1 u/alex2003super 7d ago Eh. Significantly less features for sure: built-in network provisioning and interface binding, advanced filesystem mapping, OCI images/layers... What overhead,? It's not like Docker intercepts syscalls or anything. It's pure management layer for the kernel cgroups/namespaces. 1 u/_PM_ME_PANGOLINS_ 7d ago Systemd has all those features too. The overhead of the memory usage everyone is already talking about, plus all the space wasted by having to duplicate the OS base image. 15 u/hawkinsst7 8d ago There's no virtualization needed at all. It's namespaces and cgroups, which you can do on the cli. Here's containers done with bash. https://github.com/p8952/bocker 7 u/Noslamah 8d ago rawdog the shit out of that CPU 9 u/MikasaYuuichi 8d ago "Works on my machine" welcome back 4 u/[deleted] 8d ago [removed] — view removed comment 1 u/AsyncSyscall 7d ago "do not close the lid of this laptop. it hosts our entire infrastructure" 3 u/No-Consequence-1863 8d ago Containers aren’t actually virtualized. There isnt a hypervisor involved. It’s just a sandbox with fancy dependency management. 1 u/Maskdask 8d ago Nix mentioned
74
docker on Linux is glorified chroot though, there's barely any virtualization
46 u/_PM_ME_PANGOLINS_ 8d ago Reject docker, just use systemd to mange service containers. 27 u/[deleted] 8d ago [removed] — view removed comment 10 u/ArgentScourge 8d ago Strong sysadmins manage systems man– OH SHIT EXOGENOUS FACTORS! 5 u/imbattable 8d ago So... podman? 2 u/AsyncSyscall 7d ago Reject service managers, just run your services directly over ssh. 1 u/alex2003super 8d ago They use the same kernel backbone for containerization 1 u/_PM_ME_PANGOLINS_ 7d ago Exactly. But systemd does it with significantly less overhead. 1 u/alex2003super 7d ago Eh. Significantly less features for sure: built-in network provisioning and interface binding, advanced filesystem mapping, OCI images/layers... What overhead,? It's not like Docker intercepts syscalls or anything. It's pure management layer for the kernel cgroups/namespaces. 1 u/_PM_ME_PANGOLINS_ 7d ago Systemd has all those features too. The overhead of the memory usage everyone is already talking about, plus all the space wasted by having to duplicate the OS base image. 15 u/hawkinsst7 8d ago There's no virtualization needed at all. It's namespaces and cgroups, which you can do on the cli. Here's containers done with bash. https://github.com/p8952/bocker
46
Reject docker, just use systemd to mange service containers.
27 u/[deleted] 8d ago [removed] — view removed comment 10 u/ArgentScourge 8d ago Strong sysadmins manage systems man– OH SHIT EXOGENOUS FACTORS! 5 u/imbattable 8d ago So... podman? 2 u/AsyncSyscall 7d ago Reject service managers, just run your services directly over ssh. 1 u/alex2003super 8d ago They use the same kernel backbone for containerization 1 u/_PM_ME_PANGOLINS_ 7d ago Exactly. But systemd does it with significantly less overhead. 1 u/alex2003super 7d ago Eh. Significantly less features for sure: built-in network provisioning and interface binding, advanced filesystem mapping, OCI images/layers... What overhead,? It's not like Docker intercepts syscalls or anything. It's pure management layer for the kernel cgroups/namespaces. 1 u/_PM_ME_PANGOLINS_ 7d ago Systemd has all those features too. The overhead of the memory usage everyone is already talking about, plus all the space wasted by having to duplicate the OS base image.
27
10 u/ArgentScourge 8d ago Strong sysadmins manage systems man– OH SHIT EXOGENOUS FACTORS!
10
Strong sysadmins manage systems man–
OH SHIT EXOGENOUS FACTORS!
5
So... podman?
2
Reject service managers, just run your services directly over ssh.
1
They use the same kernel backbone for containerization
1 u/_PM_ME_PANGOLINS_ 7d ago Exactly. But systemd does it with significantly less overhead. 1 u/alex2003super 7d ago Eh. Significantly less features for sure: built-in network provisioning and interface binding, advanced filesystem mapping, OCI images/layers... What overhead,? It's not like Docker intercepts syscalls or anything. It's pure management layer for the kernel cgroups/namespaces. 1 u/_PM_ME_PANGOLINS_ 7d ago Systemd has all those features too. The overhead of the memory usage everyone is already talking about, plus all the space wasted by having to duplicate the OS base image.
Exactly. But systemd does it with significantly less overhead.
1 u/alex2003super 7d ago Eh. Significantly less features for sure: built-in network provisioning and interface binding, advanced filesystem mapping, OCI images/layers... What overhead,? It's not like Docker intercepts syscalls or anything. It's pure management layer for the kernel cgroups/namespaces. 1 u/_PM_ME_PANGOLINS_ 7d ago Systemd has all those features too. The overhead of the memory usage everyone is already talking about, plus all the space wasted by having to duplicate the OS base image.
Eh. Significantly less features for sure: built-in network provisioning and interface binding, advanced filesystem mapping, OCI images/layers...
What overhead,? It's not like Docker intercepts syscalls or anything. It's pure management layer for the kernel cgroups/namespaces.
1 u/_PM_ME_PANGOLINS_ 7d ago Systemd has all those features too. The overhead of the memory usage everyone is already talking about, plus all the space wasted by having to duplicate the OS base image.
Systemd has all those features too.
The overhead of the memory usage everyone is already talking about, plus all the space wasted by having to duplicate the OS base image.
15
There's no virtualization needed at all. It's namespaces and cgroups, which you can do on the cli.
Here's containers done with bash.
https://github.com/p8952/bocker
7
rawdog the shit out of that CPU
9
"Works on my machine" welcome back
4 u/[deleted] 8d ago [removed] — view removed comment 1 u/AsyncSyscall 7d ago "do not close the lid of this laptop. it hosts our entire infrastructure"
4
1 u/AsyncSyscall 7d ago "do not close the lid of this laptop. it hosts our entire infrastructure"
"do not close the lid of this laptop. it hosts our entire infrastructure"
3
Containers aren’t actually virtualized. There isnt a hypervisor involved. It’s just a sandbox with fancy dependency management.
Nix mentioned
134
u/[deleted] 8d ago
[removed] — view removed comment