Containers · 4 November 2026

A slug addresses a container, and Cloud Run services keep the name requested

Containers accept an optional spec.slug: 1 to 63 lowercase letters, digits and hyphens, starting with a letter and not ending with a hyphen, unique within the project and set at create only. A create that repeats a slug in use returns 409 conflict, and the slug is released when the container is deleted. GET, PATCH and DELETE /v2/containers/{id} accept the slug in place of the ID; other kinds whose name is unique within the project, such as queues, accept that name the same way. A request by name requires the key's get permission on the kind. In the Google Cloud Run Admin API v2 at /compat/google-cloud-run, services.create now stores serviceId as the container's slug: the service's name is projects/{project}/locations/{location}/services/{serviceId}, and services.get, services.patch and services.delete accept that name. A second create with the same serviceId in the project returns 409 instead of returning the first service; a service created without serviceId is named by its container ID, as before. A slug is unique within a project, not within each location. A service's description now returns 400 instead of being stored as the container's name.