[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-08-18。"],[[["\u003cp\u003eThis document provides general troubleshooting steps for all artifact formats in Artifact Registry, with links to format-specific guides.\u003c/p\u003e\n"],["\u003cp\u003eYou can use the \u003ccode\u003egcloud artifacts locations list\u003c/code\u003e command to view all supported Artifact Registry locations, keeping in mind any organization policy restrictions.\u003c/p\u003e\n"],["\u003cp\u003eTo view available repositories, use the \u003ccode\u003egcloud artifacts repositories list\u003c/code\u003e command, specifying either a project or a specific location, to see the proper repository names.\u003c/p\u003e\n"],["\u003cp\u003eWhen using third-party clients, you need to use the full repository path and follow the specific conventions of that client.\u003c/p\u003e\n"],["\u003cp\u003eIf you've undeleted a project or re-enabled the Artifact Registry API, repositories may no longer work correctly, and data may be permanently lost after 7 days.\u003c/p\u003e\n"]]],[],null,["# General troubleshooting\n\nLearn about troubleshooting steps that apply to all artifact formats when\nworking with Artifact Registry. For issues specific to an artifact format,\nrefer to the format-specific page.\n\n- Container images: [Container images](/artifact-registry/docs/docker/troubleshoot), [Helm charts](/artifact-registry/docs/helm/troubleshoot)\n- Language packages: [Java](/artifact-registry/docs/java/troubleshoot), [Node.js](/artifact-registry/docs/nodejs/troubleshoot), [Python](/artifact-registry/docs/python/troubleshoot)\n- [OS packages](/artifact-registry/docs/os-packages/troubleshoot)\n\nInvalid repository or location in commands\n------------------------------------------\n\nUse the following information to help you diagnose invalid repository location\nor invalid repository name errors.\n\n### Location and repository defaults for gcloud\n\nIf you set a default [repository and location](/artifact-registry/docs/gcloud-defaults) in the Google Cloud CLI\nso that you can omit `--location` and `--repository` flags from\n`gcloud artifacts` commands, try running the command that failed with the\nflags and corresponding values. For details about the syntax for a particular\ncommand, run the command with the `--help` flag.\n\nThe default repository setting does not apply to `gcloud artifacts` commands\nwhere you specify a repository name without the `--repository` flag. For\nexample, you must specify the repository name in a\n[gcloud artifacts repositories describe](/sdk/gcloud/reference/artifacts/repositories/describe) command like the\nfollowing example: \n\n gcloud artifacts repositories describe my-repo --location=us-west1\n\nIf your command still fails, you might need to verify that you specified valid\nvalues for the repository or location.\n\n### Repository location\n\nTo list all supported Artifact Registry locations, run the command: \n\n gcloud artifacts locations list\n\nYour organization policy might include\n[location restrictions](/resource-manager/docs/organization-policy/defining-locations-supported-services#artifact-registry). Artifact Registry enforces\nthese restrictions at repository creation time.\nArtifact Registry does not enforce policy retroactively on repositories\nthat predate the location restrictions.\n\n### Repository names in gcloud commands\n\nYou can list repositories to view the repository names in a specified project\nor location.\n\nTo list all repositories in a project, run the command: \n\n gcloud artifacts repositories list --project=\u003cvar translate=\"no\"\u003ePROJECT-ID\u003c/var\u003e \\\n --location=all\n\nTo list all repositories in a location, run the command: \n\n gcloud artifacts repositories list --project=\u003cvar translate=\"no\"\u003ePROJECT-ID\u003c/var\u003e \\\n --location=\u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e\n\nReplace \u003cvar translate=\"no\"\u003ePROJECT-ID\u003c/var\u003e with your Google Cloud project ID and\n\u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e with the repository location.\n\nThe command returns information for each repository similar to the following\nexample: \n\n REPOSITORY: my-repo\n FORMAT: DOCKER\n DESCRIPTION:\n LOCATION: us-west1\n LABELS:\n ENCRYPTION: Google-managed key\n CREATE_TIME: 2021-09-23T19:39:10\n UPDATE_TIME: 2021-09-23T19:39:10\n\nThe value for `REPOSITORY` is the value you use with `gcloud artifacts` commands\nthat include the repository name as a parameter.\n\nFor example, this command uses the `--repository` flag: \n\n gcloud artifacts packages list --location=us-west1 --repository=my-repo\n\nThis command uses the repository name only without a flag: \n\n gcloud artifacts repositories describe my-repo --location=us-west1\n\n### Repository names with third-party clients\n\nFor third-party clients, you generally use a full repository path when\nconfiguring clients, such as\n`us-west1-docker.pkg.dev/my-project/my-repo`. You\nthen follow the conventions of the client for uploading and downloading\npackages. For client configuration and usage details, refer to the documentation\nfor the format you are working with.\n\n- Container images: [Docker](/artifact-registry/docs/docker), [Helm](/artifact-registry/docs/helm)\n- Language packages: [Java](/artifact-registry/docs/java), [Node.js](/artifact-registry/docs/nodejs), [Python](/artifact-registry/docs/python), [Go](/artifact-registry/docs/go)\n- OS packages: [Debian](/artifact-registry/docs/os-packages/debian), [RPM](/artifact-registry/docs/os-packages/rpm)\n\nIf you are transitioning from Container Registry, note that all image paths must include an Artifact Registry repository name. You cannot specify an image path that only includes a project ID.\n\n\u003cbr /\u003e\n\n- **Invalid path** : `us-east1-docker.pkg.dev/my-project/my-image`\n- **Valid path** : `us-east1-docker.pkg.dev/my-project/my-repo/my-image`\n\nCannot push or pull from undeleted repositories\n-----------------------------------------------\n\nRepositories no longer work properly after you undelete a Google Cloud\nproject or enable the Artifact Registry API after disabling it.\n\nIf you disable the Artifact Registry API or\n[delete the project](/resource-manager/docs/creating-managing-projects#shutting_down_projects), Artifact Registry services become\nunavailable. Artifact Registry deletes repository data after 7 days.\n\n[Learn more about data deletion on Google Cloud](/security/deletion)."]]