sigmoid.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A social space for people researching, working with, or just interested in AI!

Server stats:

599
active users

#microos

1 post1 participant0 posts today

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.

Replied in thread

@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.

Replied in thread

@jschreuder @eu_os

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.

Playing with a transactional OS (#MicroOS) does bring some learning.

Also, it's been... Ugh, two decades or more since I last touched anything #suse.

Sofar I'm liking it.