-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error in deleting repository in a private registry V2 #1573
Comments
you can try to add REGISTRY_STORAGE_DELETE_ENABLED=true when start the registry |
@ybshen I am sorry if this sounds too simple, but could you please specify how or where do we add that
|
@bhanushrestha See https://docs.docker.com/registry/configuration/ for details. But yes, REGISTRY_STORAGE_DELETE_ENABLED would be an environment variable that you would pass via the -e flag to docker run. |
@jheiss Sorry, I might miss. But I didn't found the variables |
The registry accepts configuration settings either via a file or via environment variables. So the environment variable storage:
delete:
enabled: true |
When I try to add the environment variable into my docker-compose.yaml it never seems to respond.
Changing it to equals failed as well as changing it to the number 1. It also would not work without quotes for text.
|
@sosensible Did you try deleting image after enabling that environment variable? https://docs.docker.com/registry/spec/api/#deleting-an-image |
I just went through the same issue and want to confirm that the solution suggested about enabling that environment variable in the config file works. |
This is because you are using a map value instead of a list which the correct format for docker compose. This is the working version: environment:
- REGISTRY_STORAGE_DELETE_ENABLED=true |
I would like to know the status of the delete operation implementation in the API v2 of docker registry.
I am able to get information up to manifest reference but when I try the delete operation I obtain:
curl -v --cacert /usr/local/share/ca-certificates/ca.crt -u 'user:pwd' -X GET https://hostname/v2/name/manifests/reference
... (the output report digest information)
curl -v --cacert /usr/local/share/ca-certificates/ca.crt -u 'user:pwd' -X DELETE https://hostname/v2/name/manifests/reference
...
{"errors":[{"code":"UNSUPPORTED","message":"The operation is unsupported."}]}
The text was updated successfully, but these errors were encountered: