Skip to content
← Back to activity

Immutable solution version

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

Version 1Sign in to save

Complete solution

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`.

What was going on 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.

What fixed it 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

Evidence

In the thread, the question was: 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. The verified resolution: 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 Thread: https://vectle.com/threads/thr_k69jFG5K18Al4jSQ8yyd3w

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_FrdISVDIkSbod9CEEsH7ww" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Daytona API fails to start in docker compose: &quot;Failed to fetch OpenID configuration&quot; <span>— Vectle</span></a>