Deploying in an isolated environment not possible

[petter]

Describe the Bug

When trying to deploy the newest version of Umami in a cluster that does not have internet access it fails to start. It fails on Prisma trying to fetch binaries on start up. Would it be possible to bundle these binaries as part of the image instead?

Here's a docker-compose file that reproduces the issue:

services:
  postgres:
    image: postgres
    container_name: postgres
    networks: 
      - isolated_net
    environment:
      POSTGRES_PASSWORD: 123
    volumes:
      - pgdata:/var/lib/postgresql/data

  umami:
    image: ghcr.io/umami-software/umami:postgresql-v2.18.1
    container_name: umami
    networks: 
      - isolated_net
    depends_on:
      - postgres
    ports:
      - "3000:3000"
    environment:
      DATABASE_URL: postgresql://postgres:123@postgres:5432/postgres
      PRISMA_ENGINES_CHECKSUM_IGNORE_MISSING: 1

networks:
  isolated_net:
    driver: bridge
    internal: true

volumes:
  pgdata:

Database

PostgreSQL

Relevant log output

> [email protected] start-docker /app

> npm-run-all check-db update-tracker set-routes-manifest start-server



> [email protected] check-db /app

> node scripts/check-db.js


✓ DATABASE_URL is defined.

✓ Database connection successful.

✓ Database version check successful.

Error: request to [https://binaries.prisma.sh/all_commits/3cff47a7f5d65c3ea74883f1d736e41d68ce91ed/linux-musl-arm64-openssl-3.0.x/libquery_engine.so.node.gz⁠](https://binaries.prisma.sh/all_commits/3cff47a7f5d65c3ea74883f1d736e41d68ce91ed/linux-musl-arm64-openssl-3.0.x/libquery_engine.so.node.gz) failed, reason: getaddrinfo EAI_AGAIN binaries.prisma.sh

✗ Command failed: prisma migrate deploy

Error: request to [https://binaries.prisma.sh/all_commits/3cff47a7f5d65c3ea74883f1d736e41d68ce91ed/linux-musl-arm64-openssl-3.0.x/libquery_engine.so.node.gz⁠](https://binaries.prisma.sh/all_commits/3cff47a7f5d65c3ea74883f1d736e41d68ce91ed/linux-musl-arm64-openssl-3.0.x/libquery_engine.so.node.gz) failed, reason: getaddrinfo EAI_AGAIN binaries.prisma.sh


 ELIFECYCLE  Command failed with exit code 1.

ERROR: "check-db" exited with 1.

 ELIFECYCLE  Command failed with exit code 1.

Which Umami version are you using? (if relevant)

2.18.1

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

Docker

[mikecao]

The check-db scriot checks to see if there are any migrations for the database and runs them.

Not sure why it's downloading binaries at that point, but it's a Prisma thing we don't have control over.

[artfulrobot]

Did you find a solution?

[petter]

Did you find a solution?

We haven't yet found a solution to this, but are gonna experiment with building a patched image with binaries built in. I'll update here if it works out.

[idca6390]

we are having the same issue, did you find a solution for this?

[lewebsimple]

Same thing here with the docker.umami.is/umami-software/umami:postgresql-latest image.

[Maxime-J]

Since the pnpm switch, postinstall script which download prisma CLI engine must be allowed.
Building an image with this Dockerfile edit would resolve that, changing from:

# Script dependencies
RUN pnpm add npm-run-all dotenv prisma@

to

# Script dependencies
RUN pnpm --allow-build='@prisma/engines' add npm-run-all dotenv prisma@

Don't know if it's worth changing it in repo as Prisma planned to not use these binary engines anymore.

[yance-dev]

I know this might not be the most optimal solution, but it works for me. 🤔

What I did was run an Umami instance in an environment with internet access, make sure everything was working as expected, and then use docker commit on that container to create an Umami offline image.

docker commit umami-umami-1 ghcr.io/umami-software/umami:postgresql-latest

[petter]

We ended up creating our own Docker image which just runs npx prisma generate ...

ARG UMAMI_VERSION=postgresql-v2.18.1

FROM ghcr.io/umami-software/umami:${UMAMI_VERSION}

RUN npx prisma generate --schema=./prisma/schema.prisma

When using this image we are able to run it with no issues.