Status: retired, never published. Recorded 2026-09-12 (tracker C.12.05).
oshunai/runpod-comfyui does not exist on Docker Hub (404, verified
2026-09-11) and never will: no Docker Hub account is being created (user
decision, 2026-09-11). Every image this directory builds is tagged
oshunai/runpod-comfyui:<flavor>, so nothing built here has ever been pushed
anywhere, and the workflow that pushes it cannot succeed.
The design is also the one the Chroma/RunPod work deliberately moved away from:
each flavor bakes its own model set into the image (the flagship-image
inventory alone lists 47 baked artifacts). The replacement keeps models on a
RunPod network volume and loads them on demand, from a single slim image built
by RunPod's own git integration — docker/runpod/comfyui-slim/, which is what
the live endpoints actually run.
Why it is still here#
C.12.05 says to retire this "once nothing references them". Things still do. This is the caller scan, run 2026-09-12, so the next person does not have to redo it:
| Reference | What it does |
|---|---|
scripts/isis/generate_runpod_endpoint_image_manifests.mjs |
Syncs INTO this directory (workflow_catalog, isis_nodes) and is a CI gate over node/model consistency |
scripts/isis/validate_runpod_endpoint_image_manifests.mjs |
Validates the manifest the generator emits |
infra/runpod/endpoints/image-build-manifest.json |
13 of its 17 endpoints build from this context |
infra/runpod/endpoints/image-build-config.json |
The generator's input; the flavors are declared there |
.github/workflows/deploy-runpod.yml |
Path filter (line ~97) and a buildx job with this context (lines ~305–306) |
docker/runpod/comfyui/tests/test_catalog_renderer.py |
Unit tests for catalog_renderer.py |
DEPENDENCIES.md, V1/features/external-models-and-execution.md, ISIS_TODOS_2.md |
Prose references |
Roughly forty scripts/isis/generate-v2-*/validate-v2-* scripts read
image-build-manifest.json itself. They do not name this directory, but they do
consume what the generator produces from it, so the manifest cannot simply lose
13 endpoints without checking them.
The order a removal has to happen in#
Deleting this directory first would break a CI gate and a deploy workflow, which is why C.12.05 is still open rather than done:
- Decide what happens to the 13 flavor endpoints in
infra/runpod/endpoints/image-build-config.json— removed, or marked retired the waycomfyui-vace/comfyui-ltx2/comfyui-flagship-videoalready are ininfra/runpod/endpoints/inventory/(status: "retired-never-published"). - Regenerate
image-build-manifest.jsonand check everygenerate-v2-*/validate-v2-*consumer still passes against the smaller manifest. - Remove the comfyui build job and path filter from
.github/workflows/deploy-runpod.yml. - Move
catalog_renderer.py+ its test, or drop them — the TypeScript port (libs/isis/workflows/src/templates/catalog-renderer.ts) is what the live path uses; this copy is the original the port was made from. - Then, and only then, delete this directory.
Until step 5, treat everything here as frozen: it is not the build path, it is not deployed, and changes to it do not reach any running endpoint.