Error accessing Artifact Repository in recovered project: 'Project has been deleted'

Google Cloud Serverless Applications
1

I have a GCP project that was previously deleted and then recovered. I’m trying to pull a container image from Artifact Registry but receiving an error indicating the project is deleted, even though it has been recovered.

Command used:

docker pull asia-northeast3-docker.pkg.dev/lefthands-kr/repo-name/image-name@sha256:
Error message received:

Error response from daemon: Get “https://aasia-northeast3-docker.pkg.dev/lefthands-kr/repo-name/manifests/sha256:”: denied: denied: Project #406171074403 has been deleted.
Specific questions:

What are the necessary steps to re-enable and access Artifact Registry in a recovered project?
How can I resolve this specific error message?
Are there any special configurations or IAM permissions that need to be reset after project recovery?
Do I need to reconfigure authentication for docker to access the recovered repository?
Has anyone encountered a similar situation and successfully resolved it? Any help would be greatly appreciated.

Thank you in advance.

2

Hi @lefhhands-dev,

Welcome to Google Cloud Community!

According to this documentation, Restoring a project returns it to the state it was in before it was shut down, with certain exceptions::

  • Some services have delays in restoring and you might need to wait some time (up to 36 hours) for services to be restored.
  • Some services might need to be restarted manually.
  • You can recover most resources if you restore a project within the 30-day period.

Additionally, Repositories no longer work properly after you undelete a Google Cloud project or enable the Artifact Registry API after disabling it.

If you disable the Artifact Registry API or delete the project, Artifact Registry services become unavailable. Artifact Registry deletes repository data after 7 days.

I hope the above information is helpful.

1 Like