Live data from Hacker News

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

github.com

51–60 of 118 posts

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

#51

Makes me wonder why docker still didn't make it to the ubuntu/debian repositories. Would be such an easy net benefit

What do you mean? It's been there for years: https://packages.debian.org/docker.io

It’s an old version, and I think it isn’t supported by Docker Inc (for the reasons mentioned in the sibling comment), but it’s there.

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

#52

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 achi…

Docker Desktop on Mac is a handicapped, underprivileged mess. Docker cli for Mac with Colima is still underprivileged, but at least you can skip the bs license and Docker's gui. On Windows you can at least use Docker on WSL which works great. Why use Docker Desktop is beyond me.

Colima is the way to work with Docker on mac nowadays. I appreciate Docker Inc folks trying to get some money, but Docker Desktop is just not worth it.

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

#53
post #40

Surprised no one's mentioned lazydocker as a great alternative for Docker Desktop (on Linux/macOS/Windows) [1]. It's a fairly full-featured Terminal UI that has the benefit of running over ssh: [1] https://github.com/jesseduffield/lazydocker

Literally a few days ago: https://news.ycombinator.com/item?id=42214873

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

#54
post #46

I like when repos say "not implemented yet" or "to-do" or "working on" and the last commit was years ago. Makes me feel better about not going back to my to-dos I drop through my code. (Not meaning to throw shade on this author, just finding it comforting)

Great point! It is not shade at all, you are trying to normalize this which I like. For unpaid, volunteer, or hobby code feeling a _need_ because its public can make coding less fun or prevent people from sharing code publicly they otherwise would.

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

#56
I did something (slightly) similar via proot, called Bag [1], which I must have not described as a docker alternative: It has nothing to do with cgroups, and the cli deviates from that of docker's.

The backstory: To bypass internet censorship and deep packet inspection, I had written a proxy chain solution masquerading itself as plain html traffic. I needed it constantly running everywhere I went, but I didn't want to port it to a native android app. I wanted to run it through termux and at the time termux had no jdk/jre. Proot could spawn a archlinux env and there indeed was a jdk available.

The arch env within termux turned out to be generally more suitable for all tasks. Creating and destroying ephemeral envs with different setups and prooting into them to just run a single command is easily automated with a script; I named it bag.sh, a drastically smaller form of a shipping container.

Funny bag.sh also has a roadmap/todo in there untouched for 5 years! It's written on mobile screen hence mostly formatted to 40 columns lines to fit on the display without scrolling.

[1]: https://github.com/hkoosha/bag

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

#57
post #33

Earlier quoted context omitted.

Nah, they should have prioritized building some sort of PaaS solution like CloudRun, Render or Fly so they can sell that to enterprises for $$$. Instead they did half-baked docker swarm which never really worked reliably and then lost ground to k8s rapidly

Docker was a spinoff of an internal tool used to build exactly the type of PaaS you're describing. It was like a better Heroku and I loved it, but they shut it down when they focused on commercializing Docker itself.

dot cloud yes?

I was surprised when they shut that down too.

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

#58
post #56

I did something (slightly) similar via proot, called Bag [1], which I must have not described as a docker alternative: It has nothing to do with cgroups, and the cli deviates from that of docker's. The backstory: To bypass internet censorship and deep packet inspection, I had written a proxy chain solution masquerading itself as plain html traffic. I needed it constantly running everywhere I went, but I didn't want t…

FYI, I think you forgot some important quotes in your script. Try shellcheck?

> mkdir -p $(dirname "$2")

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

#59

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 achi…

I think Docker is really lucky that devs still think container=Docker.

Podman is in many aspects superior, while still being able to function as a drop in.

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

#60
post #46

I like when repos say "not implemented yet" or "to-do" or "working on" and the last commit was years ago. Makes me feel better about not going back to my to-dos I drop through my code. (Not meaning to throw shade on this author, just finding it comforting)

I feel like most — if not all — projects are never done. Knowing when to stop is important
Post reply on HN