.nh
.TH skopeo-delete(1)
.SH NAME
.PP
skopeo-delete - Mark the \fIimage-name\fP for later deletion by the registry's garbage collector.

.SH SYNOPSIS
.PP
\fBskopeo delete\fP [\fIoptions\fP] \fIimage-name\fP

.SH DESCRIPTION
.PP
Mark \fIimage-name\fP for deletion.
The effect of this is registry-specific; many registries don’t support this operation, or don’t allow it in some circumstances / configurations.

.PP
\fBWARNING\fP: If \fIimage-name\fP contains a digest, this affects the referenced manifest, and may delete all tags (within the current repository?) pointing to that manifest.

.PP
\fBWARNING\fP: If \fIimage-name\fP contains a tag (but not a digest), in the current version of Skopeo this resolves the tag into a digest, and then deletes the manifest by digest, as described above (possibly deleting all tags pointing to that manifest, not just the provided tag). This behavior may change in the future.

.PP
When using the github.com/distribution/distribution registry server:
To release the allocated disk space, you must login to the container registry server and execute the container registry garbage collector. E.g.,

.PP
.RS

.nf
/usr/bin/registry garbage-collect /etc/docker-distribution/registry/config.yml

.fi
.RE

.PP
Note: sometimes the config.yml is stored in /etc/docker/registry/config.yml

.PP
If you are running the container registry inside of a container you would execute something like:

.PP
.RS

.nf
$ docker exec -it registry /usr/bin/registry garbage-collect /etc/docker-distribution/registry/config.yml

.fi
.RE

.SH OPTIONS
.PP
See also skopeo(1) for options placed before the subcommand name.

.PP
\fB--authfile\fP \fIpath\fP

.PP
Path of the authentication file. Default is ${XDG_RUNTIME_DIR}/containers/auth.json, which is set using \fB\fCskopeo login\fR\&.
If the authorization state is not found there, $HOME/.docker/config.json is checked, which is set using \fB\fCdocker login\fR\&.

.PP
\fB--creds\fP \fIusername[:password]\fP

.PP
Credentials for accessing the registry.

.PP
\fB--cert-dir\fP \fIpath\fP

.PP
Use certificates at \fIpath\fP (*.crt, *.cert, *.key) to connect to the registry.

.PP
\fB--daemon-host\fP \fIhost\fP

.PP
Use docker daemon host at \fIhost\fP (\fB\fCdocker-daemon:\fR transport only)

.PP
\fB--help\fP, \fB-h\fP

.PP
Print usage statement

.PP
\fB--no-creds\fP

.PP
Access the registry anonymously.

.PP
Additionally, the registry must allow deletions by setting \fB\fCREGISTRY_STORAGE_DELETE_ENABLED=true\fR for the registry daemon.

.PP
\fB--registry-token\fP \fItoken\fP

.PP
Bearer token for accessing the registry.

.PP
\fB--retry-times\fP

.PP
The number of times to retry. Retry wait time will be exponentially increased based on the number of failed attempts.

.PP
\fB--shared-blob-dir\fP \fIdirectory\fP

.PP
Directory to use to share blobs across OCI repositories.

.PP
\fB--tls-verify\fP=\fIbool\fP

.PP
Require HTTPS and verify certificates when talking to the container registry or daemon. Default to registry.conf setting.

.PP
\fB--username\fP

.PP
The username to access the registry.

.PP
\fB--password\fP

.PP
The password to access the registry.

.SH EXAMPLES
.PP
Mark image example/pause for deletion from the registry.example.com registry:

.PP
.RS

.nf
$ skopeo delete docker://registry.example.com/example/pause:latest

.fi
.RE

.PP
See above for additional details on using the command \fBdelete\fP\&.

.SH SEE ALSO
.PP
skopeo(1), skopeo-login(1), docker-login(1), containers-auth.json(5)

.SH AUTHORS
.PP
Antonio Murdaca runcom@redhat.com
\[la]mailto:runcom@redhat.com\[ra], Miloslav Trmac mitr@redhat.com
\[la]mailto:mitr@redhat.com\[ra], Jhon Honce jhonce@redhat.com
\[la]mailto:jhonce@redhat.com\[ra]