GustavoM

Nothing too shabby, but still. To run it you need docker, and after that just type

docker run -it --rm --log-driver none --read-only --net none --cap-drop=ALL --security-opt=no-new-privileges defnotgustavom/pixfire4

...and you will be greeted with a little, small, very pixelated bonfire.

"Why docker and not just a simple command?"

Mostly because of those two flags: --read-only and --net none. Can't get better than this. :^)

This also came up while in a self-learning process, but I don't want to "flex" it here.

Title. Mostly because of two flags: --read-only and --log-driver.

Title. A cheat sheet for this would be lovely.

Thanks in advance.

Title. I'm trying to compile this but I can't seem to do so with node.js.

Thanks in advance.

Is there any difference from one another? I keep hearing that using chargers is absolutely a no-go and that power supplies are much safer and better overall. Do you guys confirm this?

Thanks in advance.

ser*, and said non-root user being "nonexistant" (i.e set via ENV)? Can such container -STILL- be exploited/breached through malicious means? Forgot to mention that its a DOCKER container @ title, but there you have it. Just curious.

Thanks in advance.

...and the logic behind this is a really simple one:

Lower cone of fire = CoF tightens faster while ADS'ing.

And the "long short story" behind this is that I saw this video, went for the same "I'm gonna try to mimick this" shenanigans and it worked. Hell, I even managed to down those typical "chain headshotting me like theres a magnet on top of my nose" players. And yes, more than once, even while completely rusty (It's my second day back in the game after a long hiatus.). Also had a couple situations where I died, but made the heavy wipe both of his shield ability and its "basic" shield (Not a normal occurrence before then, but right now it is.)

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.)

Title. Long,short story: creating or editing files with nano as my non-root user gives (the file) elevated privileges, like I have ran it w/ sudo or as root. And the (only) "security hole" that I can think of is a nextdns docker container running as root. That aside, its very "overkill" security-wise (cap_drop=ALL, non-root image, security_opt=no_new_privileges, etc.).

It's like someone tried to hack me but gave up halfway. Am I right or wrong to assume this? Just curious.

Thanks in advance.

Title. I'm trying to expose my nextdns ip (running on docker) to another network.

Thanks in advance.

Title. Just wondering if I did something bad/terrible with it. Link is @ title. Check the image tag @ its repo to see how it was built. And before someone asks... the Docker lemmy community is really dead so I had to resort to you guys. Sorry, I guess.

And thanks in advance.

For those who enjoys craving a bit of a "nerdy feel" to your daily routine, have at it. Just slap this bad boy on any raspberry pi 4 with a touch screen, and enjoy your pseudo-reality at the cost of "almost nothing". Steps on how to run it are included in the link @ title as always.

• Pros:

- Isolated, does not run as root, ready to use, no need to go through lengthy installations

• Cons:

- You have to type something to use it.

Have fun.