Viewing profile — NilsIRL

> I did this before I learned how to finish projects Very curious about this. As do many people I struggle to finish projects. How does one learn this skill?

I moved zig-clap to zon. Was alright. I appreciate that absence of a package registry.

Unfortunately cosmopolitan wouldn't work for dockerc. Cosmopolitan works as long as you only use it but container runtimes require additional features. Also containers contain arbi…

I thought it was an acceptable trade-off given that AppImage has the same limitation. An alternative is to extract the image to disk but that has quite a bit of overhead.

don't give me ideas ;) (yes)

They have the same goal but achieve it differently. dockerc allows you to re-use your existing docker images without having to spend time packaging something up. The applications r…

I don't expect this to interact with the docker daemon in any way. With networking executables generated by dockerc behave in the same way as a native application running outside a…

dockerc can, the produced executables cannot, at least not without some tweaking. Even if you path through `/dev/fuse` and `/usr/bin/fusermount3` (using -v) it fails the mount the …

I hadn't heard of Apptainer/Singularity before but it doesn't seem to provide the ability to create standalone executables.

> Running on Windows/macOS was also the context in which I meant to ask about filesystem mounts. That's not an issue because the mounts are within the Linux VM. At least as long as…

That's really cool. I didn't know about that. Thanks for sharing. There's a few things that seem to make it unsuitable for the intended use case of dockerc: * The container extract…

Yeah, I don't think this makes that much sense for internal distribution. Especially if you use kubernetes. The use case is for distributing software to end users.

The main reason Zig was chosen is because the project was started at a hackathon[0] at which there was a prize for "best use of Zig". Beyond that there were also other reasons: 1. …

Thanks! > Will this run ok on a Mac? I've managed to make it work but unfortunately not in a way that produces portable binaries. I just need to figure out how to selectively stati…

Yep, this is a known issue. It also existed in the past with normal docker. https://github.com/NilsIrl/dockerc/issues/6

> How do you deal with resource sharing? This starts with just filesystem mounts, but also concerns ports, possibly devices, and probably many other things I'm forgetting. Is this …

> How static are we talking here? Enough for the executables to run everywhere. So I'm happy for system libraries to be dynamically linked. > But do you even want to distribute Win…

> It would make sense that a tool like this would prioritize MacOS/Windows support above all else. Yep, unfortunately I've not had the time to make it work well on those platforms.…

It will depend heavily on the docker image you're trying to ship. For example with macos-cross-compiler[0] the resulting binary is over 2GB. With python:alpine[1] it's only 25MB. B…

Yep! It works with any docker image!* *: https://github.com/NilsIrl/dockerc/issues/6

Thanks for the bug report! Just pushed a change that fixes it (and made a new release with the issue fixed: https://github.com/NilsIrl/dockerc/releases/ )

Yep pretty much. The executables bundle crun (a container runtime)[0], and a fuse implementation of squashfs and overlayfs. Appended to that is a squashfs of the image. At runtime …