Comment # 8
on bug 1217306
from Dario Faggioli
So, I just installed a Tumbleweed VM, and it seems to work there:
> dario@localhost:~> distrobox enter test
> Error: no such container test
> Creating the container test
> Trying to pull registry.opensuse.org/opensuse/distrobox:latest...
> Getting image source signatures
> Copying blob 3f501f5dfd08 done |
> Copying blob 2c46e69ca941 done |
> Copying config 98f2e40d0f done |
> Writing manifest to image destination
> 98f2e40d0f804ddcf8a55d3e8e8905f46bf6c439ead61ac0ed17b4ca02e8cd0f
> Creating 'test' using image registry.opensuse.org/opensuse/distrobox:latest [ OK ]
> Distrobox 'test' successfully created.
> To enter, run:
>
> distrobox enter test
>
> 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 groups... [ OK ]
> Setting up users... [ OK ]
> Setting up skel... [ OK ]
>
> Container Setup Complete!
> dario@test:~>
Version of distrobox in Tumbleweed is the latest:
> dario@localhost:~> distrobox --version
> distrobox: 1.6.0.1
In /usr/share/containers/containers.conf I have
> # Logging driver for the container. Available options: k8s-file and journald.
> #
> log_driver = "journald"
So, this seems to be either an old distrobox issue or an (old?) podman issue.
I'm not sure when I'll be able to spend time debugging distrobox 1.4 or 1.5 on
Leap. In fact, if we're still in time (are we, Lubos?), we probably should push
1.6.0.1 to, at least, Leap 15.6.
If it's podman, then I don't really know... :-(