https://bugzilla.suse.com/show_bug.cgi?id=1199871 https://bugzilla.suse.com/show_bug.cgi?id=1199871#c7 --- Comment #7 from Marcos de Souza <mpdesouza@suse.com> --- (In reply to Alexandre Vicenzi from comment #6)

(In reply to Marcos de Souza from comment #5)

...

Also I couldn't find this group on SLE15-SP5... am I missing something? Nowadays that SLE and openSUSE share the same codebase, I expect this behavior to be also present on Leap 15.5, right?

I believe the solution to your case is to change the log driver, you can set log_driver and events_logger as suggested in the previous comment.

This bug is mentioned in https://distrobox.it/compatibility/#host-distros.

Indeed, if I create a file in my hope directory like stated in comment 1:

[containers] log_driver = "k8s-file" [engine] events_logger = "file"

in ~/.config/containers/containers.conf, and recreating the container, fixes the issue.

It worked with minimal warnings: mpdesouza@dogmatix:~> distrobox create --name mpdesouza-lp --image registry.opensuse.org/opensuse/distrobox-packaging: latest Creating 'mpdesouza-lp' using image registry.opensuse.org/opensuse/distrobox-packaging:latest Resource limits are no t supported and ignored on cgroups V1 rootless systems [ OK ] Distrobox 'mpdesouza-lp' successfully created. To enter, run: distrobox enter mpdesouza-lp mpdesouza@dogmatix:~> distrobox enter mpdesouza-lp WARN[0000] Failed to mount subscriptions, skipping entry in /etc/containers/mounts.conf: open /etc/zypp/credentials.d/ SCCcredentials: permission denied Starting container... [ OK ] Installing basic packages... [ OK ] Setting up devpts mounts... [ OK ] Setting up read-only mounts... [ OK ] Setting up read-write mounts... [ OK ] Setting up host's sockets integration... [ OK ] Integrating host's themes, icons, fonts... [ OK ] Setting up package manager exceptions... [ OK ] Setting up rpm exceptions... [ OK ] Setting up distrobox profile... [ OK ] Setting up sudo... [ OK ] Setting up user groups... [ OK ] Setting up kerberos integration... [ OK ] Setting up user's group list... [ OK ] Setting up existing user... [ OK ] Setting up user home... [ OK ] Ensuring user's access... [ OK ] Container Setup Complete! It worked fine for me. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.