API container failing in docker
I recently started facing the below issue:
Running 10/10
✔ Container atscale-community-edition-tempo-1 Running 0.0s
✔ Container atscale-community-edition-collector-1 Running 0.0s
✔ Container atscale-community-edition-redis-1 Healthy 1.1s
✔ Container atscale-community-edition-postgres-1 Healthy 1.6s
✔ Container atscale-community-edition-loki-1 Running 0.0s
✔ Container atscale-community-edition-kong-1 Running 0.0s
✔ Container atscale-community-edition-promtail-1 Running 0.0s
✔ Container atscale-community-edition-identity-1 Healthy 1.1s
✔ Container atscale-community-edition-entitlement-1 Healt... 1.6s
✘ Container atscale-community-edition-api-1 Error 0.5s
dependency failed to start: container atscale-community-edition-api-1 is unhealth
Docker logs suggest the below:
addIssue: [Function (anonymous)],
2024-12-05 15:13:26 addIssues: [Function (anonymous)],
2024-12-05 15:13:26 errors: [
2024-12-05 15:13:26 {
2024-12-05 15:13:26 code: 'invalid_type',
2024-12-05 15:13:26 expected: 'string',
2024-12-05 15:13:26 received: 'undefined',
2024-12-05 15:13:26 path: [ 'ATSCALE_API_KC_PUBLIC_API_CLIENT_SECRET' ],
2024-12-05 15:13:26 message: 'Required'
2024-12-05 15:13:26 }
2024-12-05 15:13:26 ]
2024-12-05 15:13:26 }
Comments
7 comments
Thanks for the feedback Nadeem - the AtScale Product team has pushed out some updates that should solve the issue, go ahead and do another "docker compose up -d" and you should be good to go
Please let us know if any problems persist!
Hey Nadeem I just ran into the same thing upgrading to the latest - what are you using for resources on your Docker setup?
WSL 2 backend, resource limits are managed by Windows. CPU/Memory usage is pretty limited, barely 15-17% memory limit for all created containers
Atscale starts for a bit, and then throws up this error -
Application error: a server-side exception has occurred (see the server logs for more information).
Digest: 1136777656
Forum Admin - Hey unfortunately I am still facing the same error. FYI, I tried logging into my atscale account after more than a month. Could there be an issue of the license going dormant? (long shot, but trying to look at all possiblities)
+] Running 13/13
✔ Container atscale-community-edition-redis-1 Healthy 1.9s
✔ Container atscale-community-edition-tempo-1 Started 0.5s
✔ Container atscale-community-edition-collector-1 Started 1.0s
✔ Container atscale-community-edition-promtail-1 Started 1.0s
✔ Container atscale-community-edition-loki-1 Started 0.7s
✔ Container atscale-community-edition-kong-1 Started 1.2s
✔ Container atscale-community-edition-postgres-1 Healthy 22.4s
✔ Container atscale-community-edition-identity-1 Healthy 21.9s
✔ Container atscale-community-edition-entitlement-1 Healt... 22.4s
✘ Container atscale-community-edition-api-1 Error 26.8s
✔ Container atscale-community-edition-tutorial-1 Running 0.0s
✔ Container atscale-community-edition-engine-1 Running 0.0s
✔ Container atscale-community-edition-web-1 Running 0.0s
dependency failed to start: container atscale-community-edition-api-1 is unhealthy
The license key should not matter - I'll double check with the team to be sure there is nothing else on the key itself that could be causing an issue.
If you check the logs in Docker Desktop for the API service, do you see any errors? And if you attempt to start the API service via the UI, can you let me know if it starts and crashes or just won't start at all.
Hi, when I attempt to start the API via UI, it starts and then crashed. My atscale UI as well opens up for a couple of seconds at times, and then crashes. I am unable to figure out the issue through docker logs. A few days ago it seemed to be around ATSCALE_API_KC_PUBLIC_API_CLIENT_SECRET with the below error snippet:
2024-12-05 15:07:19 addIssue: [Function (anonymous)],
2024-12-05 15:07:19 addIssues: [Function (anonymous)],
2024-12-05 15:07:19 errors: [
2024-12-05 15:07:19 {
2024-12-05 15:07:19 code: 'invalid_type',
2024-12-05 15:07:19 expected: 'string',
2024-12-05 15:07:19 received: 'undefined',
2024-12-05 15:07:19 path: [ 'ATSCALE_API_KC_PUBLIC_API_CLIENT_SECRET' ],
2024-12-05 15:07:19 message: 'Required'
2024-12-05 15:07:19 }
2024-12-05 15:07:19 ]
2024-12-05 15:07:19 }
2024-12-05 15:07:19
But now I am seeing the logs different, unable to point the issue out. Would be too long to paste the logs. Please let me know if I can email them.
Please sign in to leave a comment.