Hi, first of all thanks for finally supporting containers
Now while trying to check the support as described on Run any Dockerfile on Vercel - Vercel post I ended up with a 404, and the deployment logs don’t mention any container build taking place, maybe something is still missing from the overall approach?
Hi thanks for replying, naturally, hence why I linked the blog post as well as starting point,
Also as feedback for the documentation, it would be more interesting if it used more common languages used in container development like Java, Go, C#, not JavaScript examples.
Anyway, my approach was while following the blog post:
created a project with vercel add project
dumped the Go and Dockerfile.vercel examples from blog post into the directory
did a vercel deploy
build log suggests nothing has done regarding image creations, other than creating a domain
14:06:44.828 Running build in Washington, D.C., USA (East) – iad1
14:06:44.828 Build machine configuration: 2 cores, 8 GB
14:06:44.842 Retrieving list of deployment files...
14:06:44.845 Skipping build cache, deployment was triggered without cache.
14:06:45.388 Downloading 2 deployment files...
14:06:45.696 Running "vercel build"
14:06:45.716 Vercel CLI 54.18.6
14:06:45.960 Build Completed in /vercel/output [25ms]
14:06:46.031 Deploying outputs...
14:06:47.174 Deployment completed
14:06:47.273 Creating build cache...
14:06:47.286 Skipping cache upload because no files were prepared
The files placed at the project root as described in the blog post
The samples on Container Images seem to clearly be ignoring containers as well.
Node.js and srvx dynamic server example is actually being deployed via Deploy a Node.js server capability
Whereas Nginx static server example, basically returns the index.html directly without any use of ngix.
In any of the examples, the log as shown on the blog post isn’t visible.
Instead of
▲ vercel deploy
Vercel CLI
✓ Building image from Dockerfile.vercel
✓ Stored image in your project's registry
✓ Deployed to Fluid compute
Production: https://my-server.vercel.app
One gets
PS C:\Projects\vercel\ngix> vercel deploy
Vercel CLI 54.20.0 (Node.js 26.3.0)
Directory C:\Projects\vercel\ngix
? Which team? paulopinto-xxxxxxx's projects
Found existing project
Project paulopinto-xxxxxxx-projects/ngix
? Link directory to project? yes
✓ Linked paulopinto-xxxxxxx-projects/ngix
? Pull development environment variables into .env.local? yes
> Downloading `development` environment variables for paulopinto-xxxxxxx-projects/ngix
✓ Created .env.local file and added it to .gitignore
Inspect https://vercel.com/paulopinto-xxxxxxx-projects/ngix/663mR5LHVicYHjjMKaD94gHYznBN
Production https://ngix-qkzn9szov-paulopinto-xxxxxxx-projects.vercel.app
▲ Aliased https://ngix.vercel.app
On a new project it would have automatically detected the Dockerfile.vercel and used the Container preset. I opened an internal ticket to get the docs updated with a note about changing the preset for cases where it can’t be automatically set.