This page lists known issues for Cloud Run.
You can also check for existing issues or open new issues in the public issue trackers.
Google Cloud services not yet supported
The following table lists services that are not yet supported by Cloud Run.
|Web Security Scanner|
High request latency with custom domains when invoking from some regions
Requests to Cloud Run services using custom domains can
have a very high latency from some locations.
This issue is more pronounced for Cloud Run services
If you observe this issue, you can achieve greater performance with
Cloud Load Balancing using a serverless NEG.
HTTP/2 Push is not supported
Using HTTP/2 with IAP is not supported
Cloud Run services with HTTP/2 enabled encounter an infinite redirect loop upon request when secured with IAP. This behavior is not intended and Google anticipates addressing this in the future. For now, to avoid this behavior Google recommends using the default HTTP/2 configuration (disabled) when a service sits behind IAP.
Using VPC with Cloud SQL with egress settings
Unsupported HTTP request methods
Requests with HTTP methods
CONNECT are not supported and therefore
will not be received by services running on Cloud Run.
Reserved URL paths
It is not possible to use the following URL paths:
- Paths starting with
- Some paths ending with
Reduced availability when using 3 or less maximum instances
Revisions using a maximum number of instances of 3 or less might experience unexpected downtime.
Multi Architecture Image Format is not supported
The Multi Architecture Image is not supported at this time.
HOME environment variable is set to
Cloud Run sets the
HOME environment variable to
You can't mount secrets on
/tmp in first generation execution environment
If you use first generation execution environment,
you cannot mount secrets on
/tmp directly. However, you can mount secrets on any subdirectory of
Cloud Run job tasks may be spuriously marked as retried
In some situations, a task can be marked as having been retried, when in fact the
task succeeded on its first try. Until this issue is resolved, Google recommends
--max-retries parameter set to 3 or higher to avoid spurious
IPV6 doesn't work with
vpc-egress set to all-traffic
For Cloud Run jobs and any Cloud Run service using the
second generation runtime environment, IPV6 doesn't work if
vpc-egress is set
Reduced availability for containers with a startup time longer than 10 seconds
Requests waiting for a container instance to start are kept in a queue for a maximum of 10 seconds. As a consequence, if a container has a startup time longer than 10 seconds, requests sent to it will be aborted. This can happen after a deployment that receives 100% of the traffic or when requests need to be sent to a new instance during autoscaling.
You can mitigate this issue by [gradually rolling out revisions](/run/docs/rollouts-rollbacks-traffic-migration#gradual and by optimizing startup time.