Almost everyone uses docker, but without really knowing what it is or does under the hood.
To be fair, it just works and the whole thing with namespaces and images is a dry topic.

This talk will show you how Docker works, the fun way!

The most important thing to know is, docker is just a product name for a program that uses several already long-existing technologies to create its containers.
Well, it's a little bit more, since it provides the docker hub infrastructure, a vital part of docker's success.

Since understanding docker means understanding the underlying principles, you will see how to create your own container without using anything docker.
To do this a small program is written in golang (you don't need to know the language) that creates a real container.

During this process, you will get to know and, most importantly, understand how docker works.

Why would you want to know how Docker works internally?

If you know the concept by heart, working with docker and especially debugging weird stuff it does from time to time becomes a breeze.
‚ÄčAdditionally to the things above you will get deeper knowledge about images, the second most important thing apart from containers.

The talk is aimed at programmers who struggle to understand docker or just want to know more about a technology they use every day.

Be aware: How to use Docker in daily business is not part of this talk.

Comments

Comments are closed.

Bastian at 14:10 on 8 Jun 2018

I love when speakers code during talks.

Super!
Couple of lines on Go describe the basics of docker

Dennis C. at 11:25 on 9 Jun 2018

Quite interesting talk and a good explanation into how things work under the hood.

Marv at 12:16 on 9 Jun 2018

I liked the storytelling at the start and the live coding in the slides.

When learning a new tool or technology it can be really helpful to understand the basics, and this talk teaches the basics of docker, with live coding examples.

Excellent way of showing how docker works under the hood.
Even though there were some bits that could be improved on the slides, but speaker mentioned that himself during the talk, and I'm sure its fixed for the next talk.