Skip to content
This repository was archived by the owner on Aug 18, 2025. It is now read-only.

fix: clarify private images with CVMs #580

Merged
merged 2 commits into from
Sep 3, 2021
Merged

fix: clarify private images with CVMs #580

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
60f78dc
fix: clarify private images with CVMs
sreya Sep 3, 2021
9700fd2
Edit text
Sep 3, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions admin/workspace-management/cvms.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -141,8 +141,12 @@ container is what provides

## Images hosted in private registries

Please note that _non-cached_ CVM workspaces cannot be created using images hosted
in a private registry unless you permit unauthenticated access to the images.
To use CVM workspaces with private images, you **must** create a
[registry](../registries/index.md#adding-a-registry) with authentication
credentials. Private images that can be pulled directly by the node will not
work with CVMs.

This restriction is removed if you enable [cached CVMs](#enabling-cached-cvms).

## Image configuration

Expand Down