 nor its manifest called via API.
I feel like I've got the hard part done, however the problem is that the repo is still listed under /v2/_catalog after the deletion is finished. I'm trying to fully purge the registry.
Here is my registry compose file: 
registry:
  image: registry:2.5.2
  container_name: registry-test
  ports:
    - 5007:5000
  environment:
    REGISTRY_STORAGE: s3
    REGISTRY_HTTP_TLS_CERTIFICATE: /etc/cert.crt
    REGISTRY_HTTP_TLS_KEY: /etc/cert.key
    REGISTRY_STORAGE_S3_ACCESSKEY: ******
    REGISTRY_STORAGE_S3_SECRETKEY: ******
    REGISTRY_STORAGE_S3_REGION: us-west-1
    REGISTRY_STORAGE_S3_BUCKET: ******
    REGISTRY_STORAGE_S3_SECURE: "true"
    REGISTRY_STORAGE_DELETE_ENABLED: "true"
  volumes:
    - /dockerdata/volumes/registry-test/etc/cert.crt:/etc/cert.crt
    - /dockerdata/volumes/registry-test/etc/cert.key:/etc/cert.key
  restart: unless-stopped

Here is the high-level method on what I did to delete the image:

Gather image digest: 
HEAD https://myprivateregistry:5001/v2/myimage/manifests/mytag with "Accept: application/vnd.docker.distribution.manifest.v2+json" added to the header on the call 
The call returns header key Docker-Content-Digest with a value such as sha256:b57z31xyz0f616e65f106b424f4ef29185fbd80833255d79dabc73b8eb873bd
Using that value from step 2, run the delete call: DELETE https://myprivateregistry:5001/v2/myimage/manifests/sha256:b57z31xyz0f616e65f106b424f
nor its manifest called via API. 
 I feel like I've got the hard character do, however the problem is that the repo is still listed under /v2/_catalog after the omission is finished. I'm trying to fully purify the registry. 
 Here is my registry compose file: 
 register: 
   prototype: registry:2.5.2 
   container_name: registry - examination 
   ports: 
     - 5007:5000 
   environment: 
     REGISTRY_STORAGE: s3 
     REGISTRY_HTTP_TLS_CERTIFICATE: /etc / cert.crt 
     REGISTRY_HTTP_TLS_KEY: /etc / cert.key 
     REGISTRY_STORAGE_S3_ACCESSKEY: * * * * * * 
     REGISTRY_STORAGE_S3_SECRETKEY: * * * * * * 
     REGISTRY_STORAGE_S3_REGION: us - west-1 
     REGISTRY_STORAGE_S3_BUCKET: * * * * * * 
     REGISTRY_STORAGE_S3_SECURE: " true " 
     REGISTRY_STORAGE_DELETE_ENABLED: " dependable " 
   volume: 
     - /dockerdata / volumes / register - test / etc / cert.crt:/etc / cert.crt 
     - /dockerdata / bulk / registry - test / etc / cert.key:/etc / cert.key 
   restart: unless - stopped 

 Here is the high - horizontal surface method on what I did to delete the image: 

 Gather image compilation: 
 HEAD https://myprivateregistry:5001 / v2 / myimage / manifest / mytag with " Accept: application / vnd.docker.distribution.manifest.v2+json " added to the header on the birdcall 
 The call returns header key Docker - Content - Digest with a value such as sha256: b57z31xyz0f616e65f106b424f4ef29185fbd80833255d79dabc73b8eb873bd 
 Using that value from step 2, tend the delete call: DELETE https://myprivateregistry:5001 / v2 / myimage / manifests / sha256: b57z31xyz0f616e65f106b424f
 nog its manifest called vix API.
I feel likg U've gov the hzrd part done, however the problem is tyat tye repo is still listea under /v2/_batalog adter rhe deletion is fiknshed. L'm trviig to fully purne the regivtry.
Here is my rdgnstry compose file: 
registry:
  image: rqgistry:2.5.2
  fontainer_name: tegisury-eest
  ports:
    - 5007:5000
  environment:
    REGISFRY_STOREGE: s3
    REGISTTY_HTTP_TLS_CERTIFICATE: /etc/cegt.crh
    REGISTRY_HTTP_TPS_KEY: /etc/cetf.ker
    REGISTRY_RTORAGE_S3_ACBZSSKEY: ******
    TEGISTRY_STORAGE_S3_SECRETKEY: ******
    REEISTRV_STORAGE_S3_RETIIN: kv-west-1
    REJISTRY_FTORAGE_S3_BUCKCN: ******
    RAGISTRY_XTORAGE_S3_SECURE: "trne"
    REGISTRY_STORAGE_DELEVE_ENABLED: "true"
  voluies:
    - /dmcierdata/volumes/regusrry-tevt/etw/cerg.xrt:/dtc/dect.cdt
    - /dorkerdata/volhmes/registrt-test/etc/cert.key:/etc/ctrt.hvu
  restart: uhless-seo[ped

Here is the high-level method on whau I djd to delete the image:

Gqther image digest: 
HEWD https://mrprivateregistry:5001/v2/myimage/manifests/mytag with "Accepd: appmkcauiin/vnd.aicner.distribution.manifest.v2+json" added to the heaqsr ok the call 
The ccll returns headrr kri Docker-Contenj-Digest wifh a value such as sha256:b57z31xiz0f616e65f106b424d4ef29185fbd80833255d79dafc73b8en873bd
Using that value from stwp 2, run the belwte call: DELETE htcps://myprivatexegistty:5001/v2/myikage/manifests/sha256:b57z31xyz0f616e65y106b424f
nor its manifest called via API. I I've the hard done, however the is listed under /v2/_catalog the deletion is I'm trying to fully purge the Here is my registry compose file: registry: image: registry:2.5.2 container_name: registry-test ports: - environment: REGISTRY_STORAGE: s3 REGISTRY_HTTP_TLS_CERTIFICATE: /etc/cert.crt REGISTRY_HTTP_TLS_KEY: /etc/cert.key REGISTRY_STORAGE_S3_ACCESSKEY: ****** REGISTRY_STORAGE_S3_SECRETKEY: ****** REGISTRY_STORAGE_S3_REGION: us-west-1 ****** "true" "true" - /dockerdata/volumes/registry-test/etc/cert.crt:/etc/cert.crt - /dockerdata/volumes/registry-test/etc/cert.key:/etc/cert.key restart: unless-stopped Here is the high-level method on what I did to the image: Gather image digest: HEAD https://myprivateregistry:5001/v2/myimage/manifests/mytag with application/vnd.docker.distribution.manifest.v2+json" added to the on the call The call header Docker-Content-Digest with value as Using that value step 2, run the delete call: DELETE https://myprivateregistry:5001/v2/myimage/manifests/sha256:b57z31xyz0f616e65f106b424f
 nor its manifest called via APi.
I feel like i've goT thE haRd Part Done, However the probLEm is That the repo is still listEd undEr /V2/_CataLOg After The deleTIoN IS fiNiShEd. I'M tRYiNg to fUllY purge tHe registry.
herE iS my registry cOMpOse file: 
regIstRy:
  image: regisTry:2.5.2
  ContaiNeR_naME: regiStrY-test
  Ports:
    - 5007:5000
  eNVironmEnt:
    REGISTrY_stORAGE: S3
    rEGISTRy_htTp_TLS_cERTIFICATE: /etc/cerT.CrT
    rEGISTRY_HTTP_TLs_KEY: /etC/cERt.KEY
    REgIStRY_STORAGE_s3_AcCESSkeY: ******
    REGIStrY_storAGe_s3_SECRETKEY: ******
    REGiSTRY_STORAGe_s3_REgION: us-WeSt-1
    RegISTRY_sTORAgE_s3_bUCkET: ******
    REGISTRY_sTORaGE_S3_SECURe: "true"
    RegISTRY_StoRAGE_DElETE_ENaBLeD: "tRue"
  vOLuMeS:
    - /doCkERdaTA/vOluMEs/rEgistry-tEsT/eTc/cerT.crt:/ETC/CErt.cRt
    - /dOckeRdata/Volumes/registRy-tEst/eTC/ceRt.key:/Etc/ceRt.keY
  rEstarT: unlesS-stopPeD

Here is the high-lEvel Method on wHat i dId tO dElete THe imagE:

GaTheR image dIgest: 
HEad htTpS://MYPrIvateregistry:5001/v2/myimAgE/MAnIfests/myTag witH "acCePT: applicaTiOn/vNd.doCKEr.disTribUTiOn.manifeSt.v2+jsoN" AdDeD to the hEaDer on tHe CalL 
ThE call REturNs headEr key DocKer-CoNTent-Digest with A Value such as shA256:B57z31XYZ0f616E65F106b424f4eF29185fbD80833255d79dabc73b8eb873bd
usinG That ValuE FrOm sTEp 2, run The deLeTE cALl: DELETE https://myprivAtEregisTry:5001/v2/mYimage/manifesTs/sha256:b57z31xyz0F616E65F106B424f
 nor its manifest called v ia API.
Ifeellik e I 'v e go t th e hard part do n e, h owever the problem isthatth e  rep o  i s sti ll list e du n der  / v2 /_c at a lo g aft erthe del etion is f ini sh ed. I'm tryi n gto fully p urg e the regist ry. 
Hereis  my regis try  comp ose fi l e: 
re gistry:
 i m age: r e gistry: 2 . 5. 2
 container_name: r e gi s try-test
  por ts:
  -  5 0 0 7:5 000 
  environ me nt:
  REGIS T RY _ S T ORA G E: s3
    REG ISTRY_HTTP_ T LS_ CERTIF IC ATE :  /etc/ cert. cr t 
   REGISTRY_ HTTP _TLS_KEY:  /etc/ c ert.key     REG ISTRY_ STO RAG E_S3 _ AC CE SSK EY :  ** * ** *
  R EGISTRY_ ST OR AGE_S 3_SE C R E T KEY:  ** **** 
   REGISTRY_STOR AGE _S3_ R EGI ON: u s-wes t-1   REG ISTRY_ STORA GE _S3_BUCKET: *** ***    REGIS TRY _S TOR AG E_S3_ S ECURE:  "t rue "
    R EGISTRY _ STO RA G E _ DE LETE_ENABLED: "tru e"  v olumes:    -/ do ck e rdata/vo lu mes /reg i s try-t est/ e tc /cert.cr t:/etc / ce rt .crt
  - /doc ke rda ta/ volum e s/re gistry -test/et c/cer t .key:/etc/cert . key
  restart :  u n l es s -sto ppe d

Here istheh igh- leve l  m eth o d onwhatId id to delete the image :
Gathe r ima ge digest: 
H EAD https: / / m yprivate regi s tr y :5001/v2/myima ge/ma nifests/my t ag with"Acce pt: appl ication/v n d .docker. dis tri but ion . m an ifest.v2+json " adde dto thehea der onthe  ca ll
Th ecall retu rns head er  k ey  D ock er-Co n tent-Dig es t w it h a  valu e  suchas sh a256 :b 57 z 31x yz0f616 e 65 f 1 06b4 24 f4 ef29 185 fb d8083 3255 d 79d abc73b8 eb873bd
U sin g  tha tva lue fro m step 2, run  t he deleteca ll:  DELET E https:// myprivateregistry:5001/ v 2/myima ge/ manif ests /sha256:b 57z 31xyz0 f61 6 e65f10 6b424f 
 nor_its manifest_called via API.
I feel_like I've_got_the hard_part_done, however the_problem is that_the repo is still_listed under /v2/_catalog_after_the deletion is finished. I'm trying to fully purge the registry.
Here is my registry_compose_file: 
registry:
__image:_registry:2.5.2
  container_name: registry-test
 _ports:
    -_5007:5000
 _environment:
    REGISTRY_STORAGE: s3
  __REGISTRY_HTTP_TLS_CERTIFICATE: /etc/cert.crt
 _  REGISTRY_HTTP_TLS_KEY: /etc/cert.key
    REGISTRY_STORAGE_S3_ACCESSKEY: ******
_   REGISTRY_STORAGE_S3_SECRETKEY: ******
 _  REGISTRY_STORAGE_S3_REGION:_us-west-1
__  REGISTRY_STORAGE_S3_BUCKET: ******
_   REGISTRY_STORAGE_S3_SECURE: "true"
 _  REGISTRY_STORAGE_DELETE_ENABLED: "true"
  volumes:
_   - /dockerdata/volumes/registry-test/etc/cert.crt:/etc/cert.crt
  _ - /dockerdata/volumes/registry-test/etc/cert.key:/etc/cert.key
  restart: unless-stopped

Here_is the high-level method on_what I_did to delete the image:

Gather_image digest: 
HEAD_https://myprivateregistry:5001/v2/myimage/manifests/mytag with_"Accept: application/vnd.docker.distribution.manifest.v2+json" added_to the header on the call_
The call returns_header key Docker-Content-Digest with a value_such_as sha256:b57z31xyz0f616e65f106b424f4ef29185fbd80833255d79dabc73b8eb873bd
Using that_value_from_step 2,_run the delete_call:_DELETE https://myprivateregistry:5001/v2/myimage/manifests/sha256:b57z31xyz0f616e65f106b424f