Prisma 1.34 - Docker (2025)

Overview

Prisma servers can be run with Docker. This page contains everything you need to know around the Docker setup and relevant worfklows.

Prisma Docker image

The prisma Docker image is available via Docker Hub. You can pull the latest released version of the image using the following command:

docker pull prismagraphql/prisma

Common workflows

The Docker CLI and Docker Compose CLI are used to manage the Prisma servers.

Here's a quick rundown of the most important commands:

• docker-compose up -d: Start a new Prisma server to which you can deploy your Prisma services.
• docker-compose stop: Stops the Prisma server.
• docker-compose pull: Downloads the latest Prisma images from Docker Hub
• docker logs: Shows the logs of the Prisma server (helpful for debugging).

Note that these commands need to be executed in the directory where the Docker Compose file for your Prisma server is available.

Docker Compose file

Here is an overview of all properties you need to configure on the prisma Docker image inside your Docker Compose file. The all-uppercase words represent placeholders for the configuration variables you need to provide for your Prisma setup.

version: '3'services: prisma: image: prismagraphql/prisma:__LATEST_PRISMA_VERSION__ restart: always ports: - '4466:4466' environment: PRISMA_CONFIG: | managementApiSecret: __YOUR_MANAGEMENT_API_SECRET__ port: __YOUR_PRISMA_SERVER_PORT__ databases: default: connector: __YOUR_DATABASE_CONNECTOR__ host: __YOUR_DATABASE_HOST__ port: __YOUR_DATABASE_PORT__ user: __YOUR_DATABASE_USER__ password: __YOUR_DATABASE_PASSWORD__ connectionLimit: __YOUR_CONNECTION_LIMIT__

Most notably most of your configuration takes place in the PRISMA_CONFIG environment variable.

Despite seemingly following the YAML key-value structure, PRISMA_CONFIG is actually speficied as a string. The pipe character | right after PRISMA_CONFIG denotes the beginning of a multi-line string in YAML.

PRISMA_CONFIG reference

Root properties

These are the root properties of PRISMA_CONFIG:

Database properties

Each database object in the databases object needs to include the following properties:

Debugging

To get insights into the internals of your Prisma server, you can check the logs of the Docker container.

Accessing Docker logs

View the raw logs from the running Docker containers:

docker-compose logs

Verify Docker containers

Verify that the containers are running:

docker ps

You should see an output similar to this:

$ docker psCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES2b799c529e73 prismagraphql/prisma:1.34 "/bin/sh -c /app/sta…" 17 hours ago Up 7 hours 0.0.0.0:4466->4466/tcp myapp_prisma_1757dfba212f7 mysql:5.7 "docker-entrypoint.s…" 17 hours ago Up 7 hours 3306/tcp prisma-db

This is helpful when you're getting an error message saying Error response from daemon: No such container.

Logging slow queries

To monitor and log slow queries, you can set the following environment variables in your Docker Compose file:

• SLOW_QUERIES_LOGGING: Enable slow query logging with true or false
• SLOW_QUERIES_LOGGING_THRESHOLD: The treshold (in miliseconds) for queries for queries to be logged. To log all queries, simply provide the value "0".

Here is an example:

version: '3'services: prisma: image: prismagraphql/prisma:__LATEST_PRISMA_VERSION__ restart: always ports: - '4466:4466' environment: SLOW_QUERIES_LOGGING: 'true' SLOW_QUERIES_LOGGING_THRESHOLD: '0' PRISMA_CONFIG: | managementApiSecret: __YOUR_MANAGEMENT_API_SECRET__ port: __YOUR_PRISMA_SERVER_PORT__ databases: default: connector: __YOUR_DATABASE_CONNECTOR__ host: __YOUR_DATABASE_HOST__ port: __YOUR_DATABASE_PORT__ user: __YOUR_DATABASE_USER__ password: __YOUR_DATABASE_PASSWORD__ connectionLimit: __YOUR_CONNECTION_LIMIT__

In the logs of your Docker container (which you can access with docker logs __CONTAINER_ID__), you can then see the the execution time for queries above specified threshold, for example:

SLOW QUERY - DURATION: 17QUERY: [{"query":"{ users { id email name }}","variables":{}},{"query":"{ users { id email name }}","variables":{}}]

You can find more info in this GitHub issue.

Hard resetting the Docker environment

If your local Prisma server is in an unrecoverable state, it might be necessary to completely reset it:

docker-compose killdocker-compose downdocker-compose up -d