Hitler uses Docker
nukemtube0 HN recommenders · 2016–2025
1.2M views · comedy · dated · Uploaded 2016-04-10
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.
19:10Velocity NY 2013: Richard Cook, "Resilience In Complex Adaptive Systems"
O'Reilly
52:35Debugging Under Fire: Keep your Head when Systems have Lost their Mind • Bryan Cantrill • GOTO 2017
GOTO Conferences
51:22USENIX Security '18-Q: Why Do Keynote Speakers Keep Suggesting That Improving Security Is Possible?
USENIX
59:56AWS re:Invent 2018: Amazon DynamoDB Deep Dive: Advanced Design Patterns for DynamoDB (DAT401)
Amazon Web Services
2:58The Loving Trap
Ben Woodhams
28:36Literate Devops with Emacs
Howard Abrams
19:08NaN Gates and Flip FLOPS
suckerpinch
9:55Erlang The Movie II: The Sequel
gar1t
9 comments from Hacker News
How did I miss [VIDEO] the first time around? I thought it was submitted but it doesn't show up on search. userland proxy! just use openstack for all I care. wow, that was really entertaining.
Aha, the chancellor( [VIDEO] ) will feel great to see that finaly he can eliminate IaaS/vms and use docker in production env.
People joke about everything. Just understand the context and don't take it so seriously. I live and breathe containers but still get a kick out of this: [VIDEO]
This 'Hitler uses Docker' video seems to be a pretty similar viewpoint on Docker and the world. [VIDEO]
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
So, we'll have to run every fucking Python project in a separate Docker image as usual, then. Got it. [VIDEO]
Obligatory Hitler uses Docker post: [VIDEO] Lol @ "I'm moving everyone to Windows! Don't cry, you can run bash on Windows 10 now."
> Well, not all shops just blindly install docker, pull a docker compose stack and call it day. "Hitler uses Docker": * [VIDEO]
complementary hitler uses docker [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 :)