I set up a very straightforward Godot dev environment yesterday using toolbox which is built on top of rootless Podman.

• Create a new fedora toolbox
• Enter toolbox
• Install DotNet dependencies, git, etc with dnf
• Install Godot binary from release page
• Turns out there were other dependencies I needed
• Godot wanted a few Wayland libs on the container, so I installed Weston (maybe overkill)
• Godot wanted libxrandr so I added that too
• Godot just works ™

The nice thing about toolbox is that it uses my native host Wayland compositor. So whatever I have running in the toolbox can be interacted normally through sway (my host WM).

You can either distribute a container image with your given toolbox configured, or just document the setup steps.

You can host docker volumes over NFS, but the actual container images need to exist on a filesystem that supports overlay (which NFS does not) unless you want things to be slow as shit. And I really do mean miserably slow. A container image shared over NFS will take forever to spin up because it has to duplicate the entire container filesystem instead of using overlays, and then it’ll blow up your disk usage by copying all these files around instead of overlaying them. It’s truly unusable.

From that same discussion thread:

We plan on supporting any token/nft/coin for tipping, awards, curating, less captchas, etc. Each subplebbit owner should be able to create their own tokens or nfts to monetize their effort and incentivize their users to participate. Avatars will also be curated NFTs.

The protocol does not use blockchain for data, but the web service itself looks like it would use crypto and NFT to manage aspects of user identity, spam prevention, and monetary incentive.

Eh, maybe. Back during feudalism, emancipation of serfs was also considered theft from the nobles who owned the land (and thus the serfs who worked it).

Sometimes governments implemented programs to reimburse the nobles for losing “their” serfs, and sometimes not. Now that we’re a couple centuries removed from that drama, we generally accept that the destruction of feudalism was a good thing, regardless of whether it was theft.

There used to be a similar bug in the Roku jellyfin app.

If you can recreate the subtitle issue using test file 5 from this repo, it might be worth submitting a bug report. https://github.com/ietf-wg-cellar/matroska-test-files

I once had a directory in /tmp called etc which contained subdirectories for something I was migrating.

I thought that I was in /tmp when I ran rm -rf etc… I was actually in /

Look up the GPU on these charts to find out what codecs it will support: https://developer.nvidia.com/video-encode-and-decode-gpu-support-matrix-new

NVENC support will tell you what codecs your GPU can generate for client devices, and NVDEC support determines the codecs your GPU can read.

Then compare it with the list of codecs that your Intel can handle natively.

If you want to move your containers to a different location, look into configuring docker’s data-root: https://stackoverflow.com/questions/24309526/how-to-change-the-docker-image-installation-directory

You copy /var/lib/docker to a new location and update /etc/docker/daemon.json

I will say: Moving data-root to an NFS mount isn’t going to work well. I’ve tried it, and docker containers rely on filesystem features to run their overlays. On an NFS, this feature isn’t present, so your services will duplicate the container’s entire filesystem. This will tank your performance and is basically unusable for anything but trivial examples. Docker data-root basically needs to be a “physical” disk.

I’ve had no issues using NFS shares mounted as docker volumes. It’s just the data-root where it’ll fail.

If you’re doing it from scratch, I’d recommend starting with a filesystem that has parity checks and filesystem scrubs built in: eg BTRFS or ZFS.

The benefit of something like BRTFS is that you can always add disks down the line and turn it into a RAID cluster with a couple commands.

Yep, the problem was that docker started before the NFS mount. Adding the dependency to my systemd docker unit did the trick!

isn’t it an annoyance having to connect to your home network all the time?

It’s less annoying than the gnawing fear that my network might be an easy target for attackers.

Proliant G9 is an EoL server that hasn’t been sold since 2018. Meanwhile, Debian bookworm released last year. I’d be surprised if the problem were that your installer gave you a kernel that’s too old.

What is the output of ip addr show?

It might also be worth ruling out low-level issues:

• Check for anything strange in the BIOS related to disks (fwupdmgr can automatically install BIOS updates from a live Linux session. I don’t know if Bazzite does this)
• Try using a different SATA port
• Run some SMART tests on your drives

Not that I was ever interested in being military, but I was at a lunch with two older lifelong army retirees. They kept talking about how military service broke their bodies and politicians won’t cover their medical costs. These injuries were independent of any combat: It’s just expected that you sell every part of yourself when you sign up.

Who wants to be 45 years old with a limp, be unable to hear a quiet conversation, and have horrible back problems?

As someone who has owned enterprise servers for self-hosting, I agree with the previous comment that you should avoid owning one if you can. They might be cheap, but your longterm ownership costs are going to be higher. That’s because as the server breaks down, you’ll be competing with other people for a dwindling supply of compatible parts. Unlike consumer PCs, server hardware is incredibly vendor locked. Hell, my last Proliant would keep the fans ramped at 100% because I installed a HDD that the BIOS didn’t like. This was after I spent weeks tracking down a disk that would at least be recognized, and the only drives I could find were already heavily used.

My latest server is built with consumer parts fit into a 2U rack case, and I sleep so much easier knowing I can replace any of the parts myself with brand new alternatives.

Plus as others have said, a 1U can be really loud. I don’t care about the sound of my gaming computer, but that poweredge was so obnoxious that despite being in the basement, I had to smother it with blankets just so the fans didn’t annoy me when I was watching TV upstairs. I still have a 1U Dell Poweredge, but I specifically sought out the generation that still let you hack the fan speeds in IPMI. From all my research, no such hack exists for the Proliant line.

The problem with chromebooks is that the base specs are pretty shit. A lot of them have 4 GiB of RAM and maybe 16GiB of disk if you’re lucky.

They were designed to be thin clients to connect students to the internet, and little else. Maybe they could be hacked into something useful, but I don’t think it’ll ever make a good PC. They were always destined for the landfill.

Meanwhile, the best thinkpads were quality machines back when they came out. IMO, that’s why they’re still so versatile today. Free software can’t fix bad fundamentals.

I’d recommend BTRFS in RAID1 over hardware or mdadm raid. You get FS snapshotting as a feature, which would be nice before running a system update.

For disk drives, I’d recommend new if you can afford them. You should look into shucking: It’s where you buy an external drive and then remove (shuck) the HDD from inside. You can get enterprise grade disks for cheaper than buying that same disk on its own. The website https://shucks.top tracks the price of various disk drives, letting you know when there are good deals.