Google Cloud, deploying artifact registry docker image to Compute Engine fails with “No startup scripts to run.” instead of running docker file

The e2-micro instance has limited resources, so make sure your container’s CPU and memory requirements don’t exceed its capacity. If issues persist, try manually running the container and check the logs for errors:

sudo docker run -d –name my-container europe-west2-docker.pkg.dev/{project}/{dir}/{image-name}:{tag}

Also, check Container-Optimized OS logs for Docker issues:

sudo journalctl -u docker

Ensure the VM has the necessary Artifact Registry permissions and that outbound access to the registry is allowed if the VM is behind a firewall.