On 2/19/21 11:10 AM, Ladislav Slezak wrote: > The only workaround would be to use the Leap 15.3 as the base distro for CI. > So far there should not big differences so that should work fine, at least > for some > time. We could use it until the issue is resolved, later we can switch back > to TW.
We can also go back to "self-baked solution" @home, but that's IMO a step back. This problem will not last forever. But it will most probably happen again one day. Similarly, Flatpak on my 15.2 reported to be too old for official Chromium. > BTW the same problem also happens in other distros and in other systems (even > WSL has > been reported). This clearly shows the disadvantage of containers. Even if we > bundle > our complete openSUSE user space stack (down to glibc) we still rely on the > host > kernel (Ubuntu in this case) and this might cause some incompatibilities... > :-/ While I'm not a "containers everywhere" guy, this is IMO an exception and advantages of using containers (for our use-case) are still much bigger than disadvantages. Anyway, we've just finished SUSE Workshop where Containers were an important topic. I believe that this issue deserves being recorded there... Anyone who could summarize the problem there, please? Thx Lukas -- Lukas Ocilka, Systems Mgmt & Consulting Team Leader & YaST Product Owner SLE Department, SUSE Linux
