Her 50 lines of GO lang code hides over a 100 levels of OS level abstraction, and you confidently say that you think you understand what a Docker container is. That's laughable.

@@sussus4914 so why don’t you give a talk on those 100 lines of OS abstraction?

@@sussus4914precisely why they are abstractions, so you don’t get distracted with boilerplate

For ubuntu: apt-get install lxc sudo lxc-create -t ubuntu -n yakkety # now use this for the chroot /var/cache/lxc/yakkety/rootfs-amd64 # I still had to `run mount -t proc proc /proc` to get ps to work though, not sure how to get around that

I could do this by creating a chroot filesystem. help.ubuntu.com/community/BasicChroot

debootstrap stretch test1

Efficiency. You can build a completely self-contained binary that does everything. If you add https or a straight TLS socket you only need the exe and a cert file... it's super clean. With Python you may have versioning/suppor issues. Java is a pig - it latches onto cpu+memory resources. Not really apropos. C++ is ok for this, but younger engineers may not know it + unix command programming in C++ can be a bit tricky. Golang makes it (and certain other tasks) pretty straightforward. I would use either C or golang. Maybe Rust but I don't know it yet.

@@RockwellAIM65 yeah I think outside of Go, c++ would be the best choice

@@piyushsingh178 A C based solution would be clean; you'd have to add lots of external libraries tho' ... would have been nice if C had a standard add-on for managing databases, doing all the simple network type transactions w/ a second thread perhaps (application+background processing thread) + an easy-to-interface string based hierarchical data store. C++ wasn't really necessary... it turned into the Cobol of the 1990s!

yes there is a way, how to do that i have no idea

How is she faking it ?

When did she mount an alternative fs? When she mounted proc? Or do you mean the chroot? The chroot source dir already contains a file system hierarchy because the child process quite literally has a different root, and would not be able to access anything “outside”. Without this, calling /bin/bash would do nothing since that path wouldn’t even exist. Mounting proc is required purely because of the chroot. LXC isn’t a “native” feature, cgroups are. LXC is just one of several system virtualization frameworks such as libvirt or systemd-nspawn. Her talk was about making containers from scratch, which I’ll interpret as a LSB compliant OS with a vanilla Linux kernel. LXC under the hood does pretty much the same thing as her code. Go ahead and check out their github; it’s all open-source. LXC has more features, but I’m pretty sure it’s quite a bit bigger than 60-ish lines

For me it was the fact that I always sort of imagined containers as this mystical thing. I use them all the time, but I never really thought about how they are created or work under the hood. Seeing this video really opened up my mind to how simple it really is. Of course I know there is so much more to containers than that, but just seeing how she could give the processes their own namespace, their own processes, their own “isolation”, is really interesting and impressive for just 56 lines of code.

If you follow what it shows, you'll also see what happened. It gave the program it run isolation (not messing with the environment outside), it's own root (not seeing outside a particular directory), and a few other similar things. That's what a container like Docker does, using several OS provided utilities (like chgroups, chroot, etc), like this program does (in a more basic way)

Yis

Why the need for programming languages at all? After all, all they do is translate human readable code to bunch of machine instructions. Just write those instead.

Docker is written in go.

She compared the length of her code to Docker's in the end, so it had to be written in Go.

Yes, it could be done in plain bash. But it would be hell to maintain, scale, and make able to run arbitrary containers. Whereas this shows how a container manager like Docker does it (of course with much less functionality here), so it can be more easily extended configurable etc.

Trust me, nobody is surprised that a flat earth proponent is not able to understand something very basic.

The point was to run a container without docker.

Isn't it OBVIOUS? To show how the basics with which a container system like Docker can be implemented...

What was the point of this comment again?

Very skewed view of the tech world where most of the innovation is done by women since the beginning of the time.

@@shailynortiz def not true

@@shailynortiz lol, not true

@@shailynortiz I think both views are skewed. Females are not recognized for their accomplishments in the tech world, but saying they've done the majority of innovation in that field is simply not true.

that's a cool story

You got to be running the TempleOS or something to be that arrogant.

Alex Kozadaev nope, just not a proprietary os on proprietary hardware both designed to restrict your freedoms.

An Enemy nope. Linux.

Corey Reichle makes sense. I also prefer Linux and OpenBSD and cannot see myself ever buying a Mac, however as we can see in this presentation despite of what you said it won’t stand in a way of doing cool stuff either :)