Leap Micro 6.2: Documentation?

English Virtualization
1

My first install of the Leap Micro 6.2 on a barebone MSI Z390-A PRO motherboard, that was previously used as a Desktop, but now using it a my home KVM server.

Being I’m not familiar with this version of openSUSE, I’m having trouble locating documentation to learn how to administer the OS.

I see Yast2 is not available, and I need Midnight Commander (my preferred file system explorer), and other admin tools. When I search for mc I only get these results:

nasheayahu@micro-studio:/> zypper search mc
Loading repository data...
Reading installed packages...

S  | Name    | Summary                             | Type
---+---------+-------------------------------------+--------
   | mcelog  | Log Machine Check Events            | package
i  | permctl | SUSE Linux Default Permissions tool | package

    Note: For an extended search including not yet activated remote resources please use 'zypper
    search-packages'.
nasheayahu@micro-studio:/> zypper search-packages mc
Could not search for the package: Error: Registration server returned 'base product not found' (404)Following packages were found in following modules:

Package Module or Repository                 SUSEConnect Activation Command 
------- ------------------------------------  
permctl Installed                             
mcelog  Available in repo openSUSE:repo-main  
permctl Available in repo openSUSE:repo-main  

To activate the respective module or product, use SUSEConnect --product.
Use SUSEConnect --help for more details.

Can anyone link me to Leap Micro or equivalent guide?

2

https://en.opensuse.org/Portal:Leap_Micro

1 Like
3

Hi,

It is helpful to use “MicroOS” Documentation, not Leap or Tumbleweed.

Specifically you use transactional-update instead zypper directly to do updates, as your system is immutable and needs to go through some extra hoops to do manually fired off updates.

1 Like
4

@nasheayahu Hi, aside from @hui’s info, look at installing the flatpak version of Cockpit (org.cockpit_project.CockpitClient) on a local machine and use that to connect to the MicroOS system for system management and also Virtual Machine creation/management. It also includes a file browser :wink:

Likewise I use org.virt_manager.virt-viewer to connect to Virtual Machines…

1 Like
5

the leap micro repositories are incredibly small, by design, that something like mc which is ostensibly a user application, doesn’t surprise me in the least.

You’re supposed to install stuff like that in a toolbox, not into the base system.

6

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.