On 6/13/22 18:45, Jan Engelhardt wrote:

On Monday 2022-06-13 18:16, Ancor Gonzalez Sosa wrote:

# zypper in yast [...]

26 new packages to install. Overall download size: 11.5 MiB. Already cached: 0 B. After the operation, additional 27.6 MiB will be used.

# zypper in podman [...]

9 new packages to install. Overall download size: 25.0 MiB. Already cached: 0 B. After the operation, additional 113.9 MiB will be used.

So instead of having to install yast2 (zypper tells me 11 MB), I now have to podman (25 MB).

The outcome of those two commands heavily depend on the system you execute them. What you show is the result in a traditional openSUSE in which the software is delivered as packages directly installed in the system (the paradigm I personally use and love). But that's not the only reality we find out there nowadays. You and me, who still enjoy the traditional model of Linux distributions, will still install YaST directly in the system. That's perfectly fine and will always be possible, of course. But the new containerized YaST broadens the usefulness of YaST to also cover other scenarios in which installing RPM packages is only done as a last resort and containers are the preferred way to distribute and consume software.

...

those new commands grab YaST and run it in a container that will be transparently used to administer the host system.

It's logically backwards that one is supposed to run Y2 in a container, only to have it go outside again. Containers are not supposed to affect the host system.

Actually privileged containers can affect the host system. And they have existed for years. Isolating the base system from the software running inside the containers is only one of the possible goals of containers. In some environments, containers are the main mechanism to distribute and execute software since they represent a way to bundle several software pieces (traditionally RPM packages) in a self-contained format. Now YaST is an option also in those environments. Although I expect YaST to be used seldom there - basically to cover situations in which other tools fall short in functionality or to ease transition for administrators of traditional (open)SUSE distributions. Cheers. -- Ancor González Sosa YaST Team at SUSE Software Solutions