vxcontrol/pentagi
1
0
Fork 0
mirror of https://github.com/vxcontrol/pentagi.git synced 2026-07-21 08:15:23 -04:00
Code Issues 45 Packages Projects Releases 9 Wiki Activity

[GH-ISSUE #309] [Bug] v2.0.0 - failed to get primary docker image: API returned unexpected status code: 502 on fresh install #99

New Issue
Open
opened 2026-06-06 22:09:07 -04:00 by yindo · 1 comment
yindo commented 2026-06-06 22:09:07 -04:00
Owner
Copy Link
Copy Source

Originally created by @zabeliqbal on GitHub (May 11, 2026).
Original GitHub issue: https://github.com/vxcontrol/pentagi/issues/309

Describe the bug

Fresh install of PentAGI v2.0.0 (Docker image created 2026-04-11) fails when creating new flows. Error: failed to get primary docker image: API returned unexpected status code: 502

Environment

  • PentAGI version: v2.0.0-2ec8ef3
  • Docker version: 29.4.2
  • Deployment: Docker Compose
  • OS: Debian 12

Configuration

  • Fresh database (recreated volumes)
  • LLM: Custom OpenAI-compatible endpoint (Qwen2.5-Coder-32B)
  • Docker settings: DOCKER_INSIDE=true, DOCKER_NET_ADMIN=true, DOCKER_GID=988

Error Logs

time="2026-05-11T19:08:01Z" level=error msg="failed to get flow provider" error="failed to get primary docker image: API returned unexpected status code: 502"
graphql request handled with errors: input: createFlow failed to create flow worker: failed to get flow provider: failed to get primary docker image: API returned unexpected status code: 502

Steps to reproduce

  1. Fresh install with docker-compose
  2. Login to PentAGI
  3. Create new flow
  4. Error occurs immediately

Expected behavior

Flow should create successfully and spawn worker container

Additional context

  • Database wiped and recreated (fresh volumes)
  • Docker socket accessible from container
  • PentAGI can access Docker daemon
  • Reproduced on fresh install after complete cleanup (containers, volumes, networks)
Originally created by @zabeliqbal on GitHub (May 11, 2026). Original GitHub issue: https://github.com/vxcontrol/pentagi/issues/309 ## Describe the bug Fresh install of PentAGI v2.0.0 (Docker image created 2026-04-11) fails when creating new flows. Error: `failed to get primary docker image: API returned unexpected status code: 502` ## Environment - PentAGI version: v2.0.0-2ec8ef3 - Docker version: 29.4.2 - Deployment: Docker Compose - OS: Debian 12 ## Configuration - Fresh database (recreated volumes) - LLM: Custom OpenAI-compatible endpoint (Qwen2.5-Coder-32B) - Docker settings: DOCKER_INSIDE=true, DOCKER_NET_ADMIN=true, DOCKER_GID=988 ## Error Logs ``` time="2026-05-11T19:08:01Z" level=error msg="failed to get flow provider" error="failed to get primary docker image: API returned unexpected status code: 502" graphql request handled with errors: input: createFlow failed to create flow worker: failed to get flow provider: failed to get primary docker image: API returned unexpected status code: 502 ``` ## Steps to reproduce 1. Fresh install with docker-compose 2. Login to PentAGI 3. Create new flow 4. Error occurs immediately ## Expected behavior Flow should create successfully and spawn worker container ## Additional context - Database wiped and recreated (fresh volumes) - Docker socket accessible from container - PentAGI can access Docker daemon - Reproduced on fresh install after complete cleanup (containers, volumes, networks)
yindo commented 2026-06-06 22:09:08 -04:00
Author
Owner
Copy Link
Copy Source

@asdek commented on GitHub (May 29, 2026):

hey @zabeliqbal

this error is raised on your LLM backend side and here to check logs there.

recently we discussed in the community chat similar issue with sglang, there was an error with tool-call-parser settings, might be it the same.

<!-- gh-comment-id:4580559191 --> @asdek commented on GitHub (May 29, 2026): hey @zabeliqbal this error is raised on your LLM backend side and here to check logs there. recently we discussed in the community chat similar issue with sglang, there was an error with tool-call-parser settings, might be it the same.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: vxcontrol/pentagi#99
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?