I've been running openSUSE MicroOS as a container host on a Raspberry Pi 4 for about a week now, without any trouble.
Transactional Updates (snapshots) has been working flawlessly, nothing unusual in the logs, CPU and memory usage looks similar to other OS's on the same hardware.
Anything else I should consider before moving this server out of testing?
Ive built a setup for hosting websites which consists of:
* Host running #microos with #podman
* #Treafik and #sshpiper at the edge
* #Nginx, php-fpm, #mariadb + phpmyadmin + nginx or #postgres + dbadmin, openssh for each site
It actually works quite well, openssh keybased access is to transfer files into the containers, traefik does the reverse proxying.
I'm just wondering if its a sustainable and maintainable setup. Sometimes just going with a "standard" solution seems so much easier.
@paulk #Leap or #Tumbleweed – or something fancier like #MicroOS? I’m a long-time fan of #openSUSE myself, and particularly of stable Leap.
From last week's Linux Update newsletter: Koen Vervloesem shows you how to manage containers with MicroOS, Cockpit, and Podman
https://www.linux-magazine.com/Issues/2025/291/Container-Management?utm_source=SM
#containers #openSUSE #MicroOS #Cockpit #Podman #Docker
@maxxieb (1/2)
I had to refrain from calling "Bingo", because I had anticipated that question. But it is an obvious question that deserves an answer. I also had to stop myself from quoting Shakespeare ("There more things ...").
In my case it boils down to this:
1. I have been experimenting with using #NixOS on my laptop, where I do all of my (private) things. I also have home-manager on my work laptop.
I can almost do all of the things I can on my #openSUSE #Tumbleweed laptop. This includes packaging for openSUSE.
But I have not converted all of my 3 dozen different VMs, servers, raspis, NUCs and whatnot to NixOS. They will keep running a mixture of immutable (openSUSE #MicroOS, #Fedora #CoreOS, NixOS, ...) and non-immutable things (Debian, Proxmox, ...). And I would like to be able to manage them from whatever host I am currently working from. Hence I would like to have a working Ansible environment on my NixOS laptop to manage other machines with.
Odd. On #SuSE #MicroOS my #podman #containers suddenly aren't able to reach the internet anymore.
When checking the routes with `podman unshare --rootless-netns ip r s` i'm also missing everything except the local podman network.
With Github's UI/UX feeling increasingly annoying over time, I am taking a look at self hosting again to pair with https://codeberg.org/anuragsoni as an externally hosted git forge! Compared to last time I hosted a server, I'm doing things a little differently this time (I promise I will not write yet another static website generator!!)
* Picked Hetzner instead of Linode. No particular issues with Linode but Hetzner's pricing was more attractive and they offer ampere based arm64 servers
* Picked fedora as my server! Ideally I'd run #microos but that isn't available on Hetzner-cloud. Fedora gets me the latest podman!
* Provisioned a non-admin user dedicated to all my Podman use
* Running caddy as a rootless Podman container (among other services) paired with systemd!
This is my first time looking at #systemd and so far I'm really liking it!!
Re rootless podman, the only "gotcha" I ran into was having to allow non-admin users to access privileged ports >= 80 as those are typically blocked for rootless applications.
Maybe this will give be a nice excuse to also document everything I did to configure this whole thing and add some stuff to my website!!
Next step will be to setup https://forgejo.org to run in another rootless container and sit behind caddy!
To my knowledge #opensuse is not yet available as images with rpm-ostree layer. Though I think this development and #bootc are big advantage for organisations who already work with containers. It is also an advantage for organisations that would require more than one image for different ministries/departments/user groups.
I have followed the development on #MicroOS and @kalpa . It was still beta last time I checked. It works differently.
Ostres ara flipo, la gent de @opensuse@fosstodon.org tenen una eina online per configurar un arxiu Ignition per fer la instal·lació de #MicroOs a un servidor headless... #NoPasMalament @fedora@fosstodon.org no trobo cap eina per fer el mateix amb CentOS... 
@jolupa Iepa! Doncs depèn de si busques rolling release o Standard Release
#Tumbleweed es Rolling y #Leap es Standard release. Qualsevol de les dues en el moment de la instal·lació et preguntarà quin tipus d'instal·lació vols.
Jo utilitzo #MicroOS que és #Tumbleweed però immutable.
Ja está el nou servidor a ple rendiment amb tots els serveis en marxa sobre #openSuse amb #MicroOS i els serveis corrent amb #Portainer sobre #Podman
#opensuse #kalpa für meinen Vater ist eine sehr feine Installation geworden. Bin gespannt, wie es sich bewährt. Glaube wird gut.
Werde in der Zwischenzeit gleiche Konfiguration für meine Tante vornehmen.
Mir gefällt vor allem, wie schlank das System ist. Im Grunde nur #firefox und noch ein paar "Hilfsprogramme" (Konsole, KDE-Einstellungen, usw.)
Sowas in #hyprland wäre gail!
Sembla que #openSUSE #Tumbleweed és una de les primeres distribucions #Linux a adoptar el nucli 6.13 
Jo també la tinc a #MicroOS @opensuse #LinuxKernel #OpenSourcehttps://floss.social/@9to5linux/113903033430721093
[^BgTA^] :verified: :opensuse:...
I won't get to a post tomorrow, but for tonight I have a post explaining how I set up Caddy as a web proxy for the other services,
Another post about my home server. This time I explain how I've set up an internal DNS service.
**Update:** It was pointed out that the list of private TLDs was incorrect, and I have corrected them.
I wrote a post about my home server I set up. There will be further posts about each service I have running, and how I run them.
