27. April 2025 | Linux Containers | Docker | LXC | runc
Running Docker on VMware / vSphere (VSX, etc.) in your own datacenter: Still depends on your hardware (if the server dies, the VM dies, containers die). Still depends on your VMware infrastructure (and VMware itself can crash or have bugs). You add another layer of...
27. April 2025 | Linux Containers | Docker | LXC | runc
Why you wouldn’t run hundreds of containers directly on bare metal: Single point of failure → if the kernel or hardware dies, everything dies. Kernel risk → one bad kernel update could wipe out hundreds of containers at once. Hard to isolate performance issues →...
27. April 2025 | Linux Containers | Docker | LXC | runc
Short version: LXC and Docker containers share the host’s kernel. They don’t have their own separate kernel inside the container. So: if the host’s kernel changes (upgrade, patch, bug, security fix) → it immediately affects all containers running on...
15. April 2025 | Linux Containers | Docker | LXC | runc
Nice one — here’s the simple version: Control groups (cgroups) = control „how much“ resources a process can use (CPU, memory, disk I/O, network, etc.). Example: „This container can only use 1 CPU and 512MB RAM.“ Namespaces = control...
9. April 2025 | Hypervisor, Linux Containers | Docker | LXC | runc
Good question! Here’s the main difference between LXC and Xen: LXC (Linux Containers) uses operating system-level virtualization. It shares the same Linux kernel between all containers. Containers are isolated from each other, but they’re all running on the same...
4. April 2025 | Linux Containers | Docker | LXC | runc
LXC has been around since about 2008! 🚀 It was developed as part of the Linux kernel’s growing support for cgroups (control groups) and namespaces, which allow process isolation — two key ingredients for containers. So timeline-wise: 2006–2008: Linux kernel gets...
