Jack Wallen kicks the tires on openSUSE Micro, a modern container-specific OS, and shares his thoughts (both good and bad) with you.
openSUSE Micro is a new Linux distribution aimed at hosting containerized workloads with automated management and patching. With this open-source purpose-built operating system, you get an environment specifically designed for workloads that benefit from transactional updates. This rolling release distribution is exactly what your company needs.
openSUSE Micro aims to be predictable, scalable, reliable and flexible. This new way of thinking about containerized deployment uses standard openSUSE RPMs, has no size limit, and is easy and repeatable to roll out, so you don’t have to learn a new packaging format.
I installed openSUSE Micro to see what’s what. My impressions were mixed, which is to be expected given that the platform is fairly new. Let’s dive in.
See: 40+ Open Source and Linux Terms You Should Know (TechRepublic Premium)
System role
One of the first deviations from normal openSUSE is system roles. During installation, you can choose which role the OS will play. However, at first glance, these roles are a bit confusing.
- micro OS: Designed for single-purpose systems and optimized for large-scale deployments. By default it does not provide any services. This will install the OS without a desktop environment.
- MicroOS container host: Optimized for containers and installs Podman. It also installs without a desktop environment, but with everything needed to deploy containers.
- MicroOS Desktop (GNOME): Same as MicroOS Container Host, but only includes desktop environment, automatic updates, and rollbacks. This system role is in beta.
- MicroOS Desktop (KDE): Same as MicroOS Container Host, but only includes desktop environment, automatic updates, and rollbacks. This system role is in alpha.
- MicroOS with remote authentication (agent): Same as MicroOS, but with a remote authentication agent. Remote authentication is how a host authenticates its hardware and software configuration to a remote server. This will install the agent part.
- MicroOS with Remote Verifier: Same as MicroOS, but with remote authentication verification. Remote authentication is how a host authenticates its hardware and software configuration to a remote server. This will install the verifier part.
I decided to install the MicroOS Desktop (GNOME) system role just to see how it worked. The install wasn’t perfect in that I had to keep pressing retry because some packages failed to install on the first try.
I just completed a fully functional installation with the vanilla GNOME desktop environment. I installed openSUSE Micro as a VirtualBox VM, so I wasn’t able to successfully install the Guest Additions or run the VM with a different graphics controller. So my desktop resolution was pretty small. For this reason, if you’re planning to go virtual root, your best bet is to install without a desktop environment.
Another issue I initially discovered was that the filesystem was mounted as read-only, so there was no option to install software. But the good news is that using the Podman container runtime library works as expected.
Please let me explain. The read-only file system is intentionally done for security purposes. It is important to remember that openSUSE Micro is not intended to be used as a standard operating system, but for similar containerized deployments. So there is no need to mount the file system in read/write mode. In fact, you don’t want the file system mounted in any way other than read-only. So with openSUSE Micro as the platform for your containers, you’ll feel instantly at ease.
But there are pitfalls. He prefers to manage containers via the GUI, but he’s the go-to manager Portainer doesn’t support his Podman yet. Also, Cockpit could not be installed because the system boots in read-only mode. There is a way around it.
After starting openSUSE Micro, edit fstab with the following command:
vi /etc/fstab
Find the line that ends with . ro change it to rwOnce that is done, save the file, reboot your machine and install Cockpit with Podman support using the following command:
sudo zypper install cockpit cockpit-podman
It should have worked. However, similar to what I experienced during the OS installation, the installation of the Cockpit Bridge package failed, but no reason was given. No matter how I tried to install it, it didn’t work.
This is fine because you can interact with Podman from the command line. Besides, I don’t want to install anything extra on a platform intended for scalable container deployment. This should be as minimal as possible. My sole purpose was to see what I could do with openSUSE Micro. So I decided to test a simple deployment instead of relying on the GUI. I’m not going to lie. Podman is not as user friendly as Docker. For example, you can easily deploy a WordPress site using Docker. With Podman, not so much.
Nevertheless, I decided to do a simple NGINX deployment with Podman using the following command.
podman pull docker.io/nginx
podman run -d --name docker-nginx -p 8080:80 docker.io/nginx
The rollout went smoothly, but it’s very basic. To take this one step further, he deployed Joomla with Podman using the following command:
podman pod create --name mypod --publish 8080:80
podman run -dit --pod mypod -e MYSQL_DATABASE=joomla -e MYSQL_USER=joomlauser -e MYSQL_PASSWORD=joomlapassword -e MYSQL_ROOT_PASSWORD=rootpw --name mariadb docker.io/library/mariadb
podman run -dit --pod mypod -e JOOMLA_DB_HOST=127.0.0.1 -e JOOMLA_DB_USER=joomlauser -e JOOMLA_DB_PASSWORD=joomlapassword -e JOOMLA_DB_NAME=joomla --name joomla docker.io/library/joomla
Joomla was GUI install ready and running like a champ. I was amazed at how responsive the Joomla deployment was. This is a testament to how well openSUSE Micro performs even with a desktop installed.
My conclusion about openSUSE Micro
openSUSE Micro is a great option for deploying a purpose-built OS for containerized applications. Small, very fast and secure.
Download the openSUSE Micro ISO and give it a try. openSUSE Micro could be your go-to platform for deploying containers.
Become a Linux expert with these TechRepublic Academy resources
Subscribe to TechRepublic’s How To Make Tech Work on YouTube to get all the latest tech advice for business professionals from Jack Wallen.
