Containers From Scratch • Liz Rice • GOTO 2018
GOTO Conferences6 HN recommenders · 2018–2025
321K views · talk · evergreen · Uploaded 2018-06-29
Liz Rice live-codes a minimal container runtime in a few lines of Go at GOTO Amsterdam 2018. She explains namespaces, control groups and what a host knows about its containers.
HN considers it one of the best talks for understanding how containers work from the ground up.
47:18The Tragedy of systemd
linux.conf.au
1:12:27CppCon 2015: Andrei Alexandrescu “std::allocator...”
CppCon
51:18Lexical Scanning in Go - Rob Pike
GoogleFOSSSydney
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
1:48:55The Thirty Million Line Problem
Molly Rocket
59:34CppCon 2017: Matt Kulukundis “Designing a Fast, Efficient, Cache-friendly Hash Table, Step by Step”
CppCon
1:03:51VCF East: Ken Thompson interviewed by Brian Kernighan
Vintage Computer Federation
7 comments from Hacker News
1. Why Do Keynote Speakers Keep Suggesting That Improving Security Is Possible? - James Mickens [LINK] 2. James Mickens on JavaScript - James Mickens [LINK] 3. Creating containers From Scratch - Liz Rice [VIDEO] 4. 2013 Isaac Asimov Memorial Debate: The Existence of Nothing - Panelists: J. Richard Gott, Jim Holt, Lawrence Krauss, Charles Seife, Eve Silverstein. Moderator: Neil deGrasse Tyson [LINK] 5. 2016 Isaac Asimov Memorial Debate: Is the Universe a Simulation? - Panelists: David Chalmers, Zohreh Davoudi, James Gates, Lisa Randall, Max Tegmark Moderator: Neil deGrasse Tyson [LINK] 6. Zig: A programming language designed for robustness, optimality, and clarity – Andrew Kelley [LINK] 7. Concurrency Is Not Parallelism - Rob Pike [LINK]
Liz Rice has done some awesome on-stage live coding, including a very small container runtime in go. [VIDEO]
>I wish there were a tool that could just record everything [...] if you "know" everything, then notes serve no purpose. I guess the completeness of your proposed "auto-memorize-everything" solution depends on what style of notes a person writes. A lot of my notes are annotations or personal commentary that don't exist in the sources of the url text or video. Here's an example of that type of notes I often take... E.g. I found some links that explain how one can grok "Docker" by going through the learning exercise of re-inventing it from basic os features with homemade scripts. But I wrote my own personal notes (in "##")about the limitations of the explanations in the urls: ## these tutorials explain the verb (runtime) but not noun (artifacts of image file) [LINK] [VIDEO] Because content cannot meta-analyze itself and enumerate all the ideas and concepts that are not embedded in its own text, it means a hypothetical indexing engine that converted the 2 links above to searchable data still would not retrieve the extra meta information I wrote. A lot of good notes are generated from your own brain. EDIT add to categorize different types of "notes" to aid discussion: (1) notes as memorization aid such as copying facts : a user writes a note that says "1 inch equals 25.4 millimeters" after seeing it on a webpage or something. So the "universal-record-and-index-everything" would help make these type of notes obsolete because one could just skip writing that note down and just reca
This will be a fun read, thanks! If you'd prefer to see the same ideas in video form, Liz Rice gave a pretty good prsentation on this same topic in 2018: [VIDEO]
Indeed a bit of an odd request, but I'm partial to Liz Rice's "Containers from Scratch" talk. Probably one of the most enlightening presentations I've seen in recent years, full-stop. [0] [VIDEO]
Big fan of the following talk that explains how containers work from the ground up. Containers From Scratch • Liz Rice • GOTO 2018 - [VIDEO]
I loved this hands-on presentation Containers From Scratch by Liz Rice from few years ago [VIDEO] . Today, Linux containers in (less than) 100 lines of shell by Michael Kerrisk was published [LINK] .