Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
4d05f22f
Commit
4d05f22f
authored
Mar 04, 2021
by
Alvin Gounder
Committed by
Nick Gaskill
Mar 04, 2021
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Minor update to container_registry documentation for clarity
parent
df5fcb4e
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
doc/administration/packages/container_registry.md
doc/administration/packages/container_registry.md
+2
-2
No files found.
doc/administration/packages/container_registry.md
View file @
4d05f22f
...
...
@@ -900,12 +900,12 @@ not directly accessible via `tag`:
sudo
gitlab-ctl registry-garbage-collect
-m
```
Without the
`-m`
flag, the Container Registry only removes layers that are not referenced by any manifest, tagged or not.
Since this is a way more destructive operation, this behavior is disabled by default.
You are likely expecting this way of operation, but before doing that, ensure
that you have backed up all registry data.
When the command is used without the
`-m`
flag, the Container Registry only removes layers that are not referenced by any manifest, tagged or not.
### Performing garbage collection without downtime
> [Introduced](https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/764) in GitLab 8.8.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment