Vercel's Container runtime now supports deploying a standard root Dockerfile or Containerfile if no other framework is identified.
In this scenario, Vercel employs the Container preset, builds the specified file, and directs all incoming traffic toward the resulting image.
To initiate container usage on Vercel, one must introduce a Dockerfile to the project structure.
However, if project detection identifies a different framework, such as Django, that framework's configuration takes precedence.
Alternatively, to force the use of the Dockerfile or Containerfile for building, operators can execute the command `vercel project update --framework container`, or configure this within `vercel.json`.
A file named `Dockerfile.vercel` or `Containerfile.vercel` will override any detected framework configuration. Furthermore, multi-service deployments maintain their structure using `vercel.json` services, including a per-service entrypoint.
It is noted that the Container runtime is currently in beta. Operationally, it functions on Vercel Functions and is subject to Active CPU pricing.
This capability expands the deployment options available to platform operators, allowing for direct containerization workflows when standard framework detection is absent.
