cl4ysg5/s3-uploadThis is the source code for a RunPod Serverless worker that uses the ComfyUI API for inference.
!Docker Pulls !Worker Version
The model(s) for inference will be loaded from a RunPod Network Volume.
You can send requests to your RunPod API Endpoint using the /run
or /runsync endpoints.
Requests sent to the /run endpoint will be handled asynchronously,
and are non-blocking operations. Your first response status will always
be IN_QUEUE. You need to send subsequent requests to the /status
endpoint to get further status updates, and eventually the COMPLETED
status will be returned if your request is successful.
Requests sent to the /runsync endpoint will be handled synchronously
and are blocking operations. If they are processed by a worker within
90 seconds, the result will be returned in the response, but if
the processing time exceeds 90 seconds, you will need to handle the
response and request status updates from the /status endpoint until
you receive the COMPLETED status which indicates that your request
was successful.
You can optionally Enable a Webhook.
| Status | Description |
|---|---|
| IN_QUEUE | Request is in the queue waiting to be picked up by a worker. You can call the /status endpoint to check for status updates. |
| IN_PROGRESS | Request is currently being processed by a worker. You can call the /status endpoint to check for status updates. |
| FAILED | The request failed, most likely due to encountering an error. |
| CANCELLED | The request was cancelled. This usually happens when you call the /cancel endpoint to cancel the request. |
| TIMED_OUT | The request timed out. This usually happens when your handler throws some kind of exception that does return a valid response. |
| COMPLETED | The request completed successfully and the output is available in the output field of the response. |
The serverless handler (rp_handler.py) is a Python script that handles
the API requests to your Endpoint using the runpod
Python library. It defines a function handler(event) that takes an
API request (event), runs the inference using the model(s) from your
Network Volume with the input, and returns the output
in the JSON response.
Pull requests and issues on GitHub are welcome. Bug fixes and new features are encouraged.
探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
在 Linux 系统配置镜像服务
在 Docker Desktop 配置镜像
Docker Compose 项目配置
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
VS Code Dev Containers 配置
MacOS OrbStack 容器配置
在宝塔面板一键配置镜像
Synology 群晖 NAS 配置
飞牛 fnOS 系统配置镜像
极空间 NAS 系统配置服务
爱快 iKuai 路由系统配置
绿联 NAS 系统配置镜像
QNAP 威联通 NAS 配置
Podman 容器引擎配置
HPC 科学计算容器配置
ghcr、Quay、nvcr 等镜像仓库
无需登录使用专属域名
需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
免费版仅支持 Docker Hub 访问,不承诺可用性和速度;专业版支持更多镜像源,保证可用性和稳定速度,提供优先客服响应。
专业版支持 docker.io、gcr.io、ghcr.io、registry.k8s.io、nvcr.io、quay.io、mcr.microsoft.com、docker.elastic.co 等;免费版仅支持 docker.io。
当返回 402 Payment Required 错误时,表示流量已耗尽,需要充值流量包以恢复服务。
通常由 Docker 版本过低导致,需要升级到 20.x 或更高版本以支持 V2 协议。
先检查 Docker 版本,版本过低则升级;版本正常则验证镜像信息是否正确。
使用 docker tag 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。
来自真实用户的反馈,见证轩辕镜像的优质服务