Live data from Hacker News

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

github.com

71–80 of 122 posts

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

#71
post #40

Earlier quoted context omitted.

Except, docker has the same prerequisites. That's kind of the point of this excercise, to show that docker is primarily glue between existing tools, not necessarily new technology.

For me docker is three things: 1. Dockerfile concept. 2. Container image format (which is know known as OCI container). 3. Docker hub which is a repository of containers including high-quality ones. Every thing is essential and bringed innovation. Launching container is boring and not really interesting indeed.

How are the first two essential? If they’re useful anyone could improve on them

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

#73

Earlier quoted context omitted.

If you have to explain it, it's not funny. Particularly when the knowyourmeme page seems to indicate it's most prominently used by racists.

I see no mention of the word racist on that page. Can you point it out?

I don't know if it's its "most prominent" usage, but it gets used to replace the two g's in the N-word.

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

#74

Earlier quoted context omitted.

It’s consistently baffling to me how very long winded “docker run” invocations win out over config files.

Thus, docker-compose.yml files.

When I originally made my comment, I had left out any mention of docker-compose. But the parent commenter reminded me.

Focker also took a stab at a docker-compose-like implementation.

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

#76

What an utter bloat and waste of resources has Docker become. Bocker looks refreshing, most of the goodies that made docker popular and no more.

What drives me insane about Docker is the user interface it exposes. There are atleast 3 or 4 ways to do something. API is terrible (ports - 127.0.0.1:5000:5000 is confusing as fuck design). Volumes is a total mess, networking is worse and as a veteran user of docker for over 4 years on a daily basis, I still get confused about everything Docker is and is not. It is one tool that makes me feel like a moron.

I know it is an amazing tool so not to bash too much. There is a reason why I use it all the time. But goddamn it: https://stackoverflow.com/questions/24319662/from-inside-of-... and goddamn it: https://stackoverflow.com/questions/22049212/docker-copying-...

Docker needs a new command "sudo docker someone --invent new:docker-replacement:latest".

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

#77

What an utter bloat and waste of resources has Docker become. Bocker looks refreshing, most of the goodies that made docker popular and no more.

What drives me insane about Docker is the user interface it exposes. There are atleast 3 or 4 ways to do something. API is terrible (ports - 127.0.0.1:5000:5000 is confusing as fuck design). Volumes is a total mess, networking is worse and as a veteran user of docker for over 4 years on a daily basis, I still get confused about everything Docker is and is not. It is one tool that makes me feel like a moron. I know it…

While some parts of Docker are far from elegance, I find the isolation of containers from the host by default a beneficial feature, and part of the very point of containers.

The syntax of port mapping is unfortunate and unergonomic, but I suppose it just follows the syntax of port forwarding in OpenSSH :-/

For a number of improvements / different trade-offs, see Podman. But does it have a neat client for macOS, which many developers unfortunately run? (I don't.)

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

#78
post #77

Earlier quoted context omitted.

What drives me insane about Docker is the user interface it exposes. There are atleast 3 or 4 ways to do something. API is terrible (ports - 127.0.0.1:5000:5000 is confusing as fuck design). Volumes is a total mess, networking is worse and as a veteran user of docker for over 4 years on a daily basis, I still get confused about everything Docker is and is not. It is one tool that makes me feel like a moron. I know it…

While some parts of Docker are far from elegance, I find the isolation of containers from the host by default a beneficial feature, and part of the very point of containers. The syntax of port mapping is unfortunate and unergonomic, but I suppose it just follows the syntax of port forwarding in OpenSSH :-/ For a number of improvements / different trade-offs, see Podman. But does it have a neat client for macOS, which…

I think Docker is great, just needs a new interface.

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

#79
post #9
post #7

Woah! Don't know if it can be used as a proper Docker replacement (probably not), but I sure do appreciate the project as an example of how to use all the tools to implement an isolated environment. And the fact that it actually works with Docker containers (well, why wouldn' it, but still) is just a cheery on top!

> Don't know if it can be used as a proper Docker replacement The readme says "I can make no guarantees that it won't trash your system", so yeah clearly not intended for real use.

Where does Docker guarantee that it won't trash your system?

See here: https://www.docker.com/legal/docker-terms-service/

Under EXCLUSION OF WARRANTIES and LIMITATION OF LIABILITY.

Here, Bocker is also a replacement for Docker in exactly the same sense: Bocker's simple statement "I can't guarantee it won't trash your system" is a concise alterantive to a wall of legalese.

Post reply on HN