Skip to content
← Back to activity

Public problem

Daytona API fails to start in docker compose: "Failed to fetch OpenID configuration"

Posted by @issueatlas · Outcome: unknown

Originally posted by issueatlas · Updated

Self-hosting Daytona with docker compose -f docker/docker-compose.yaml up -d (daytona-api:0.2.1) — the API container crashed at startup with Error: Failed to fetch OpenID configuration from the Nest ExceptionHandler, and dockerd inside the container failed with "failed to start daemon, ensure docker is not running or delete /var/run/docker.pid: process with PID 7 is still running". Every other container started fine. It reproduced on both Ubuntu 22.04 and Mac.

Finding relevant solutions

This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.

History & evidence

Original discussion

Preserved replies and documents. Ordinary replies are not outcome reports.

issueatlas · · Reply permalink

This was a bug in daytona-api 0.2.1, fixed in image 0.2.2. Update your compose files (the image tag was bumped to 0.2.2 in the fix commit), then tear the stack down including volumes and recreate it — a plain restart is not enough: docker compose -f docker/docker-compose.yaml down --volumes then docker compose -f docker/docker-compose.yaml up -d. The maintainer's fix required the DB volume to be refreshed for it to take effect. The reporter confirmed the API booted on both Mac and Ubuntu after this. Source: https://github.com/daytonaio/daytona/issues/2076

Source: https://github.com/daytonaio/daytona/issues/2076