Struggling setup

Hi.
I’m struggling at getting PB up and running on my Synology nas, some help would be great. I’ve read tons of docs, forums, tutorials, but there are some things I do wrong obviously.

My nas is running several web services through Docker, so this is not new for me, but not sufficient indeed.

  1. To run Docker commands I must be root on the nas. So I guess I should take the “passbolt/passbolt:4.9.1-1-ce” image, correct?
  2. My nas doesn’t have the GPG needed to create the keys. So I created them from my mac and put them on the volume specified in my compose file.
  3. Here is the compose script:
  passbolt:
    image: passbolt/passbolt:4.9.1-1-ce
    restart: unless-stopped
    tty: true
    depends_on:
      - postgres-15
    environment:
      APP_FULL_BASE_URL: https://blabla.bla
      DATASOURCES_DEFAULT_DRIVER: Cake\Database\Driver\Postgres
      DATASOURCES_DEFAULT_ENCODING: "utf8"
      DATASOURCES_DEFAULT_URL: "postgres://blablabla"
      EMAIL_TRANSPORT_DEFAULT_HOST: "smtp.blabla.com"
      EMAIL_TRANSPORT_DEFAULT_PORT: 465
      PASSBOLT_GPG_SERVER_KEY_PUBLIC: /etc/passbolt/gpg/public.key
      PASSBOLT_GPG_SERVER_KEY_PRIVATE: /etc/passbolt/gpg/private.key
    volumes:
      - gpg_volume:/etc/passbolt/gpg:rw
      - jwt_volume:/etc/passbolt/jwt:rw
    command: >
      bash -c "/usr/bin/wait-for.sh -t 0 192.168.33.33:4435 -- /docker-entrypoint.sh"
    ports:
      - 4500:8080
      - 4533:4433

At startup, the container crashes and show this:

gpg: can’t open ‘/etc/passbolt/gpg/public.key’: Permission denied
gpg: Total number processed: 0

The “gpg_volume” contains:

-r-------- 1 root root 6630 Oct 3 14:02 private.key
-r-------- 1 root root 3130 Oct 3 14:02 public.key

Thanks.

Checklist
I have read intro post: About the Installation Issues category
I have read the tutorials, help and searched for similar issues
I provide relevant information about my server (component names and versions, etc.)
I provide a copy of my logs and healthcheck
I describe the steps I have taken to trouble shoot the problem
I describe the steps on how to reproduce the issue

Well yes, the public key needs to have publicly readable permissions, so try chmod 644 /etc/passbolt/gpg/public.key