HackerTube

Hitler uses Docker

nukemtubeCited 9× on HN, 2016–2025
YouTube
comedy · general · 2016–2025 on HN

A Downfall parody in which Hitler rages about Docker problems. It is a short comedy sketch aimed at developers.

Posted as a running joke whenever Docker, containers or frustrating software come up, not as something to learn from.

9 comments from Hacker News

@yevpats2025-03 · in “Yoke: Infrastructure as code, but actually”

complementary hitler uses docker ▶ this video . but yeah I think infrastructure is hard but at the end it's just a tool for a job, you can use terraform, cdk, pulumi, yoke - the cycle of X for Infrastructure is bad continues :)

@saidinesh52023-11 · in “The Curse of Docker”

Obligatory Hitler uses Docker post: ▶ this video Lol @ "I'm moving everyone to Windows! Don't cry, you can run bash on Windows 10 now."

@throw0101c2023-11 · in “FreeBSD 14.0 Delivering Great Performance Uplift”

> Well, not all shops just blindly install docker, pull a docker compose stack and call it day. "Hitler uses Docker": * ▶ this video

@pmarreck2023-10 · in “Mojo is now available on Mac”

So, we'll have to run every fucking Python project in a separate Docker image as usual, then. Got it. ▶ this video

@still_grokking2020-07 · in “Ask HN: What's the worst piece of software you use everyday?”

Even I would like to tune in to Docker bashing (in this case one can actually say with confidence: "Hitler was right"[1]) the fundamental architectural problem is on the OS side. UNIX, and especially Linux, is a monolithic design. Even such an OS is able to separate user processes form each other all system parts run by concept in the form of a "big ball of mud", with "god-like" capabilities available to them by default. Sure, some internal "barriers" have been added, and per process capability dropping has been retrofitted, but this is backwards form the architectural point of view. Cutting things in peaces after the fact is almost always way more complicated and awkward compared to designing things in a modular way form the get go. This is related as virtualizing a modular OS is almost a no-brainer (conceptually). You just need to start additional instances of the required system servers / modules / whatever-you-call-that-parts. Compared to that virtualizing a monolith is like trying to construct a kind of Ouroboros: It needs to run itself (with an altered, usually constrained view on the 'outside' world) from inside of itself; and it can't just globally drop the "god-like capabilities" its execution context provides—like it would be possible with an external process. It needs to "hide or manipulate things in front of its own eyes" even "it" has the "all seeing eye". Or to put it even more metaphorical: "A God tries to use his divine powers to constrain his omnipotence so h