Can't start container with Catalina, Big Sur or Monterey

[Fortichoun]

Hello ! Thanks for this project

I've got an error when launching the container (I've tried with Catalina, Big Sur & Monterey), maybe can you help me ? I put here the stack trace of the error when I start Monterey and then the info gave by the template command

error: failed to initialize alpm library:
(root: /, dbpath: /var/lib/pacman/)
could not find or read directory
supermin: build: 0 files
supermin: build: 0 files, after matching excludefiles
supermin: build: 18 files, after adding hostfiles
supermin: build: 18 files, after removing unreadable files
supermin: build: 23 files, after munging
supermin: kernel: looking for kernel using environment variables ...
supermin: kernel: SUPERMIN_KERNEL=/boot/vmlinuz-linux
supermin: kernel: SUPERMIN_KERNEL_VERSION=5.12.14-arch1-1
supermin: kernel: SUPERMIN_MODULES=/lib/modules/5.12.14-arch1-1
supermin: kernel: picked vmlinuz /boot/vmlinuz-linux
supermin: kernel: kernel_version 5.12.14-arch1-1
supermin: kernel: modpath /lib/modules/5.12.14-arch1-1
supermin: ext2: creating empty ext2 filesystem '/var/tmp/.guestfs-1000/appliance.d.p1poj1l6/root'
supermin: ext2: populating from base image
supermin: ext2: copying files from host filesystem
supermin: ext2: copying kernel modules
supermin: *** parent directory not found ***
supermin: When reporting this error:
supermin: please include ALL the debugging information below
supermin: AND tell us what system you are running this on.
     src=/lib/modules
    dest=/lib/modules
 dirname=/usr/lib
basename=modules
supermin: ext2fs_namei: parent directory not found: /usr/lib: File not found by ext2_lookup
supermin: failure: ext2fs_namei: parent directory not found
libguestfs: error: /usr/bin/supermin exited with error status 1, see debug messages above
libguestfs: trace: launch = -1 (error)
libguestfs: trace: close
libguestfs: libguestfs: closing guestfs handle 0x56417d598180 (state 0)trace: 
closelibguestfs: 
command: run: rm
libguestfs: libguestfs: command: run: \ -rf /tmp/libguestfsjDhJvjclosing guestfs handle 0x562ccd7d7180 (state 0)

### cleaning up ...

And then the info gave by the template command :

Linux alexandre-Inspiron-7590 5.4.0-107-generic #121-Ubuntu SMP Thu Mar 24 16:04:27 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
:0
1
NAME="Ubuntu"
PRETTY_NAME="Ubuntu 20.04.3 LTS"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
Filesystem                 Size  Used Avail Use% Mounted on
/dev/mapper/vgubuntu-root  468G  106G  338G  24% /
QEMU emulator version 4.2.1 (Debian 1:4.2-3ubuntu6.21)
Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers
libvirtd (libvirt) 6.0.0
              total        used        free      shared  buff/cache   available
Mem:           15Gi       8,6Gi       4,1Gi       798Mi       2,6Gi       5,7Gi
Swap:         979Mi       934Mi        45Mi
12
12
crw-rw----+ 1 root kvm 10, 232 avril  4 10:30 /dev/kvm
total 104K
drwxrwxrwt  2 root      root      4,0K avril  4 10:31 .
drwxrwxrwt 39 root      root       96K avril  4 15:35 ..
srwxrwxrwx  1 alexandre alexandre    0 avril  4 10:31 X0
srwxrwxr-x  1 gdm       gdm          0 avril  4 10:31 X1024
srwxrwxr-x  1 gdm       gdm          0 avril  4 10:31 X1025
root        1300  1.0  0.3 2119796 54188 ?       Ssl  10:30   3:18 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
alexand+   54876  0.0  0.0   9044  2696 pts/3    S+   15:38   0:00 grep --color=auto dockerd
kvm:x:108:
docker:x:998:alexandre
libvirt:x:135:alexandre
libvirt-qemu:x:64055:libvirt-qemu
libvirt-dnsmasq:x:136:

Thanks for your help !

[Capy4U]

What command did u use?

[ZGuQing]

I had the same problem

[Fortichoun]

I did use the command gave in the README, Catalina for example :

docker run -it \
    --device /dev/kvm \
    -p 50922:10022 \
    -v /tmp/.X11-unix:/tmp/.X11-unix \
    -e "DISPLAY=${DISPLAY:-:0.0}" \
    sickcodes/docker-osx:latest

[kuba1128111]

try running first xhost + and then running the README command with sudo