Comment # 3 on bug 1208289 from Luciano Santos

Something's not right. If one's on a Tumbleweed system and run:

$ distrobox create paperino
$ distrobox enter paperino

Distrobox should use a Tumbleweed image as seen here:

> $ distrobox create paperino
> Trying to pull registry.opensuse.org/opensuse/tumbleweed:latest...
> Getting image source signatures
> Copying blob 2fd8976f5ca6 done
> Copying config 83c212e5d7 done
> Writing manifest to image destination
> Storing signatures
> 83c212e5d7bb78937e6a1ce138411f29e9662924f095b78f8e1126fb6717c03b
> Creating 'paperino' using image registry.opensuse.org/opensuse/tumbleweed:latest          [ OK ]
> Distrobox 'paperino' successfully created.
> To enter, run:
> 
> distrobox enter paperino

And not Leap, since Tumbleweed doesn't have util-linux-systemd anymore.

Here on my Tumbleweed system `distrobox create paperino` basically worked. It
stumbled upon something else, though:

> (201/202) Installing: libgtk-4-1-4.8.3-1.2.x86_64 [......done]
> (202/202) Installing: libvte-2_91-0-0.70.2-2.1.x86_64 [..done]
> Executing %posttrans script 'login_defs-4.13-3.1.noarch.rpm' [...
> Created symlink /etc/systemd/system/default.target.wants/ca-certificates.path ->  /usr/lib/systemd/system/ca-certificates.path.
> Created symlink /etc/systemd/system/timers.target.wants/fstrim.timer -> /usr/lib/systemd/system/fstrim.timer.
> Created symlink /etc/systemd/system/multi-user.target.wants/remote-fs.target -> /usr/lib/systemd/system/remote-fs.target.
> Created symlink /etc/systemd/system/multi-user.target.wants/kbdsettings.service -> /usr/lib/systemd/system/kbdsettings.service.                                                                                                                     
> Created symlink /etc/systemd/system/getty.target.wants/getty@tty1.service -> /usr/lib/systemd/system/getty@.service.
> Created symlink /etc/systemd/user/basic.target.wants/systemd-tmpfiles-setup.service -> /usr/lib/systemd/user/systemd-tmpfiles-setup.service.
> Created symlink /etc/systemd/user/timers.target.wants/systemd-tmpfiles-clean.timer -> /usr/lib/systemd/user/systemd-tmpfiles-clean.timer.                                                                                                           
> ....done]
> + '[' 107 -ne 0 ']'
> Error: An error occurred
> + printf 'Error: An error occurred\n'

Zypper returned the 107 code, which means the installation succeeded but some
post scriptlet failed. That's something that could be improved in Distrobox's
handling of openSUSE containers, though.