Try Cockpit in Leap Release Candidate

29. Apr 2024 | Lubos Kocman and Douglas DeMaio | CC-BY-SA-3.0

Try Cockpit in Leap Release Candidate

openSUSE Leap 15.6 exited Beta and entered its Release Candidate phase with build 669.1 last week. You can get Leap 15.6 RC install images from

This means the release is considered featurefull and contributors should focus on bug fixes and eliminating any remaining build failures.

Users who are eager to install Leap 15.6 on their machines should check the release’s known issues to see if there is any issue that prevents the use of the RC.

The release team was able to deliver a long time awaited Cockpit for both Leap and SUSE Package Hub users. Users might be familiar with Cockpit’s web-based admin interface from Leap Micro tutorials.

Users are advised not to publicly expose Port 9090 used with the admin interface; just like people shouldn’t expose their router’s web interface to the public.

`$ sudo zypper in cockpit`

`$ sudo systemctl enable --now cockpit.socket`

`$ firefox https://localhost:9090 # root login is disabled by default check note bellow`

Previous attempts to include Cockpit in Leap 15.5 were made, but there were several blockers. Inclusion was possible thanks to a refresh of the python311 stack, which was part of massive update effort for SUSE Linux Enterprise Server 15 Service Pack 6 along with unification branding. The team was able to build Cockpit once and provide it for both SLES and Leap users with this RC.

Root login into cockpit is disabled by default Similarly to password-based root login via ssh, root login into cockpit is disabled by default in openSUSE Leap. This isn’t the case for Leap Micro where we expect single user boxes.

If you prefer root login, over privileged user account access, then simply edit and remove root from disallowed-users and a restart of service.

$ sudo vim /etc/cockpit/disallowed-users

$ sudo systemctl restart cockpit.socket

There is no existing SELinux policy on Leap 15.X so the SELinux part of Cockpit is not expected to be working. The release team expects to have an SELinux policy in Leap 16, so this will be working for future releases.

Happy Hacking!

Share this post: