· python
Vercel Container runtime supports plain Dockerfile or Containerfile deployment in beta
Developers can now deploy a standard root Dockerfile or Containerfile directly through Vercel's Container runtime, provided no other framework is identified in the project.
When this setup is in place, Vercel automatically chooses the Container preset, builds the specified file, and directs all incoming traffic to the generated image.
To begin utilizing containers on Vercel, simply include a Dockerfile within your project structure.
However, if project detection identifies a different framework, like Django, that existing framework determination takes precedence.
Should you wish to force the use of a Dockerfile or Containerfile for the build, you can execute the command `vercel project update --framework container`, or specify the framework within your `vercel.json` file.
It is important to note that a `Dockerfile.vercel` or `Containerfile.vercel` will override any framework detection, and multi-service deployments will retain their configuration using `vercel.json` services with a per-service entrypoint.
The Container runtime is currently in beta, operates using Vercel Functions, and utilizes Active CPU pricing for billing.
For comprehensive guidance, developers are encouraged to consult the Container runtime documentation to get started.
