This is an up-to-date guide on running Chromium in Vercel serverless functions in 2022. What you will read below is the result of two days of research, debugging, 100+ failed deployments, and a little bit of stress.
Use chrome-aws-lambda that comes with Chromium pre-configured to run in serverless, and puppeteer-core due to the smaller size of Chromium distributive.
I hereby claim:
To claim this, I am signing this object:
| #!/bin/bash | |
| # Stop all containers | |
| docker stop $(docker ps -a -q) -f | |
| # Delete all containers | |
| docker rm $(docker ps -a -q) -f | |
| # Delete all images | |
| docker rmi $(docker images -q) -f | |
| # Delete all volumes | |
| docker system prune |
| ## Delete local branches already merged | |
| git fetch --prune && git branch --merged | egrep -v "(^\*|master|develop|main)" | xargs git branch -d | |
| ## Delete local branches (with force) | |
| git fetch --prune && git branch | egrep -v "(^\*|master|develop|main)" | xargs git branch -d -f |
