A Vite dev server that crashes with ENOSPC inside Docker

Why does the dev server die on startup the moment a teammate opens your repo inside a container?

AdvancedRead 7 minDoing: under an hour6 steps

▶ Start

What you'll have at the end

The dev server starting cleanly inside the same container after you raise its file watcher limit

Before you start

You need

A project that already starts inside a container you can open a shell into, where the dev server running there is the one refusing to start with an error naming a source file it was trying to watch.

Not covered

Missed hot-reload updates once the watch table already has room, which is a separate fix, and setting a project up to run in a container for the first time.

Leans on

Docker Cheat Sheetthe full Compose Dependency Conditions and Security Practices tables, since this fix leans on both a startup ordering condition and a security tradeoff it only touches in passing.
Ubuntu Cheat Sheetthe whole Kernel Parameter Tuning table, for every other setting this same command family can change once you already have it open.
Linux Bash Scripting Cheat Sheetthe Input and Output table behind the exact syntax this recipe leaves you to fill in for writing the new settings into a file.
Vite Cheat Sheetthe Dev Server Configuration table for the rest of what this same server controls, since raising its watch ceiling only fixes the one setting this recipe is about.

6 steps

Where to go next

Restore Vite's HMR once reloads take over

if the crash is gone but saves still fall back to a full page reload instead of an instant update, that gap and its fix live there.

Checked 22 Aug 2026

Part of the Vite cookbook