I am testing out MicroOS and the possible usage for a Development laptop. The thought of a read-only filesystem to prevent anyone from doing anything really stupid and the way apps are installed and run is promising. I am also l looking at SLE Micro to run Rancher and K8s environment. My question is what is the best way to join MicroOS to an AD domain for user authentication?
When I run a realm list I see it appears joined and I see the computer object in AD via Users and Computers; however, when I run ‘id <ad_user>’ nothing is returned and I cannot login with my AD creds so I am missing something. Or is MicroOS meant to be an individual desktop environment with only local users?
Hi
I don’t run/use AD I would suggest running toolbox then install the packages there and play around, or use transactional-update shell then when exiting it will save your updates on the reboot…
My rancher instance is running vagrant/Leap 15.3, I use vagrant/ignition/MicroOS for k8s, you might want to join the SUSE & Rancher community at Community | Rancher which has a lot more information and free classes etc
Thanks malcolmlewis! That definitely looks like some useful information.
I guess what I am trying to accomplish is determine if MicroOS would be suitable, once configured, to provide our Developers a Linux notebook environment. We are looking at Ubuntu, Pop!_OS, etc as well but already having SLE running on servers and managed with SUMA I was thinking MicroOS would be a good fit as well even though the Gnome interface is Alpha it does appear this is the way going forward for openSUSE. Really nice idea I just need to figure out how to join to AD so users can leverage their AD creds to login and security is happy when no local users exists on the laptop.
So we have a Mailing List, IRC and Matrix/Discord channels, I would suggest #opensuse-microos-desktop on Matrix, else pop over to the SUSE & Rancher community.
I would suggest running toolbox then install the packages there and play around, or use 