Mama told me not to come.
She said, that ain’t the way to have fun.
I’m looking at moving my NAS to it.
I currently use openSUSE Leap, so to prep for the switch, I’m moving everything to podman.
I’ve never had a system update go bad on Leap, but I am being impacted by old system packages but don’t want to jump to Tumbleweed. I’m hoping this will give me a more up to date base and force me to put things into containers properly.
All of those should be fine, the main caveats w/ Linux are:
Blender works perfectly fine, gaming on Steam and Heroic works well, emulators work well, and while I don’t know anything about Linux music production, I know there are software options available.
Anyway, I recommend buying a separate disk and trying Linux out. That way you don’t touch your current Windows install while messing w/ stuff.
Been messing around w/ podman, and after hours of slamming my head against the wall, I decided Seafile isn’t worth it. :) It launches a bunch of stuff inside one container, and I just couldn’t figure out how to get that to work w/ quadlet (worked fine w/ podman kube play though).
I got forgejo set up and now I’m looking into setting up runners so I can finally migrate off hosted gitlab onto my own forgejo instance.
Some other things I’m planning on doing this week:
If I get time, I want to install openSUSE MicroOS onto my NAS and start migrating everything to it (from openSUSE Leap). I really like the idea of an immutable base OS, and my NAS is already 90% containers (pretty much just Samba left). I need to fix some permission issues anyway (keep having to chown my videos so samba and jellyfin can work together), and this should make things a bit more obvious.
I’ll probably also start a blog about my self-hosting journey, because the info around podman is kinda sparse, especially when it comes to quadlet.
Edit: got OCIS working, but it was a bit of a pain. Starting that blog really sounds like a good idea…
In an ideal world, sure, but all software has bugs (example vulnerabilities here). Proper security design doesn’t ask “how can X happen?” but “what if X happens?” If you break out of a docker container, you have root access to the system because the docker daemon runs as root.
With podman, there is no root docker daemon, so you’d also need privilege escalation in addition to breaking out of the container.
Put them in a pod and it’s just systemctl --user start <name>-pod or sudo systemctl start <name>-pod. A pod is basically a compose file, but split across multiple files instead of chunks of yaml.
this post of mine
You have a typo in the title for the section about backups.
In that post you use the compose format. Have you used quadlet? My understanding is that’s the “preferred” way to do things, I’ve also had some issues and am trying to decide if it’s worth it. Any thoughts?
I’m looking into Technitium, which doesn’t get a ton of attention here. It looks to be much more feature packed than PiHole (DNS over HTTPS, for example), and similar to AdGuard Home.
Um, what does that even mean?
Edit: Looks like it runs a VM. So some overhead, but still cool.
Yup. As always, do backups for anything important. Semver is certainly helpful in communicating scope of changes.
Don’t trust Semantic Versioning claims, devs can and so screw it up. That said, if they claim to follow semver, it’ll probably work, but I’ve had patch versions break my code before.
Nice!
Is devrandom your router or something?
What happens if you decide to use Fedora or Ubuntu on two devices?
Sounds like a good option for a VPS.
What happens if you add another RPi?
Nah, just a huge fan of barley tea.
Hmm, what does localhost.local do if you use mdns?
Also, your router must be a bit confusing:
I use “butler” terms, like:
They serve me well, and I give them due respect.
If they’re using Linux, they should be fine. Most desktops don’t use a ton of RAM, and there are light desktops if that’s their issue.
If they’re running vanilla Minecraft with a handful of friends, just hosting the server should be fine. Mods are where things get ridiculous.
I went with mikrotik. It’s not too expensive, has way more features than I’ll ever need, and it’s rock solid. I used openwrt before that, which also did the job.
Honestly, that’s going to be pretty far down the road. Use what you’ve got, and fix issues as you go. Professional hardware is rarely needed, but it is pretty cool.