跳到主内容
智客 ZICQ

技能库 智客分类:运维与云 render-docker

Render Docker

在Render-Dockerfile上建造并部署多级容器、多级建筑、蓝图多克球场、私人注册、层缓存和平台限制。 当用户提及 Docker, Dockerfile, 容器图像, 多相建置, 容器注册, GHCR, ECR, BuildKit, dockerContext, 运行时的 Docker 或图像时使用, 或者优化 Docker 建立在 Render 上.

469 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

在Render-Docker文件、多阶段建筑、蓝图多克字段、私人登记、层缓存和平台限制上建造和部署多克容器

何时用

- 编写或调试一个** Docker file** 用于渲染服务

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Render Docker Deployments、When to Use、Render Docker Builds、Blueprint Configuration、Multi-Stage Builds、Build Args vs Secrets。

文件分析

文件分析:除 SKILL.md 外,正文引用了 references/dockerfile-patterns.md、references/registry-setup.md、references/optimization-guide.md,属于带资源的技能包,这些文件按需再读。

官方 description(原文)

Builds and deploys Docker containers on Render—Dockerfiles, multi-stage builds, Blueprint Docker fields, private registries, layer caching, and platform constraints. Use when the user mentions Docker, Dockerfile, container images, multi-stage builds, container registry, GHCR, ECR, BuildKit, dockerContext, runtime docker or image, or optimizing Docker builds on Render.

Render Docker DeploymentsWhen to UseRender Docker BuildsBlueprint ConfigurationMulti-Stage BuildsBuild Args vs SecretsRegistry ConfigurationLayer CachingPlatform Specifics`.dockerignore` and Start CommandsReferencesRelated Skills

兼容:Any Render compute service (web, private, worker, cron) with runtime: docker or runtime: image. · 许可:MIT

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
render-docker
description
Builds and deploys Docker containers on Render—Dockerfiles, multi-stage builds, Blueprint Docker fields, private registries, layer caching, and platform constraints. Use when the user mentions Docker, Dockerfile, container images, multi-stage builds, container registry, GHCR, ECR, BuildKit, dockerContext, runtime docker or image, or optimizing Docker builds on Render.
compatibility
Any Render compute service (web, private, worker, cron) with runtime: docker or runtime: image.
许可
MIT
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 3
  • references/dockerfile-patterns.md
  • references/registry-setup.md
  • references/optimization-guide.md

以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「render-docker」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-54b0f46e38bc67f9-%E7%BA%A2%E8%89%B2%E5%A4%9A%E5%85%8B.html
请存为 .cursor/skills/render-docker/SKILL.md 或 .claude/skills/render-docker/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/render-oss/skills 取完整目录,不要只建一个 SKILL.md。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/render-oss/skills' --list

npx skills add 'https://github.com/render-oss/skills' --skill 'render-docker'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版

name: render-docker description: >- Builds and deploys Docker containers on Render—Dockerfiles, multi-stage builds, Blueprint Docker fields, private registries, layer caching, and platform constraints. Use when the user mentions Docker, Dockerfile, container images, multi-stage builds, container registry, GHCR, ECR, BuildKit, dockerContext, runtime docker or image, or optimizing Docker builds on Render. license: MIT compatibility: >- Any Render compute service (web, private, worker, cron) with runtime: docker or runtime: image. metadata: author: Render version: "1.0.0" category: deployment

Render Docker Deployments

Render uses BuildKit for Docker builds. All compute service types that support custom runtimes can use runtime: docker (build from a Dockerfile in the repo) or runtime: image (pull a prebuilt image; no Dockerfile build on Render). Deeper patterns and copy-paste templates live under references/.

When to Use

  • Authoring or debugging a Dockerfile for a Render service
  • Choosing runtime: docker vs runtime: image in a Blueprint
  • Wiring private base images or prebuilt images with registry credentials
  • Multi-stage builds, build args, secrets, and layer caching
  • Performance and security hardening of container images on Render

For full Blueprint authoring, see render-blueprints. For end-to-end deploy flows, see render-deploy.

Render Docker Builds

  • BuildKit is used for Docker builds on Render.
  • runtime: docker: Render builds an image from your repo using dockerfilePath, dockerContext, and optional dockerCommand (overrides image CMD).
  • runtime: image: Render pulls image.url; no repo-based image build. Set image.creds.fromRegistryCreds.name when the registry is private.

Blueprint Configuration

| Field | Role | |-------|------| | dockerfilePath | Path to the Dockerfile (default ./Dockerfile) | | dockerContext | Build context directory (what is sent to the daemon) | | dockerCommand | Overrides the container CMD after the image is built | | image.url | Image reference for runtime: image (registry/repo:tag or digest) | | image.creds | Dashboard-stored credential reference for a private prebuilt image | | registryCredential | Dashboard-stored credential reference for private base images used by runtime: docker |

Example sketch (values illustrative):

services:
  - type: web
    name: api
    runtime: docker
    region: oregon
    plan: starter
    dockerfilePath: ./Dockerfile
    dockerContext: .
    dockerCommand: node server.js
    envVars:
      - key: PORT
        value: 10000

For runtime: image, set image.url and, if needed, image.creds per Registry Configuration below.

Multi-Stage Builds

Recommended for production. Use a builder stage for compilation and dependency installation, and a minimal runner stage that only copies artifacts and runtime files. Benefits:

  • Smaller images and faster pulls
  • Fewer tools and secrets in the final image (smaller attack surface)
  • Clear separation between build-time and run-time dependencies

See references/dockerfile-patterns.md for language-specific templates.

Build Args vs Secrets

Critical: Never pass secrets via ARG. Build arguments are stored in image layers and can be recovered from the image history or intermediate layers.

  • Prefer runtime environment variables (Render env vars / secret files) for application secrets.
  • For build-time secrets (e.g. private package feeds), use Docker BuildKit secret mounts (RUN --mount=type=secret,...) rather than ARG.

Treat anything sensitive as runtime or BuildKit secret mount, not as a build arg.

Registry Configuration

Private base images (for runtime: docker) or prebuilt images (runtime: image) need authentication:

  • Store credentials in the Render Dashboard under Registry Credentials.
  • For runtime: docker, reference private base-image credentials with registryCredential.fromRegistryCreds.name.
  • For runtime: image, reference private prebuilt-image credentials with image.creds.fromRegistryCreds.name.

Supports common registries (Docker Hub, GHCR, ECR, Google Artifact Registry, and others). Step-by-step per provider: references/registry-setup.md.

Prebuilt image services do not auto-deploy when the tag moves in the registry; trigger a manual redeploy or use a deploy hook when you publish a new image.

Layer Caching

  • Render caches Docker layers between builds; order Dockerfile instructions so that frequently unchanged layers stay early (see references/optimization-guide.md).
  • Tags and caching: mutable tags like latest can resolve to stale cached images. Prefer immutable references: digest (repo/image@sha256:...) or version pins (v1.2.3).

Platform Specifics

  • Render builds linux/amd64. Avoid assumptions about other architectures in production images.
  • Port binding matches native services: bind HTTP to 0.0.0.0:$PORT (Render sets PORT).
  • Health checks behave like non-Docker web services (healthCheckPath, etc.).
  • Secret files from Render appear under /etc/secrets/ — do not rely on repo-root secret paths inside the container unless you copy or mount them explicitly in the image.

.dockerignore and Start Commands

  • Always maintain a .dockerignore that excludes node_modules, .git, .env, build artifacts, logs, and OS junk. This shrinks context upload time and avoids leaking local files into layers. Lists and rationale: references/optimization-guide.md.
  • Custom start command: if you need multiple shell steps, use a single shell form, e.g. /bin/sh -c 'set -e; ./migrate && exec node server.js' (prefer exec so your app receives signals for graceful shutdown).

References

| Document | Contents | |----------|----------| | references/dockerfile-patterns.md | Multi-stage templates (Node, Python, Go, Ruby, Rust, static sites) | | references/registry-setup.md | Docker Hub, GHCR, ECR, Artifact Registry + Blueprint wiring | | references/optimization-guide.md | Layer order, .dockerignore, BuildKit cache mounts, debugging |

Related Skills

  • render-deploy — Deploy flows, Blueprint vs Dashboard, operational steps
  • render-blueprints — Full render.yaml schema, wiring, and validation
  • render-web-services — Web service behavior, health checks, and HTTP edge cases

相关技能

运维与云

Docker Essentials

用于容器管理,图像操作,调试的基本道克命令和工作流程.

运维与云

Find Skills

从开放的代理技能生态系统中发现并安装技能. 使用时:(1)用户问"我如何做X",X可能拥有现有技能,(2)用户说"为X找到技能"或"是否为X有技能",(3)用户问"你能否做X",X是专门能力,(4)用户想扩展代理能力,(5)用户想搜索工具,模板,或工作流程,(6)用户提到他们希望…

运维与云

Microsoft Foundry

构建,部署,评价,优化,微调,管理微软创始代理,模型,资源最终结束. 用法:铸造、azd ai代理、azd 提供/部署、托管代理脚手架/开发/运行/部署/拖放、即时代理创建、创建代理、更新代理、添加代理工具、援引代理、代理.yaml、评估代理、批量活化、连续活化、持续监测、代理C…

运维与云

Azure Deploy

执行已有.azure/部署计划.md和基础设施文件的ALREADY-PREPARED应用程序的Azure部署。 当用户向 CREATE 请求新应用程序时, 请不要使用此技能 。 这种技能运行了 azd上行, azd 部署, trarraform 应用, 和 az 部署命令带有内置…