Issues upgrading to V3 in docker

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

We currently have Passbolt running in docker user the 2.13.5-debian image. I am trying to upgrade to V3. When I do that, we get an popup when trying to login saying the server key has changed. For some users, accepting this change allows them to login. This is mildly frustrating because any time we do a docker-compose down and then back up, the server key changes again. However, for some users accepting the key and then entering their password results in this error:

image

I am not sure what is causing this. Here is a sample of my docker-compose file:

version: '3.4'
services:
  passboltdb:
    image: mariadb:10.3
    container_name: passboltdb
    restart: always
    hostname: passboltdb
    env_file:
      - ./mysql.env
    volumes:
      - ./mysql:/var/lib/mysql
    ports:
      - 3306

  passbolt:
    image: passbolt/passbolt:3.2.0-ce
    container_name: passbolt
    hostname: passbolt
    restart: always
    tty: true
    depends_on:
      - passboltdb
    env_file:
      - ./passbolt.env
    volumes:
      - ./gpg:/etc/passbolt/config/gpg
      - ./public:/usr/share/php/passbolt/webroot/img/public
      - ./bind_mount_files/app.php:/etc/passbolt/app.php
        
networks:
  default:
    external:
      name: nginx-proxy

Can anyone help me with this? In the past upgrading versions was as simple as changing the image name. With version 3, i see all the migrations take place, and i have moved files to the new locations, but it is still being stubborn.

Hi @acook44 double check path to gpg folder. The official docker-compose.yml is showing /etc/passbolt/gpg.