You can deploy a container image stored in Artifact Registry toCloud Run. You can also deploy directly from source toCloud Run, which includes automatically creating a container image foryour built source and storing the image in Artifact Registry.

Permissions required to deploy

Deploying from source

To deploy from source, you must havepermissionsto build, store the built container image, and deploy.

Deploying container images

To deploy to Cloud Run, you must have the ArtifactRegistry Reader role (roles/artifactregistry.reader) on the project orrepository containing the images you want to deploy and theCloud Rundeployment permissions.

If your repositories are in a different project, you must grantArtifact Registry Reader permissions to theCloud Run Service Agent.

Deploying from local source

Forsupported languages,Cloud Run can automatically:

1. Containerize local source code.
2. Push the container image to an Artifact Registry repository.
3. Deploy the container image Cloud Run from the repository.

Cloud Run pushes and pulls images using the repositorycloud-run-source-deploy in the region that you specify at deploy time.If the repository does not exist, Cloud Run creates it for you ifyour account has the requiredpermissions.

For details, seeDeploying from source code. You can also try theCloud Run quickstarts for languages thatsupport deploying from source code.

Deploying container images

You can deploy an image bytag or digest that is stored inArtifact Registry.

Deploying to a service for the first time creates its first revision. Note thatrevisions are immutable. If you deploy from a container image tag, it will beresolved to a digest and the revision will always serve this particular digest.

You can deploy a container using the Google Cloud console or thegcloudcommand line. For instructions see,Deploying container images.