Stay organized with collections
Save and categorize content based on your preferences.
A base image is the starting point for most container-based development workflows.
Developers start with a base image and layer on top of it the necessary libraries,
binaries, and configuration files used to run their application. Google Cloud's buildpacks
publishes base images with multiple configurations of the available system packages and languages.
Security and maintenance updates to these base images are made available through
routine updates. Google Cloud's buildpacks applies these updates automatically or
lets you manually update, depending on the environment and your configuration.
For example, Cloud Run functions supports automatic updates.
Base images are hosted in every region where Artifact Registry is available.
You can customize the base image path by replacing the first portion of the URI
with your region of choice:
REGION with the preferred region, for example us-central1.
STACK with the preferred operating system stack, for example google-22.
RUNTIME_ID with the runtime ID used by your function, for example python310.
For example, buildpacks references the latest Node.js 20 base image using the google-22 stack,
hosted in us-central1 with the following URL:
us-central1-docker.pkg.dev/serverless-runtimes/google-22/runtimes/nodejs22.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[[["\u003cp\u003eBase images serve as the foundation for container development, allowing developers to add necessary components to run their applications.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Cloud's buildpacks provide regularly updated base images with various system package and language configurations, ensuring security and maintenance.\u003c/p\u003e\n"],["\u003cp\u003eBase images are available in all regions where Artifact Registry is present, and their URIs can be customized by specifying the desired region, stack, and runtime ID.\u003c/p\u003e\n"],["\u003cp\u003eThe document lists supported runtimes and their associated configurations, including Node.js, Python, Go, Java, Ruby, PHP, and .NET Core, along with their supported generations and environments.\u003c/p\u003e\n"],["\u003cp\u003eSecurity and maintenance updates can be done automatically or manually depending on the environment and the configuration, as supported in Cloud Run.\u003c/p\u003e\n"]]],[],null,["# Base images\n\nA base image is the starting point for most container-based development workflows.\nDevelopers start with a base image and layer on top of it the necessary libraries,\nbinaries, and configuration files used to run their application. Google Cloud's buildpacks\npublishes base images with multiple configurations of the available system packages and languages.\n\nSecurity and maintenance updates to these base images are made available through\nroutine updates. Google Cloud's buildpacks applies these updates automatically or\nlets you manually update, depending on the environment and your configuration.\nFor example, Cloud Run functions supports [automatic updates](/run/docs/configuring/services/automatic-base-image-updates).\n\nBase images are hosted in every region where Artifact Registry is available.\nYou can customize the base image path by replacing the first portion of the URI\nwith your region of choice:\n\n\u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e`-docker.pkg.dev/serverless-runtimes/`\u003cvar translate=\"no\"\u003eSTACK\u003c/var\u003e`/runtimes/`\u003cvar translate=\"no\"\u003eRUNTIME_ID\u003c/var\u003e\n\nReplace:\n\n- \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e with the preferred region, for example `us-central1`.\n- \u003cvar translate=\"no\"\u003eSTACK\u003c/var\u003e with the preferred operating system stack, for example `google-22`.\n- \u003cvar translate=\"no\"\u003eRUNTIME_ID\u003c/var\u003e with the runtime ID used by your function, for example `python310`.\n\nFor example, buildpacks references the latest Node.js 20 base image using the `google-22` stack,\nhosted in `us-central1` with the following URL:\n`us-central1-docker.pkg.dev/serverless-runtimes/google-22/runtimes/nodejs22`.\n\n### Node.js\n\n### Python\n\n### Go\n\n| **Note:** Go's [release policy](https://go.dev/doc/devel/release#policy) states that each major Go release is supported until there are two newer major releases. Key dates might not be available until newer versions of Go are made publicly available.\n\n### Java\n\n### Ruby\n\n### PHP\n\n### .NET Core"]]
