Overview
About 231 wordsLess than 1 minute
CNB provides hosting capabilities for common artifacts, where you can publish and share your artifacts.
Permission Control
In CNB, you can publish artifacts to specified repositories and share them based on repository visibility and permission controls.
The visibility of artifacts is consistent with the visibility of the repository they are published to. Authentication will use the user's repository permissions, with no need for additional artifact-specific configuration.
Resource | Action | Required Permission |
---|---|---|
Public Repository Artifacts | Pull | Anyone can pull, no authentication required |
Public Repository Artifacts | Push | Repository Developer and above |
Public Repository Artifacts | Delete | Repository Administrator and above |
Private Repository Artifacts | Pull | Repository Guest and above, authentication required |
Private Repository Artifacts | Push | Repository Developer and above |
Private Repository Artifacts | Delete | Repository Administrator and above |
CNB Artifact uses access tokens as authentication credentials. When logging in for artifact authentication, use 'cnb' as the username and your access token as the password. For example, using the Docker login command:
docker login docker.cnb.cool -u cnb -p {token-value}
Artifact Types
CNB currently supports the following artifacts:
Artifact Type | Domain |
---|---|
docker | docker.cnb.cool |
helm | helm.cnb.cool |
Storage Statistics
We charge based on the storage space occupied by your artifacts hosted on CNB. You can view the storage capacity used by each artifact in Repository-Usage Statistics.
Note: For Docker artifacts, duplicate base images are deduplicated when calculating storage capacity.