1skopeo-delete(1)() skopeo-delete(1)()
2
3
4
6 skopeo-delete - Mark image-name for deletion.
7
8
10 skopeo delete image-name
11
12
13 Mark image-name for deletion. To release the allocated disk space, you
14 must login to the container registry server and execute the container
15 registry garbage collector. E.g.,
16
17
18 /usr/bin/registry garbage-collect /etc/docker-distribution/registry/config.yml
19
20 Note: sometimes the config.yml is stored in /etc/docker/registry/config.yml
21
22 If you are running the container registry inside of a container you would execute something like:
23
24 $ docker exec -it registry /usr/bin/registry garbage-collect /etc/docker-distribution/registry/config.yml
25
26
27
28
29 --authfile path
30
31
32 Path of the authentication file. Default is ${XDG_RUNTIME_DIR}/contain‐
33 ers/auth.json, which is set using podman login.
34 If the authorization state is not found there, $HOME/.docker/con‐
35 fig.json is checked, which is set using docker login.
36
37
38 --creds username[:password] for accessing the registry
39
40
41 --cert-dir path Use certificates at path (*.crt, *.cert, *.key) to con‐
42 nect to the registry
43
44
45 --tls-verify bool-value Require HTTPS and verify certificates when
46 talking to container registries (defaults to true)
47
48
49 --no-creds bool-value Access the registry anonymously.
50
51
52 Additionally, the registry must allow deletions by setting REG‐
53 ISTRY_STORAGE_DELETE_ENABLED=true for the registry daemon.
54
55
57 Mark image example/pause for deletion from the registry.example.com
58 registry:
59
60
61 $ skopeo delete --force docker://registry.example.com/example/pause:latest
62
63
64
65 See above for additional details on using the command delete.
66
67
69 skopeo(1), podman-login(1), docker-login(1)
70
71
73 Antonio Murdaca runcom@redhat.com ⟨mailto:runcom@redhat.com⟩, Miloslav
74 Trmac mitr@redhat.com ⟨mailto:mitr@redhat.com⟩, Jhon Honce jhonce@red‐
75 hat.com ⟨mailto:jhonce@redhat.com⟩
76
77
78
79 skopeo-delete(1)()