It’s not the postgres db, it’s the internal pictrs db.

Fix your docker volume permissions so pictrs can write to the folder

They can’t give, but they can purchase.

Nice job!

Just an idea: I bet you could probably squeeze in a disassembled usb hub to make it easier to get those front ports.

Something like https://a.aliexpress.com/_mNBftvQ

I’ve got tons of their socks in a variety of styles and I’ve never had an issue.

Gotta get the Darn Tough socks. No more tossing in the trash, they have a lifetime warranty but they also last forever. After many years I finally just sent like 12 pairs in and got all new ones.

Yes

That’s correct. You’re telling docker to bind to that specific network interface. The default is 0.0.0.0 which listens on all interfaces.

https://github.com/containrrr/watchtower is a bit cleaner than that

Bro, just docker-compose pull && docker-compose up -d

I’m appreciating how rapid the releases have been coming lately.

You could just swap the two disks and see if it follows the drive or the link.

If the drive, rma it. I don’t put a lot of faith in smart data.

Usually means a failing drive in my experience.

Ok that’s impressive! I had no idea.

Is it that prevalent? Seems like anti cheat works, at least I don’t see much of it in the games I play. Are y’all seeing cheaters frequently? What games?

The file handle of the directory changes when you mount the nfs on it, and docker is still looking at the old file handle.

It’d probably work if you mounted nfs to a folder inside that one, or moved your docker mount one level up.

Otherwise you’ll need to get your container to restart after the mount is attached. You could do this with a health check for the container that checks the files are there, and restart the container if they’re not. Or you could just fix your boot order and set nfs as a dependency for docker.

Would be better if you made it “a joke about maize”

Look at workstation cards. Things like the T1000 for example.

No grace period I’m aware of, just removal vs purging. If it’s been removed it can be edited in the db to restore it. Once it’s been purged, it’s gone for good.

Ntfs isn’t going to care or even be aware of the hypervisor FS, zfs or btrfs would both work fine.

Making sure you don’t have misaligned sectors, is pretty much the only major pitfall. Make sure you use paravirt storage and network drivers.

Edit: I just realized you’re asking for the opposite direction, but ultimately the same guidelines apply. It doesn’t matter what filesystems are on what, with the above caveats.

FYI setting my zigbee channel resolved all of my zigbee issues, all 3 networks run flawlessly in parallel for me: https://www.metageek.com/training/resources/zigbee-wifi-coexistence/