Troubleshooting ESPv2 Container Deployment and Image Naming Issues

[Nam-Kieudang]

We have followed the ESPv2 App Engine (https://cloud.google.com/endpoints/docs/openapi/set-up-app-engine-standard-environment-espv2) documentation steps to build and deploy new containers and services. The images are stored in the Container Registry.

However, we've noticed that the newly created images have different names than previous ones. The format of the image name is correct according to the documentation as `<ESP_VERSION>-<CLOUD_RUN_HOSTNAME>-<CONFIG_ID>`, but recently the image names have included the prefix `no-new-use-public-image` (as shown in the screenshot below).

Additionally, during the "Deploying the ESPv2 container" step using the `gcloud run deploy` command, we encounter an error indicating that the images cannot be accessed, even though the image url is correctly and the necessary permissions have been granted.

Cloud Run API check failed. Requests will be rejected after January 2025 hard enforcement deadline. User does not have access to image gcr.io/<project_id>/endpoints-runtime-serverless:<image_name>

Why did the image name change like that and is this name change causing an error when deploying the espv2 container on cloud run?

[-Rhett · Accepted solution]

Hi @Nam-Kieudang,

While searching about your issue, I came across a GitHub thread that seemed closely related to your post. I just wanted to confirm, was that also you who posted on the Google Cloud Platform esp-v2 issue tracker?

From the thread, it looks like the issue was resolved by:

• Updating Endpoints release to 2.51.0
• Confirming user or service account had correct IAM roles for the quickstart
• Migrating images from Container Registry to Artifact Registry

To make sure everything completely works, I want to verify if you’re able to successfully deploy your APIs on Cloud Endpoints. If yes, here are additional resources that can help you learn more about Cloud Endpoints:

• API management best practices
• Cloud Endpoints how-tos
• OpenAPI feature limitations and known issues

By the way, thanks for raising the issue about the code. We’ve monitored this internally and are looking to improve the script with respect to GCR being deprecated. If you want to help out, you may file a detailed bug report through the Issue Tracker. Feel free to include steps to replicate, configuration settings, screenshots, and other details of the issue to help us investigate. While there isn’t a specific timeframe for resolution, once we've fixed an issue in production we'll indicate this and then update and close the bug.

I hope this helps!

[Nam-Kieudang]

Hi @-Rhett 

Yes, I posted on the Google Cloud Platform ESP-v2 issue. Thank you for pointing that out.

I appreciate the suggestions. I will try updating the Endpoints release to 2.51.0 to remove prefix no-new-use-public-image in the image name, and ensure that the user or service account has the correct IAM roles. I also migrated from Container Registry to Artifact Registry to resolve the Cloud Run deployment problem.

Thanks again for your help!