Drei bier ist auch ein schnitzel und dann hast du nichts getrunken.

Three beers are also a schnitzel and then you drank nothing.

I don’t speak German, but this phrase spoke to me.

I was going to buy the Lego Star Trek enterprise, but it was sold out before I got there. Oh well, they saved me from myself with artificial supply restrictions.

Instead, I didn’t buy anything.

It’s beautiful!

Missed opportunity for jazz.

TRS-80 then IBM PCjr here. Both hand-me-downs though.

Mom wouldn’t let me on the 386 until I could touch-type and write a program in BASIC. She was a Cobol and IBM RPG programmer.

“Vexillophile” is a word you probably won’t ever need again.

Omg thank you for the money!

It’s really not bad with full elastic bands. Make a rough square using the point of the corners as one corner and the only non-elastic fold as the opposite. Just flop the sloppy elastic to the inside. I then fold in thirds and again in thirds. Just fold the weird parts to the inside each time.

My wife still thinks it’s magic after 20 years.

I see. Yeah, that compose file is gross unless you’re running this on a dedicated vps, and even then…

I haven’t run snikket before, but it looks straightforward to me. Maybe the documentation has improved?

Don’t forget multicast (live streaming)!

Once podman is installed (iirc the network package is marked as a dependency for most package managers) and your user is configured (provide subuids/subguids), I really think podman is a simpler model. The containers you run are actually yours (not root’s) and you don’t need to be part of a privileged docker group to run them. Of course, you can run containers as root with podman too: just use sudo.

You’ll actually need to configure your user the same way for running docker in rootless mode, which should be the default.

Your dockerfile will work with podman. Your docker-compose file will too (via podman compose). You’ll have access to awesome new capabilities like pods, and defining your containers with kubernetes style yaml, and running your containers via systemd.

However, with rootless podman/docker, you should remove any/all of the USER silliness the rootful/default docker people do to protect themselves a bit from rogue processes effectively running as root and/or container escapes to root.

Tiling WM and Gruvbox. Doesn’t get any better!

Yeah, it is pretty great!

I’m building software to bridge an in house legacy system and a CLI program. It has 1 partial restful API endpoint (no delete, no patch/put). But it does have 3 cyber security suites including one that wraps the runtime. It is not a public API.

I have 4 meetings a week.

Did I mention I work from home?

Going on 22 days waiting for a firewall rule change so I can pull containers from the enterprise GitHub enlistment.

I’ve had discussions with 4 different OUs. Not one of them has been able to tell me why the firewall is different for this VM. There is no way for me to see the state of each and compare.

I’ll probably come off as a crusader, but rootless Podman is a great way to accomplish this out of the box.

Podman maps your user ID to root in the container, but you don’t need root (or a rootful socket) to run the container.

Docker also has a rootless mode now, but I’ve found no reason to go back.

Also don’t forget your locking nut key for those pesky lock nuts

Leaving only those will make for a bigger surprise a few minutes later when they take a corner at speed. Or hit a bump.

Battery powered impact driver plus a deep socket set = you can remove lug nuts or bolts (securing a wheel to a vehicle) in very quick fashion.

Here’s a compact socket set that will handle most every consumer vehicle too: https://www.amazon.com/dp/B00EHK86WS.

Almost the same one at HF where you can pay cash: https://www.harborfreight.com/12-in-drive-impact-flip-socket-set-3-piece-62491.html

You joke, but we learned “tons” and “metric tons” in elementary school.

I assume it’s the reason “metric” is used as an adjective this way.

It seems like the only time I encounter this oddness is when some upstream docker image maintainer has done a weird with users (I once went 3 image levels up to figure out what happened).

Or if I borrow a dockerfile and don’t strip out the “nonroot” user hacks that got popularized years ago.