Supported language runtimes and base images

This page describes the supported language runtimes and base images for deploying services or functions from source, and container images built on scratch .

Base images are composed of an operating system stack and a language runtime:

• A stack is made up of a Linux distribution version and system packages, such as OpenSSL and curl .
• A language runtime is the specific version of the programming language used by your application.

Cloud Run supports multiple language runtimes, each of which is available through container base images provided by Google Cloud's buildpacks . Language runtimes are supported only as long as they are supported by their respective open source communities.

It is the developer's responsibility to upgrade services to newer language runtimes before it reaches end of support. Refer to the Cloud Run runtime lifecycle for details.

The Cloud Run lifecycle policy does not apply to containers built outside of Cloud Run.

Using language runtimes

Cloud Run language runtimes are used for the following:

• Deploying functions and services
• Enabling automatic security updates
• As base images for building containers

Security and maintenance updates

Security and maintenance updates are available for generally available language runtimes. You can apply these updates automatically or manually depending on how you configure automatic security updates . Automatic security updates are enabled by default when deploying functions and services to Cloud Run.

How to obtain base images

Base images are hosted in every region where Artifact Registry is available .

There are three methods for specifying a base image:

• RUNTIME_ID : Gives you the base image for the specified language using its default stack. The base image will be taken from a repository in the same REGION where your service is deployed. We recommend you specify the RUNTIME_ID for most cases.
• STACK / RUNTIME_ID : An alias for the full base image path. The base image will be taken from a repository in the same REGION where your service is deployed. Use this option if you need a specific system package in the stack .
• REGION -docker.pkg.dev/serverless-runtimes/ STACK /runtimes/ RUNTIME_ID : The full base image path. Use this option if you want full control over the specific base image and the region where it's downloaded from.

For the three methods for specifying a base image, replace:

• REGION with the preferred region, for example europe-west1 .
• STACK with the preferred operating system stack , for example google-22-full .
• RUNTIME_ID with the language runtime ID used by your function, for example nodejs22 .

For example, to reference the full base image path for the latest Node.js 20 base image using the google-22-full stack, hosted in europe-west1 , use the following URL:

europe-west1-docker.pkg.dev/serverless-runtimes/google-22-full/runtimes/nodejs22

Node.js

Python

Go

Java

Ruby

PHP

Runtime	Runtime ID	Stacks	Runtime base image
PHP 8.4	php84	google-22-full (default)	google-22-full/php84
PHP 8.3	php83	google-22-full (default)	google-22-full/php83
PHP 8.2	php82	google-22-full (default)	google-22-full/php82
PHP 8.1	php81	google-18-full	google-18-full/php81
PHP 7.4	php74	google-18-full	google-18-full/php74

.NET