Skip to main content
Supported Regions:上海

Service Related

Error creating service: image repository quota exceeded or image repository namespace quota exceeded​

Users need to log in to the Tencent Cloud TCR console - select Guangzhou region - Personal Edition Shared Instance (first-time login requires initializing the personal image repository account according to the prompts), delete unnecessary image repositories or namespaces, and retry creating the CloudRun service after deletion.

Encountering "Service Frozen" prompt when clicking CloudRun​

CloudRun will freeze resources for users who have been inactive for a long time. After freezing, the service will be inaccessible. You can self-recover and unfreeze according to the pop-up guidance. After unfreezing, you need to redeploy the version to use it. Old versions cannot continue to be used.

Why aren't old CloudRun version instances automatically destroyed after deploying a new version?​

After creating new version instances, old version instances cannot be scaled down immediately, otherwise existing connections and traffic before the new version starts successfully will report errors. If multiple versions exist online and all have traffic, automatic scaling will not occur.

Instance scaling requires meeting the following two conditions:

  • No traffic for thirty minutes (only effective when minimum replicas set to 0)
  • Offline delayed scaling (version has no traffic)

Note that: the configured maximum replicas control the single version's pods. If multiple versions exist:
Maximum pods = Configured maximum replicas × Number of versions

Forced scaling can also be achieved by manually deleting old versions.

Why does CloudRun automatically scale even when CPU and memory usage rates haven't reached the configured scaling limits according to monitoring?​

In the monitoring, you can see CPU and memory usage rates. However, the memory usage rate in monitoring does not include Page Cache. Data in Page Cache also occupies memory. If the usage rate is consistently above the set value, it will result in inability to scale down.

Understanding Page Cache:

  • In Kubernetes, Cache in Pod memory typically refers to the Page Cache used by applications.
  • When applications read or write files, Page Cache caches file data and metadata to improve file access performance.
  • If applications in the Pod frequently read and write large amounts of files, Page Cache may occupy a lot of memory, causing the Pod's memory usage rate to be too high.

WeChat CloudRun call failed Error: cloud.callContainer:fail​

Specific error: Your server is Forbidden For CallContainer​

If the service version was created using CLI, you can check the CLI version number with the command:

tcb -v

If the version number is lower than 2.11.X, you can upgrade the version:

npm uninstall @cloudbase/cli -g  # Uninstall first
npm install @cloudbase/cli -g    # Then install

If the service version was not created with CLI, you can refer to the documentation