Skip to content

Latest commit

 

History

History
47 lines (32 loc) · 1.8 KB

ts_add_namespace.md

File metadata and controls

47 lines (32 loc) · 1.8 KB
copyright lastupdated keywords subcollection content-type
years
2017, 2024
2024-04-25
registry, namespace, value, characters, delete
Registry
troubleshoot

{{site.data.keyword.attribute-definition-list}}

Why can't I add a namespace in {{site.data.keyword.registryshort_notm}}?

{: #troubleshoot-add-namespace} {: troubleshoot} {: support}

Setting up a namespace fails in {{site.data.keyword.registrylong}}. {: shortdesc}

When you run ibmcloud cr namespace-add, you are unable to set your entered value as the namespace. {: tsSymptoms}

The following alternatives are possible causes: {: tsCauses}

  • Scenario A. You used invalid characters in the namespace value.
  • Scenario B. You entered a namespace value that is already being used by another {{site.data.keyword.cloud_notm}} organization.
  • Scenario C. A namespace was recently deleted and you're reusing its name. If the namespace that was deleted contained many resources, the deletion might not yet be fully processed by {{site.data.keyword.registryshort}}.

You can fix this problem in the following ways: {: tsResolve}

Follow any instructions that are in the returned error message. If that is not successful, or no instructions are provided, try the following options:

  • Scenario A. Check that you entered a valid namespace:
    • Your namespace must be unique across all {{site.data.keyword.cloud_notm}} accounts in the same region.
    • Your namespace must be 4 - 30 characters long.
    • Your namespace must start and end with a letter or number.
    • Your namespace must contain lowercase letters, numbers, hyphens (-), and underscores (_) only.
  • Scenario B. Choose a different value for your namespace.
  • Scenario C. If you're re-creating a namespace that was deleted, and it contained many images, try again later.