@vercel/container@0.0.4
📦 vercel-cliView on GitHub →
✨ 2 features🐛 6 fixes🔧 3 symbols
Summary
This patch primarily fixes several issues related to the `vercel dev` experience for the container framework, ensuring correct file detection, preventing build errors during dev, and improving container reuse and error reporting.
✨ New Features
- The dev server now correctly maps the container preset's <detect> sentinel to discovered Dockerfiles (Dockerfile.vercel, Containerfile.vercel, Dockerfile, or Containerfile) when used as a top-level build.
- The container dev server is now reused across requests, keeping a live container running instead of rebuilding the image and starting a new container on every HTTP request.
🐛 Bug Fixes
- Fixed `vercel dev` for the `container` framework when used as a top-level build, preventing warnings about not matching source files.
- Prevented `@vercel/container build()` from throwing `` `vercel dev` cannot build container images from a Dockerfile `` during dev.
- Fixed an issue where a container build output (OCI image reference) was incorrectly treated as a zip-based function, avoiding the `output.createZip is not a function` error.
- The dev path now correctly discovers `Dockerfile.vercel` / `Containerfile.vercel` opt-in markers when the container entrypoint is the `<detect>` sentinel, matching build path behavior.
- Improved error handling for `vercel dev` when the Docker daemon is not running, providing a clear message instead of a cryptic exit code 125 error.
- Container start failures during dev now correctly name the container and include the underlying Docker error output.