Live data from Hacker News

Show HN: dockerc – Docker image to static executable "compiler"

github.com

91–100 of 150 posts

Re: Show HN: dockerc – Docker image to static executable "compiler"

#91

So what does this mean? That I can finally ship portable Ruby executable without requiring the end user to install Ruby?

You should also be able to do that with Cosmopolitan/APE.

Would you be able to expand on this, my impression is that these tools build a custom c program instead? Thanks

Re: Show HN: dockerc – Docker image to static executable "compiler"

#94

Earlier quoted context omitted.

Im surprised no one mentioned that the program the unstable ranter wants is essentually a social media stalker app to find people on all social media sites. Perhaps some barriers to use are good sometimes.

If they don't want people to find their social media profiles, then they shouldn't have social media profiles.

Unfortunately to access Lynda, you have to make a LinkedIn account

Re: Show HN: dockerc – Docker image to static executable "compiler"

#95
post #77

This is really great. I have been trying to get my docker to be more distributable. Right now it's just a simple python script in a python env inside a docker container inside a QEMU container to automate a click and then netcat something. Pretty sweet. It's only like 20GB, so pretty lightweight by modern standards.

/s this please, people might get some ideas otherwise...

Re: Show HN: dockerc – Docker image to static executable "compiler"

#96
post #76
post #56

Earlier quoted context omitted.

I wish we could have something like exes with permissions. Similar to browsers. So I could run an arbitrary executable, but the OS level APIs would be blocked unless the user allowed the given permission.

What's wrong with flatpak for that? Honest question as I don't know that space really

it should not be the flatpack who decides its own appropriate permissions, but the owner of the OS where the flatpack runs. Even when--especially when--, the permissions profile disagrees with that requested by the developers. Whatever permissions the flatpack "requires" should be irrelevant. Only those granted by the user will be given.

Flatpack and snap and other systems that conflate packaging and permission management get it totally wrong. Permission management is an OS-issue, not a packaging issue. Thus, distributing a plain static executable or a python script should be just as safe as a "safely packaged" app.

Re: Show HN: dockerc – Docker image to static executable "compiler"

#97
It's interesting. According to the source code, it uses FUSE to mount the container's internal filesystem. This means that the compiled binary will either need root privileges to run, or the user must have configured FUSE to allow non-root mounting. Not ideal, but there's not much of an alternative either.

Re: Show HN: dockerc – Docker image to static executable "compiler"

#98
What about Cosmopolitan and WASM? ;)

Cosmopolitan libc allows compiling of a single binary that runs on multiple OS platforms without modification – maybe Dockerc could use this to create a more universally portable container binary?

WASM binaries could run in the browser, or another WASM VM, including securely sandboxed environments that spin up fast.

I understand that newer Docker builds can use WASM under the hood so WASM in WASM would be funny, it seems if that were the case, maybe extracting the WASM with a more thin wrapper would be better?

Re: Show HN: dockerc – Docker image to static executable "compiler"

#100

Earlier quoted context omitted.

If they don't want people to find their social media profiles, then they shouldn't have social media profiles.

Unfortunately to access Lynda, you have to make a LinkedIn account

Who is Lynda?
Post reply on HN