Skip to content
DevMeme
5857 of 7590
When Windows and Linux Split, Docker Becomes the Custody Arrangement
Containerization Post #6414 · source on Telegram

When Windows and Linux Split, Docker Becomes the Custody Arrangement

Description

Cartoon-style meme on a sky-blue background. Text at the top reads, "Divorce leads children to the worst places" in bold black font. On the left cliff stands a humanoid figure whose head is replaced by the classic four-color Windows logo; on the right cliff a similar figure has the Tux penguin for a head. A child in the middle (face blurred) is pulled in opposite directions by both "parents" while teetering over a gap. At the bottom of the chasm is a large Docker logo (blue whale carrying shipping containers) implying that if the tug-of-war fails, the child will fall into container land. The scene satirically depicts cross-platform friction: Windows and Linux environments fighting over workloads, leaving developers to rely on Docker as the painful compromise

Categories

Containerization OperatingSystems DevOps SRE

Common Tags

Docker Containerization WindowsVsLinux OperatingSystems Devops CrossPlatformDevelopment RelatableDevExperience TechHumor

Comments

25
Anonymous ★ Top Pick Containers were supposed to be the peace treaty, but they’ve ended up as the weekend shuttle for binaries whose OS parents still refuse to share a file system
  1. Anonymous ★ Top Pick

    Containers were supposed to be the peace treaty, but they’ve ended up as the weekend shuttle for binaries whose OS parents still refuse to share a file system

  2. Anonymous

    After 15 years of wrestling with Docker Desktop's WSL2 backend eating 16GB of RAM just to run a single nginx container, you realize the real custody battle isn't between Windows and Linux - it's between your sanity and the Docker daemon that somehow needs admin privileges to map a port

  3. Anonymous

    The real tragedy isn't the custody battle - it's that Docker still has to explain to both parents why it needs WSL2 to visit Windows, while Linux just natively understands. At least the child support payments come in the form of container orchestration fees, equally distributed across both platforms' cloud bills

  4. Anonymous

    DevOps joint custody: Windows wants Docker Desktop, Linux demands cgroups v2 - so the kid lives in OCI land where path separators and CRLF/LF negotiate peace via 2am bind mounts

  5. Anonymous

    Windows and Linux divorced, but Docker got full custody - and your on-call rotations

  6. Anonymous

    Windows and Linux split custody, so the kid lives with Docker - weekends are WSL2, weekdays are bind‑mount visitation, and permissions get negotiated via UID maps and cgroups v2

  7. @H3R3T1C 1y

    Well Docker is more linux than w$n

    1. @Bonessssss 1y

      win -> ping win

  8. @H3R3T1C 1y

    even the most used on w$n is with WSL

  9. @jaaaaded 1y

    docker is just linux cgroups

    1. @Bonessssss 1y

      - You can't store and then restore cgroup as you can with a Docker image - On top of that, containers allow for predefined environment (except kernel version) - On the other hand (I think) most IPC methods are unavailable between processes that are not running in the same container (and cgroups don't have that limitation)

  10. @H3R3T1C 1y

    hummm more linux namespaces

    1. @ygerlach 1y

      Docker uses cgroups and namespaces to implement its features. But you can for example use systemd containers to have even better system integration.

      1. @andrei_nik_kolesnikov 1y

        podman, that is?

      2. @chupasaurus 1y

        By not having a sane way to interact from shell with netns created by systemd, for example. Such better @ much wow.

  11. @H3R3T1C 1y

    cgroup is for resources control

  12. @ygerlach 1y

    podman is yet another implementation. I am talking about the systemd-nspawn command.

    1. @andrei_nik_kolesnikov 1y

      Podman uses systemd-nspawn as its underlying container runtime

      1. @ygerlach 1y

        Ah, didnt know that. Last time i checked they where using runc or something like that. Where is that stated?

        1. @andrei_nik_kolesnikov 1y

          https://wiki.gentoo.org/wiki/Podman https://wiki.gentoo.org/wiki/Systemd/systemd-nspawn podman is a daemonless container engine for developing, managing, and running OCI Containers on Linux, aiming to be a drop-in replacement for Docker ... On systemd-based systems, Podman uses systemd slices to allow Podman to run rootless, i.e. as a non-privileged user. systemd-nspawn is a lightweight, loosely chroot-like, OS-level OCI container environment native to systemd

  13. @mira_the_cat 1y

    tan ni la mi wile toki e toki pona

  14. @SamsonovAnton 1y

    What's the divorce between 🪟 and 🐧 they are talking about?

  15. @LostGhost11 1y

    Docker is only there because distro-specific package managers are terrible

  16. dev_meme 1y

    At this stage I have no idea if this is satire or just pure trolling

  17. dev_meme 1y

    Yeah, that's how it should be Damn, I even lost a few golden memes because after finding them I went deeper checking "is it actually funny and correct" and then... Bah, where is the meme? Well, it was long time ago, I rarely do it like this now

More like this

More like this in Containerization →
Containerization Docker Containerization
Grandma Remembers Deploying Applications Without Containers

Grandma Remembers Deploying Applications Without Containers

Containerization
Two Types of 'Advanced Linux User' -- Infra Engineer vs Rice Enthusiast

Two Types of 'Advanced Linux User' -- Infra Engineer vs Rice Enthusiast

OperatingSystems
All Modern Digital Infrastructure Rests on Bitnami Container Images

All Modern Digital Infrastructure Rests on Bitnami Container Images

Containerization
Use J and K for navigation