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.

That one didn’t work for me, but here’s an archive link: https://archive.is/0oKSF

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?

It is. I got it working wirelessly once for shits and giggles using USB/IP.

Dug up the comment: https://lemmy.world/comment/3637478

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!

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

I have entire conversations and then 5-30min later realize I had a conversation and panic because I can’t remember anything about it except that words were exchanged.

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.

More perspectives:

If you divided this amount equally across every human on earth (8,142,000,000), they’d each get about $61.

Only 9 sovereign wealth funds hold more value. https://en.m.wikipedia.org/wiki/Sovereign_wealth_fund

Cheddar Cheeseius.

Oh man, I grew up with those intercoms on the top right.

That’s what qualified as a baby monitor. It had a lock button so it could constantly transmit.

So weird to see them again.

Quesabirria from the local taco place. Didn’t even realize we were celebrating!

It’s perfectly representative of the opinion asked for.

Getting down voted is hilarious, because we’re admitting “fuck you, this is actually awesome.”