Calibre not launching over version 6.4 podman

Calibre does not launch at all if version is over 6.4 in podman.

If i try to access either the guacamole or calibre-web page, it shows an connexion refused page.
Calibre does launch on version 6.4 and lower.

Here is my launcher file :

podman run -d \
  --name=calibre \
  --security-opt seccomp=unconfined \
  --label io.containers.autoupdate=registry \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=America/NewYork \
  -p 8080:8080 \
  -p 8081:8081 \
  -v /root/calibre2/config:/config \

permissions for theses files are set as user:group 1000:1000

Logs shows :

[custom-init] No custom services found, skipping...
[migrations] started
[migrations] no migrations found

          _         ()
         | |  ___   _    __
         | | / __| | |  /  \
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/

Brought to you by

To support LSIO projects visit:

User uid:    1000
User gid:    1000

Generating 2048 bit rsa key...

ssl_gen_key_xrdp1 ok

saving to rsakeys.ini

// Key is not shown for security reason

**** No auth enabled. To enable auth, you can set the PASSWORD var in docker arguments. ****
[custom-init] No custom files found, skipping...

i am running this setup on :

PRETTY_NAME="Ubuntu 22.10"
VERSION="22.10 (Kinetic Kudu)"

using podman :
podman/kinetic,now 3.4.4+ds1-1ubuntu1 amd64 [installed]

Thanks in advance everybody

Are you able to reproduce the issue using docker? We do not support or test on podman. I can tell you that rootless will almost definitely not work

Im running it as root and i didn’t tried it on docker.
I use most of your images and its the only one causing issue.

I was able to make it work on docker.
Personally I would like to be able to get it on podman and I have a mention for docker without the seccomp : there is not much informations in logs , it just looks like the app is frozen. Is it possible to log more informations about that ?

Open an issue with Podman. Could be SELinux blocking access to the directory but we would need to see the podman info output.

Also try with --privileged to see if some security mechansim that Docker allows we are blocking.