Cinny docker on ARM creates no cinny.conf file

[PixelcrafterEXE]

Describe the bug

I'm running Cinny on a RPi 5 (ARM) and the same compose file works on my x86 Desktop. When I start the container on the Pi there is no Webinterface.

After some investigation I found that the cinny.conf file (which i didn't via-mount) doesnt get created and nginx therefor doesnt get set up to respond to requests. I'm not sure why this happens or if this is for sure an ARM issue but when via-mounting the config file that was previously created on another machine the container works

Reproduction

1. Install Docker on a Rpi5
2. Run this Compose file

  cinny:
    image: ghcr.io/cinnyapp/cinny
    container_name: cinny
    ports:
      - 8083:80

3. Run docker exec cinny cat /etc/nginx/conf.d/default.conf (returns empty in my case)

Expected behavior

❯ docker exec cinny cat /etc/nginx/conf.d/default.conf
server {
  listen 80;
  listen [::]:80;

  location / {
    root /usr/share/nginx/html;

    rewrite ^/config.json$ /config.json break;
    rewrite ^/manifest.json$ /manifest.json break;

    rewrite ^/sw.js$ /sw.js break;
    rewrite ^/pdf.worker.min.js$ /pdf.worker.min.js break;

    rewrite ^/public/(.*)$ /public/$1 break;
    rewrite ^/assets/(.*)$ /assets/$1 break;

    rewrite ^(.+)$ /index.html break;
  }
}

Platform and versions

ARM on Respian (Debian), RPi5, Latest Cinny, no Matrix connected (yet)

Additional context

No response

Edit: Its not just the default.conf file that is empty but most files in nginx.