| skopeo-delete(1)() | skopeo-delete(1)() |
skopeo-delete - Mark the image-name for later deletion by the registry's garbage collector.
skopeo delete image-name
Mark image-name for deletion. To release the allocated disk space, you must login to the container registry server and execute the container registry garbage collector. E.g.,
/usr/bin/registry garbage-collect /etc/docker-distribution/registry/config.yml Note: sometimes the config.yml is stored in /etc/docker/registry/config.yml If you are running the container registry inside of a container you would execute something like: $ docker exec -it registry /usr/bin/registry garbage-collect /etc/docker-distribution/registry/config.yml
--authfile path
Path of the authentication file. Default is
${XDG_RUNTIME_DIR}/containers/auth.json, which is set using skopeo
login.
If the authorization state is not found there, $HOME/.docker/config.json is
checked, which is set using docker login.
--creds username[:password] for accessing the registry.
--cert-dir path Use certificates at path (*.crt, *.cert, *.key) to connect to the registry.
--tls-verify bool-value Require HTTPS and verify certificates when talking to container registries (defaults to true).
--no-creds bool-value Access the registry anonymously.
Additionally, the registry must allow deletions by setting REGISTRY_STORAGE_DELETE_ENABLED=true for the registry daemon.
--registry-token Bearer token for accessing the registry.
Mark image example/pause for deletion from the registry.example.com registry:
$ skopeo delete --force docker://registry.example.com/example/pause:latest
See above for additional details on using the command delete.
skopeo(1), skopeo-login(1), docker-login(1), containers-auth.json(5)
Antonio Murdaca runcom@redhat.com ⟨mailto:runcom@redhat.com⟩, Miloslav Trmac mitr@redhat.com ⟨mailto:mitr@redhat.com⟩, Jhon Honce jhonce@redhat.com ⟨mailto:jhonce@redhat.com⟩