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
d5f080e1
Commit
d5f080e1
authored
Jun 25, 2020
by
Tim Poffenbarger
Committed by
Suzanne Selhorn
Jun 25, 2020
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add note for expired image garbage collection
parent
47465b47
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
3 deletions
+7
-3
doc/user/packages/container_registry/index.md
doc/user/packages/container_registry/index.md
+7
-3
No files found.
doc/user/packages/container_registry/index.md
View file @
d5f080e1
...
...
@@ -495,15 +495,19 @@ older tags and images are regularly removed from the Container Registry.
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/15398) in GitLab 12.8.
For a specific project, if you want to remove tags you no longer need,
you can create an expiration policy. When the policy is applied, tags matching the regex pattern are removed.
The underlying layers and images remain.
To delete the underlying layers and images no longer associated with any tags, Instance Administrators can use
[
garbage collection
](
../../../administration/packages/container_registry.md#removing-unused-layers-not-referenced-by-manifests
)
with the
`-m`
switch.
NOTE:
**Note:**
For GitLab.com, expiration policies are not available for projects created before GitLab 12.8.
For self-managed instances, expiration policies may be enabled by an admin in the
[
CI/CD Package Registry settings
](
./../../admin_area/settings/index.md#cicd
)
.
Note the inherent
[
risks involved
](
./index.md#use-with-external-container-registries
)
.
It is possible to create a per-project expiration policy, so that you can make sure that
older tags and images are regularly removed from the Container Registry.
The expiration policy algorithm starts by collecting all the tags for a given repository in a list,
then goes through a process of excluding tags from it until only the ones to be deleted remain:
...
...
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