←back to thread

Bocker: Docker implemented in around 100 lines of Bash (2015)

(github.com)
398 points emersonrsantos | 2 comments | 23 Nov 24 23:18 UTC | HN request time: 0s | source
Show context
mschuster91 ◴[24 Nov 24 00:42 UTC] No.42225102[source]▶
The fact how simple it is to re-implement a large part of Docker because all it fundamentally is a bit of glue code to the kernel is the biggest problem Docker-the-company faced and still faces.

Where Docker adds real value is not (just) Docker Hub but Docker for Windows and Mac. The integrations offer a vastly superior experience than messing around with VirtualBox and Vagrant by hand (been there, done that) to achieve running Docker on one's development machine.

replies(9): >>42225135 #>>42225179 #>>42225190 #>>42225192 #>>42225204 #>>42225325 #>>42225397 #>>42226422 #>>42227107 #
seabrookmx ◴[24 Nov 24 00:48 UTC] No.42225135[source]▶
Rancher desktop is also a viable option and free. Many including my work moved to it after Docker's new licensing kicked in.

IMO the real magic of Docker was the Docker/OCI image format. It's a brilliant way to perform caching and distribute container images, and it's really what still differentiates the workflow from "full" VM's.

replies(2): >>42225222 #>>42226682 #
1. tryauuum ◴[24 Nov 24 08:14 UTC] No.42226682[source]▶
Related to image format, has anyone tried to use alternative image formats? There was a differnt format / filesystem for containers to leverage deduplication between different images (so the node won't need to fetch yet another copy of cuda / pytorch)
replies(1): >>42226852 #
2. fire_lake ◴[24 Nov 24 09:05 UTC] No.42226852[source]▶
This is common in the Bazel community.