--- title: Container Runtime product: vercel url: /docs/functions/runtimes/container canonical_url: "https://vercel.com/docs/functions/runtimes/container" last_updated: 2026-07-07 type: how-to prerequisites: - /docs/functions/runtimes - /docs/functions related: - /docs/functions/usage-and-pricing - /docs/cli/deploy - /docs/git - /docs/container-registry - /docs/services summary: Run any code and library on Vercel Functions with an OCI container image built from a Dockerfile or Containerfile at the project root. install_vercel_plugin: npx plugins add vercel/vercel-plugin --- # Container Runtime > Container Runtime is available in Beta on all plans Vercel Functions can run any code and library using Open Container Initiative (OCI) container images, built from a `Dockerfile` or `Containerfile` in your project. Functions scale up and down automatically based on demand, and use [Active CPU](/docs/functions/usage-and-pricing) pricing. You are only billed for CPU when your code is actively running, not while waiting for I/O or sleeping. ## Related pages > **For AI agents:** Follow these links to understand how this page connects to the rest of the Vercel ecosystem. For the full cross-link map (inbound, outbound, prerequisites, and semantic neighbors), see the .graph.md link below. - [Does Vercel support Docker deployments?](https://vercel.com/kb/guide/does-vercel-support-docker-deployments) — Vercel supports deploying OCI-compatible container images through Vercel Functions and Vercel Container Registry, with A - [Running Docker on Vercel](https://vercel.com/kb/guide/docker) — Learn how to run Docker on Vercel by deploying OCI container images as Vercel Functions, storing them in Vercel Containe - [How to use Vercel Container Registry](https://vercel.com/kb/guide/how-to-use-vercel-container-registry) — Push, store, and pull OCI container images with Vercel Container Registry, then deploy them to Vercel Functions and Verc - [How to choose between Functions, containers, and Daemons on Vercel](https://vercel.com/kb/guide/vercel-functions-containers-daemons) — Choose Vercel Functions for HTTP requests, container images for custom runtimes, and Daemons for continuous background w - [Run any Dockerfile on Vercel](https://vercel.com/blog/dockerfile-on-vercel) - [Deploy a Node.js Fastify app on Vercel with Docker](https://vercel.com/kb/guide/deploy-nodejs-on-vercel-with-docker) — Build a Node.js application with Fastify and Docker, then deploy it to Vercel Functions. Learn how to configure environm - [Bring your Dockerfile to Vercel Functions](https://vercel.com/changelog/bring-your-dockerfile-to-vercel-functions) - [Glossary](https://vercel.com/docs/glossary) — Learn about the terms and concepts used in Vercel's products and documentation. - [Bring Your Own Cloud](https://vercel.com/docs/networking/bring-your-own-cloud) — Bring Your Own Cloud \\(BYOC\\) lets you run Vercel Functions behind your project in your own AWS account while Vercel rou Full cross-link map for this page: [/docs/functions/runtimes/container.graph.md](/docs/functions/runtimes/container.graph.md) ## Migrate an existing Docker app To move an existing Docker app to Vercel, follow the migration guide for your current platform: - [Migrate from Railway to Vercel](/kb/guide/migrate-railway-to-vercel) - [Migrate from Fly.io to Vercel](/kb/guide/migrate-fly-io-to-vercel) - [Migrate from Render to Vercel](/kb/guide/migrate-render-to-vercel) - [Migrate from Google Cloud Run to Vercel](/kb/guide/migrate-cloud-run-to-vercel) - [Migrate self-hosted Next.js and containers from AWS to Vercel](/kb/guide/migrate-containers-from-aws-to-vercel) ## Usage ### Dockerfile A root `Dockerfile` or `Containerfile` is enough when Vercel detects no other framework. On a new project, Vercel selects the Container preset, builds that file, and routes all traffic to the image. When the project already matches another framework, such as Next.js, Vercel keeps that framework. Set the project framework to Container to build the root file. `--yes` skips the confirmation prompt: ```bash vercel project update --framework container --yes ``` A `Dockerfile.vercel` or `Containerfile.vercel` file selects the Container preset when that preset should win over another detected framework. Create a `Dockerfile` at the project root: #### Node.js and srvx dynamic server ```docker filename="Dockerfile" FROM node:26-alpine RUN npm i -g srvx WORKDIR /app COPY server.ts . # srvx listens on $PORT by default CMD ["srvx", "--prod"] ``` ```ts filename="server.ts" export default { fetch(req: Request) { return Response.json({ ip: req.headers.get("x-forwarded-for") }) } } ``` #### Nginx static server ```docker filename="Dockerfile" FROM nginx:alpine COPY . /usr/share/nginx/html ``` ```html filename="index.html"

Hello from Vercel Functions running a custom OCI image!

``` Deploy your application using the [Vercel CLI](/docs/cli/deploy) or by pushing to a [Git repository](/docs/git). During the build step, the image will be built and pushed to [VCR](/docs/container-registry). You can also develop and test locally using `vercel dev`. This requires the `docker` CLI and Docker daemon to be available on your machine. ### Services A single root `Dockerfile` deploys with the steps above. Use [services](/docs/services) to run multiple applications, backends, or frontends in the same Vercel project. Traffic is routed to the correct service with the `rewrites` configuration: ```json {5,9} filename="vercel.json" { "services": { "frontend": { "root": "frontend/", "entrypoint": "Dockerfile" }, "backend": { "root": "backend/", "entrypoint": "Dockerfile" } }, "rewrites": [ { "source": "/api/(.*)", "destination": { "service": "backend" } }, { "source": "/(.*)", "destination": { "service": "frontend" } } ] } ``` ```docker filename="frontend/Dockerfile" FROM nginx:alpine ... ``` ```docker filename="backend/Dockerfile" FROM node:26-alpine ... ``` Set the `entrypoint` key to the path of your dockerfile, relative to the service's `root`, for each service that uses a custom container image. See [services](/docs/services) for more information on configuring services. ## Observability You can view [runtime logs](/docs/functions/logs) from the container's `stdout` and `stderr` streams. Because these logs are not tied to a specific request, they are broadcast to all inflight requests of the instance. [Vercel Observability](/docs/observability) metrics are available like any regular Vercel Function. ## Port resolution Vercel Functions running container images are expected to open an HTTP server to receive traffic on. The default port is `80`, and it can be overridden by setting the `PORT` [environment variable](/docs/environment-variables) in the project settings. ## Scale in behavior Functions not receiving any traffic for 5 minutes in production environments, and 30 seconds in preview environments, will automatically scale down. When a function instance is scaled down, the container receives a `SIGTERM` signal with a 30 seconds grace period to clean up before being forcefully terminated. Learn more about the [`SIGTERM` signal](/docs/functions/functions-api-reference#sigterm-signal). ## Limits and pricing The same [limits](/docs/functions/limitations) and [Active CPU pricing model](/docs/functions/usage-and-pricing) of Vercel Functions apply to custom container images. [Secure Compute](/docs/networking/secure-compute) and [Static IPs](/docs/networking/static-ips) are not yet supported with custom container images. ## Related - [Vercel Functions](/docs/functions) - [Vercel Container Registry](/docs/container-registry) - [Daemons](/docs/daemons) for container images that run continuously without receiving traffic - [Container Images Demo template](https://vercel.com/templates/container-images/container-images-demo) --- [View full sitemap](/docs/sitemap) If you encounter incorrect information, can’t find what you need, need a capability Vercel doesn’t currently offer, or have any other feedback to report, please do it by following the instructions at https://vercel.com/feedback.md.