Long, short story: CLI animation with some minor annoyances. “Handcrafted” most of em out of the .c file, followed by a bunch of gcc flags. Made it distroless, and this came up. Then my “sharing itch” started after checking the memory usage of the container at a whooping 0 bytes. (I know it must be way more than that, but still.). Just curious if I screwed something up or not. Also, c/Docker is really dead so I had to resort to you guys.
docker run -it --rm --log-driver none --net none --cap-drop=all --read-only --security-opt=no-new-privileges defnotgustavom/nyancat
Downvotes are to the left if you just don’t care and need that dopamine/self-validation hit, I guess. (Just saying since last time I shared a simple command, with code and all, and I got downvoted to oblivion plus my thread deleted for no apparent reason, so eh.)
Why wrap a CLI tool in a docker container? Wouldn’t it be simpler to directly compile nyancat to multiple architectures if the goal is to make it run on all platforms?
If you really wanted to, you could create an actually portable executable :)
That looks really interesting! Does this exist for other languages like Rust?
Yes, some people tried it, and it seems to work: https://ahgamut.github.io/2022/07/27/ape-rust-example/
Very interesting, might have to check that out sometime
Like go?
Because I’m doing this as a “self-learning” process. Plus, docker is an excellent tool and even “silly” images like this one can give me an edge while looking for (more) jobs, so there’s that. Coding could grant me the same “edge” as well yes, but docker has “more value” since it requires you to code -AND- to have some knowledge/depth regarding typical “dockerization” processes.
I would imagine it’s just to experiment with docker