Skip to content

feat(comfyui): add comfyui image - #11

Merged
swibrow merged 2 commits into
mainfrom
feat/comfyui
Aug 29, 2026
Merged

feat(comfyui): add comfyui image#11
swibrow merged 2 commits into
mainfrom
feat/comfyui

Conversation

@swibrow

@swibrow swibrow commented Aug 29, 2026

Copy link
Copy Markdown
Contributor

ComfyUI v0.34.0 on CUDA-enabled PyTorch, for GPU image and video generation workflows. Consumed by ai/comfyui in home-ops on the RTX 3090 Ti node, to run Wan 2.2 text-to-video.

Notes

  • amd64 only. The CUDA torch build targets the x86_64 GPU host; an arm64 copy would be several GB of image nothing can schedule a GPU onto.
  • cu130. CUDA 13 still supports Ampere (sm_86), which is what the 3090 Ti needs.
  • The torch trio is pinned as a set. Upstream wound torchaudio down, so the cu130 index stops at 2.11.0 while torch is already at 2.13.0. Letting pip resolve freely downgrades torch to match torchaudio, so all three are explicit and must move together. Renovate tracks torch; a bump there needs the other two checked.
  • torch is installed from the CUDA index before requirements.txt, which lists all three unpinned - pip then treats them as satisfied rather than pulling CPU wheels from PyPI over the top.

Validation

hadolint -c .hadolint.yaml passes. The build itself was not run locally - this is an amd64 CUDA image and the dev machine is arm64, so an emulated multi-GB pip install is not a useful check. CI builds it on a native amd64 runner and runs the metadata test, which is the real gate.

ComfyUI v0.34.0 on CUDA-enabled PyTorch, for GPU image and video generation.
Built for the RTX 3090 Ti node, so amd64 only - an arm64 copy would be several
GB nothing can schedule a GPU onto.

torch/torchvision/torchaudio are pinned as a set rather than resolved: upstream
wound torchaudio down, so the cu130 index stops at 2.11.0 while torch is
already at 2.13.0, and a free resolve downgrades torch to match.

Signed-off-by: swibrow <15628653+swibrow@users.noreply.github.com>
Kubernetes args override CMD, so with CMD-only and no ENTRYPOINT a consumer
setting args would have the runtime exec the first flag as the binary.

Signed-off-by: swibrow <15628653+swibrow@users.noreply.github.com>
@swibrow
swibrow merged commit 2249b70 into main Aug 29, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant