@vercel/container
27.0.0 · 18 Nov 2026Apache-2.03.8M / weekRepositoryHomepagenpmAtom feed
Upgrading @vercel/container From 0.0.0 to 0.2.0
8 releases in betweenevery note read
Release by release
- New
Expose the resolved rewrite destination as the request path observed by containers, and warn affected container projects about the behavior change.
- New
- Fixed
Bump all workspace packages to trigger a full publish from vercel-internal.
- Fixed
- New
Add package manifest to container builder.
- New
- Fixed
Apply
functionsconfiguration (memory,maxDuration,architecture,regions,functionFailoverRegions,experimentalTriggers,supportsCancellation) to container runtime outputs. The@vercel/containerbuilder now resolves matchingvercel.json/ per-servicefunctionsentries at build time, and the CLI writes those settings into the container.vc-config.json.
- Fixed
- Fixed
Fixed
vercel devfor thecontainerframework when used as a top-level build (outside ofservices).
- Fixed
- Fixed
Refine container detection for
services/experimentalServicesV2.
- Fixed
- New
Support deploying any project as a container via a
Dockerfile.vercelorContainerfile.vercelmarker. A new experimentalcontainerframework preset detects these files and is listed first so it takes precedence over all other frameworks — a project that also looks like (e.g.) a Next.js app will deploy as a container when one of these markers is present. As an experimental framework it is gated behindVERCEL_USE_EXPERIMENTAL_FRAMEWORKS. The@vercel/containerbuilder now recognizes the.vercelmarkers, auto-discovers them when its entrypoint is<detect>, and supports root (non-service) container deploys. - Fixed
Fix container service build output so requests reach the function. Container services now do a normal build, emitting the function at the natural
indexpath inside the nestedservices/<name>/output along with a catch-all route, instead of namespacing under_svc/<name>/indexwith no route to it. Previously a request to the service root never matched the function.
- New
- New
Add an experimental container service runtime. A service with
runtime: "container"either builds itsDockerfile/Containerfileand pushes the resulting OCI image to the Vercel Container Registry (VCR), or passes a prebuilt image reference through as build output. - Fixed
vc devno longer leaks host/shell-only environment variables into container services. Variables that describe the developer's machine rather than the Linux container — notably macOSTMPDIR(/var/folders/.../T), plusHOME,PATH,SHELL, and similar — are now filtered out of the container's env. Previously they were passed through and broke apps that write to the OS temp dir (e.g. Ghost's multer upload middleware failed withEACCES). The container's own values for these are used instead. - Fixed
vc devnow publishes container services on the host port the services orchestrator pre-allocated (meta.port) instead of a Docker-chosen ephemeral port. Service bindings target the pre-allocated port (http://127.0.0.1:<port>/), so a container published on a different port was unreachable for cross-service requests. Falls back to an ephemeral port when no port is provided.
- New
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.