Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
NilsIRL
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
1.
▲
Paged Out Issue #4
(pagedout.institute)
4 points
by
NilsIRL
2y ago
|
0 comments
2.
▲
by
NilsIRL
2y ago
> 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?
3.
▲
by
NilsIRL
3y ago
I moved zig-clap to zon. Was alright. I appreciate that absence of a package registry.
4.
▲
by
NilsIRL
3y ago
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 arbitrary executables so not sure how that would work eithe
5.
▲
by
NilsIRL
3y ago
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.
6.
▲
by
NilsIRL
3y ago
don't give me ideas ;) (yes)
7.
▲
by
NilsIRL
3y ago
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 running from dockerc-generated executables run inside a conta
8.
▲
by
NilsIRL
3y ago
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 container. > What about using Zon for deps, instead
9.
▲
by
NilsIRL
3y ago
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 fuse filesystems with the error mes
10.
▲
by
NilsIRL
3y ago
I hadn't heard of Apptainer/Singularity before but it doesn't seem to provide the ability to create standalone executables.
11.
▲
by
NilsIRL
3y ago
> 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 you're not trying to implement volumes. &
12.
▲
by
NilsIRL
3y ago
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 extracts itself which means there is quite a bit of
13.
▲
by
NilsIRL
3y ago
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.
14.
▲
by
NilsIRL
3y ago
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. I have been wanting to try out Zig 2. It fit the r
15.
▲
by
NilsIRL
3y ago
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 statically link some of the QEMU dependencies or write a
16.
▲
by
NilsIRL
3y ago
Yep, this is a known issue. It also existed in the past with normal docker. https://github.com/NilsIrl/dockerc/issues/6
17.
▲
by
NilsIRL
3y ago
> 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 somehow configurable? I'm not too sure what res
18.
▲
by
NilsIRL
3y ago
> 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 Windows binaries? That's what I'm imaginin
19.
▲
by
NilsIRL
3y ago
> 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. I got an initial demo working on MacOS but I&#
20.
▲
by
NilsIRL
3y ago
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. Because the image isn't copied whether the ima
21.
▲
by
NilsIRL
3y ago
Yep! It works with any docker image!* *: https://github.com/NilsIrl/dockerc/issues/6
22.
▲
by
NilsIRL
3y ago
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/ )
23.
▲
by
NilsIRL
3y ago
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 the squashfs and overlayfs are mounted and the container is
24.
▲
Show HN: dockerc – Docker image to static executable "compiler"
(github.com)
374 points
by
NilsIRL
3y ago
|
135 comments
25.
▲
by
NilsIRL
3y ago
This already exists: https://mfi.apple.com/
26.
▲
by
NilsIRL
3y ago
Karpathy just tweeted about it [0]: > Hi everyone yes, I left OpenAI yesterday. First of all nothing "happened" and it’s not a result of any particular event, issue or drama (but please keep the conspiracy theories coming as th
27.
▲
The AI Effect
(en.wikipedia.org)
3 points
by
NilsIRL
3y ago
|
0 comments
28.
▲
by
NilsIRL
3y ago
Google News?
29.
▲
Isochrone Map
(en.wikipedia.org)
2 points
by
NilsIRL
3y ago
|
0 comments
30.
▲
The Suidperl Story
(mattmccutchen.net)
1 points
by
NilsIRL
3y ago
|
0 comments
More ›