[CRITICAL] Docker image fails to start - Prisma 7 requires Node.js >= 20.19.0

[gabrielem]

📜 Description

The latest Docker image (ghcr.io/gitroomhq/postiz-app:latest) fails to start due to an incompatibility between the Node.js version in the Docker image and Prisma 7.0.0 requirements.

Prisma 7.0.0 (released November 19, 2025) requires Node.js >= 20.19.0, but the current Docker image appears to be using an older version (likely 20.18.x or earlier).

🔴 Error Log

.../node_modules/prisma preinstall: ┌────────────────────────────────────────────────────────────────────┐
.../node_modules/prisma preinstall: │    Prisma only supports Node.js versions 20.19+, 22.12+, 24.0+.    │
.../node_modules/prisma preinstall: │    Please upgrade your Node.js version.                            │
.../node_modules/prisma preinstall: └────────────────────────────────────────────────────────────────────┘
.../node_modules/prisma preinstall: Failed
ELIFECYCLE Command failed with exit code 1.

The container enters a restart loop and never becomes operational.

👟 Reproduction Steps

1. Pull the latest Postiz Docker image:

   docker pull ghcr.io/gitroomhq/postiz-app:latest

2. Start the container using the official docker-compose.yml

3. Check container logs:

   docker-compose logs -f postiz

4. Observe the Prisma preinstall error and container restart loop

👍 Expected Behavior

The container should start successfully and Postiz should be accessible.

👎 Actual Behavior

Container fails during npm install phase with Prisma version compatibility error and enters restart loop.

💻 Environment

• Docker Image: ghcr.io/gitroomhq/postiz-app:latest
• Installation Method: Docker Compose (official configuration)
• Date: November 26, 2025
• Prisma Version: 7.0.0 (released November 19, 2025)

🔍 Root Cause

According to Prisma 7 upgrade guide, the minimum supported Node.js versions are:

• Node.js 20: >= 20.19.0
• Node.js 22: >= 22.12.0
• Node.js 24: >= 24.0.0

The current Docker image appears to use Node.js 20.18.x or earlier, which is incompatible.

💡 Suggested Solution

Update the Dockerfile to use a compatible Node.js version:

# Option 1: Node 22 LTS (recommended)
FROM node:22-alpine

# Option 2: Node 24 (latest)
FROM node:24-alpine

# Option 3: Specific Node 20 version
FROM node:20.19-alpine

🚨 Impact

This is a critical blocker for:

• New installations of Postiz
• Users pulling the latest image
• Anyone updating their existing deployment

🔧 Temporary Workaround

Users can temporarily pin to a previous version in docker-compose.yml:

services:
  postiz:
    image: ghcr.io/gitroomhq/postiz-app:v1.6.7  # Last working version

✅ Checklist

• I have checked existing issues for duplicates
• I have provided complete error logs
• I have identified the root cause
• I have suggested a solution
• This affects production deployments

📚 References

• Prisma 7.0.0 Release: https://www.prisma.io/blog/announcing-prisma-orm-7-0-0
• Prisma 7 Upgrade Guide: https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-7
• Prisma System Requirements: https://www.prisma.io/docs/orm/reference/system-requirements

[gabrielem]

For anyone hitting this issue right now:

Quick fix until this is resolved officially:

# In your docker-compose.yml, change:
image: ghcr.io/gitroomhq/postiz-app:latest

# To:
image: ghcr.io/gitroomhq/postiz-app:v1.6.7

Then run:

docker-compose down
docker-compose pull
docker-compose up -d

Your data in volumes will be preserved. ✅

[egelhaus]

I think you have a corrupted instance, as we do use node 22.

Dockerfile.dev :
FROM node:22.20-alpine