Docker Deployment - http2 frame too large ?

[JoshuaNCSU]

I am very new to looking at this project, but it looks very interesting. I am attempting to deploy a clean install of Worklenz in a Portainer (docker compose) environment. When I use your existing docker-compose.yml file, I am getting a couple of errors that I seem to be unable to work around. Normally with deploying stacks with Portainer, you run into a few issues just with environmental differences, but this seems to be something with the stack being able to get downloaded and built. I was wondering if you had any insights?

Failed to deploy a stack: frontend Pulling backend Pulling frontend Warning Head "https://ghcr.io/v2/worklenz/worklenz-frontend/manifests/latest": denied backend Warning Head "https://ghcr.io/v2/worklenz/worklenz-backend/manifests/latest": denied listing workers for Build: failed to list workers: Unavailable: connection error: desc = "error reading server preface: http2: frame too large"

I have slightly altered your docker-compose.yml file to omit the 'Networks' part, as they don't play nice with Portainer, but this is something I have encountered before and know how to resolve or if this something that you've seen before.

Portainer stack (docker-compose.yml)
`services:
frontend:
image: ghcr.io/worklenz/worklenz-frontend
build:
context: ./worklenz-frontend
dockerfile: Dockerfile
container_name: worklenz_frontend
ports:
- "4200:4200"
depends_on:
backend:
condition: service_started

backend:
image: ghcr.io/worklenz/worklenz-backend
build:
context: ./worklenz-backend
dockerfile: Dockerfile
container_name: worklenz_backend
ports:
- "3000:3000"
depends_on:
db:
condition: service_healthy
environment:
- ANGULAR_DIST_DIR
- ANGULAR_SRC_DIR
- AWS_REGION
- BACKEND_PUBLIC_DIR
- BACKEND_VIEWS_DIR
- COMMIT_BUILD_IMMEDIATELY
- COOKIE_SECRET
- DB_HOST
- DB_MAX_CLIENTS
- DB_NAME
- DB_PASSWORD
- DB_PORT
- DB_USER
- GOOGLE_CALLBACK_URL
- GOOGLE_CLIENT_ID
- GOOGLE_CLIENT_SECRET
- HOSTNAME
- LOGIN_FAILURE_REDIRECT
- NODE_ENV
- PORT
- SESSION_NAME
- SESSION_SECRET
- SLACK_WEBHOOK
- SOCKET_IO_CORS
- SOURCE_EMAIL
- USE_PG_NATIVE
- BUCKET
- REGION
- S3_URL
- S3_ACCESS_KEY_ID
- S3_SECRET_ACCESS_KEY

db:
image: postgres:15
container_name: worklenz_db
environment:
POSTGRES_DB: "${DB_NAME}"
POSTGRES_PASSWORD: "${DB_PASSWORD}"
healthcheck:
test: ["CMD-SHELL", "pg_isready -d ${DB_NAME} -U ${DB_USER}"]
interval: 10s
timeout: 5s
retries: 5
volumes:
- /docker/worklenz/worklenz_postgres_data:/var/lib/postgresql/data # Slightly altered environmental path
- /docker/worklenz/worklenz-backend/database/:/docker-entrypoint-initdb.d # Slightly altered environmental path

volumes:
worklenz_postgres_data:`

[JoshuaNCSU]

Here is the actual error that I am getting when I attempt to deploy the stack:

Failed to deploy a stack: backend
Pulling frontend
Pulling backend
Warning Head "https://ghcr.io/v2/worklenz/worklenz-backend/manifests/latest": denied frontend
Warning Head "https://ghcr.io/v2/worklenz/worklenz-frontend/manifests/latest": denied listing workers for Build: failed to list workers: Unavailable: connection error: desc = "error reading server preface: http2: frame too large"