Installing the `patterns-microos-cockpit` package (and thereby the
microos_cockpit pattern) doesn't install cockpit itself as can be seen below:
> microos:~ # transactional-update pkg install patterns-microos-cockpit && reboot
> ...
> microos:~ # zypper se cockpit
> Loading repository data...
> Reading installed packages...
>
> S | Name | Summary | Type
> ---+--------------------------+------------------------------------------------------------------------------+--------
> | cockpit | Web Console for Linux servers | package
> | cockpit-agama | Cockpit module for Agama | package
> i | cockpit-bridge | Cockpit bridge server-side component | package
> | cockpit-devel | Development files for for Cockpit | package
> | cockpit-doc | Cockpit deployment and developer guide | package
> | cockpit-kdump | Cockpit user interface for kernel crash dumping | package
> | cockpit-machines | Cockpit user interface for virtual machines | package
> | cockpit-networkmanager | Cockpit user interface for networking, using NetworkManager | package
> | cockpit-packagekit | Cockpit user interface for packages | package
> | cockpit-pcp | Cockpit PCP integration | package
> i | cockpit-podman | Cockpit component for Podman containers | package
> | cockpit-selinux | Cockpit SELinux package | package
> | cockpit-storaged | Cockpit user interface for storage, using udisks | package
> i | cockpit-system | Cockpit admin interface package for configuring and troubleshooting a system | package
> | cockpit-tukit | Cockpit module for Transactional Update | package
> | cockpit-ws | Cockpit Web Service | package
> i | microos_cockpit | Web based remote system managemet | pattern
> i+ | patterns-microos-cockpit | Web based remote system managemet | package
I would assume that installing this package on MicroOS results in a workable
cockpit installation. This is on MicroOS, it could be that some packages are
only recommended but not required and therefore not installed there.