Hacker News Reader

Hacker News

Comment by arjvik | Hacker News Reader

Parent Full thread

arjvik

Good friend built dockerc[1] which doesn't have this limitation!

[1]: https://github.com/NilsIrl/dockerc

View on HN

That screenshot in the readme is hilarious. Nice project.

Instead it requires QEMU!

I can't tell what this does from the readme. Does it package a container runtime in the exe? Or a virtual machine? Something else?

Looks like MacOS and Windows support is still being worked on.

lol guy makes a fair point. Open source software suffers from this expectation that anyone interested in the project must be technical enough to be able to clone, compile, and fix the inevitable issues just to get something running and usable.

Thank goodness; solving this "problem" for the general internet destroyed it. Your point seems to be someone else should do that for every stupid asshole on the web?

I'd say that a lot of people suffer from this expectation that just because I made a tool for myself and put it up on GitHub in case someone else would also enjoy it that I'm now obligated to provide support for you. Especially when the person in the screenshot is angry over the lack of a Windows binary.

But will this run inside another docker container?

I normally hate things shipped as containers because I often want to use it inside a docker container and docker-in-docker just seems like a messy waste of resources.

Doesn't podman get around a lot of those issues?

Aw hell, more band-aids because people don't want to get software distribution done right.

Can we please go back to the days of sudo dpkg -i foo.deb and then just /usr/bin/foo ?

I am still using "ar x" and "tar xvf" for .deb files on Void Linux, because some projects only release .deb files!

Docker in Docker is not a waste of resources, they just make the same container runtime the container is running on available to it. Really a better solution than a control plane like Kubernetes.

Aren't you describing docker-out-of-docker rather than docker-in-docker?

No, you're running docker inside a docker container. The container provides a docker daemon that just forwards the connection to the same runtime. It's not running two dockers, but you are still running docker inside docker.

https://medium.com/@moshedana058/understanding-docker-in-doc...

Docker is not emulation so there's no waste of resources.

Reply on news.ycombinator.com