docs(harbor): clarify read-only mode behavior and replace hardcoded IP - #742
Open
Kibakus wants to merge 1 commit into
Open
docs(harbor): clarify read-only mode behavior and replace hardcoded IP#742Kibakus wants to merge 1 commit into
Kibakus wants to merge 1 commit into
Conversation
Signed-off-by: Kibakus <den01246@gmail.com>
Kibakus
force-pushed
the
Registry-Read-Only
branch
from
July 13, 2026 10:05
3fb7956 to
e750b4e
Compare
Vad1mo
reviewed
Jul 14, 2026
| ## Make the Registry Read Only | ||
|
|
||
| You can set Harbor to read-only mode. In read-only mode, Harbor allows `docker pull` but prevents `docker push` and the deletion of repositories and tags. | ||
| You can set Harbor to read-only mode. In read-only mode, Harbor prevents `docker push` and the deletion of repositories and tags. `docker pull` may not work with newer versions of Docker client due to additional requests made during pull; use `skopeo pull` or `skopeo copy` as an alternative. |
Member
There was a problem hiding this comment.
needs clarification: "additional requests"
Author
There was a problem hiding this comment.
We encountered unexpected behavior with Harbor 2.8.0 while it is in Read Only mode.
The documentation states that Read Only mode should only prevent push and delete operations, while pull should continue to work.
However, docker pull fails with:
Error response from daemon: error from registry: The system is in read only mode. Any modification is prohibited.
At the same time:
- curl to /v2/.../manifests/... returns 200 OK;
- curl to /v2/.../blobs/... returns 200 OK;
- skopeo inspect works;
- skopeo copy successfully downloads the image.
Author
|
@Vad1mo ? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR updates the read-only mode documentation by:
docker pullmay fail with newer Docker clients because of additional requests made during image pullskopeo pullorskopeo copyas an alternative when this happensharbor.example.comWhy
The previous documentation stated that
docker pullis always allowed in read-only mode, which is no longer true for newer Docker clients. This can confuse users who encounter unexpected failures while Harbor is in read-only mode.Using a hostname instead of a hardcoded IP also makes the example more generic and easier to follow.
Testing
Documentation only.