render-disks

Attaches and manages persistent disks on Render services including mount paths, sizing, and snapshots.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/DingJun1028/esggo-kv --skill render-disks-dingjun1028
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: render-disks
Source: https://github.com/DingJun1028/esggo-kv/tree/main/.agents/skills/render-disks
Command: npx skills add https://github.com/DingJun1028/esggo-kv --skill render-disks-dingjun1028

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Render services use an ephemeral filesystem by default, so all local file changes are lost on every deploy or restart. This Skill guides you through attaching persistent disks so uploads, databases, and stateful data survive deployments. ## Core Features & Use Cases - Disk Setup & Configuration: Attach disks via the Dashboard or Blueprint (render.yaml) with correct mount paths per runtime (Node.js, Go, Docker) and avoid disallowed paths. - Constraint Awareness: Understand critical limits—single instance only, no zero-downtime deploys, no build-time disk access, and size can grow but never shrink. - Snapshots & File Transfers: Use automatic 24-hour snapshots with 7-day retention, full restores, and SCP or magic-wormhole file transfers. - Use Case: Deploy a WordPress CMS on Render with media uploads persisted at /var/data, sized at 10 GB, while understanding why horizontal scaling is disabled. ## Quick Start Ask the assistant to attach a 10 GB persistent disk mounted at /var/data to my Render web service using a Blueprint.

Frequently Asked Questions about render-disks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a persistent disk to a Render service?▼

Add a persistent disk from your service's Disks page in the Render Dashboard by setting a mount path and size in GB, or define a disk block with name, mountPath, and sizeGB in your render.yaml Blueprint. Adding a disk triggers a new deploy.

Can a Render service with a disk scale horizontally?▼

No, services with an attached disk are limited to a single instance and cannot use autoscaling. Disks also disable zero-downtime deploys, so the old instance stops before the new one starts.

Why can't my build script access the Render disk?▼

Disks are only mounted at runtime; buildCommand and preDeployCommand run on separate compute without disk access. Move any disk-dependent logic into your service's start command instead.

Should I use a Render disk or Render Postgres for a database?▼

Prefer Render Postgres for relational databases because it provides managed backups, point-in-time recovery, and replicas. Self-managed databases on disks require database-native backup tools like mysqldump, since disk snapshots may capture corrupted database states.

How do Render disk snapshots and restores work?▼

Render automatically snapshots disks every 24 hours and retains them for at least 7 days. Restores are full-disk only and destructive—all changes after the snapshot are permanently lost and the service restarts during restore.

Can I decrease the size of a Render disk after creation?▼

No, disk size can be increased at any time without downtime but can never be decreased. Start with the smallest viable size and grow as needed, since billing is based on provisioned size.