Download the Image Mastering API v2.0 (IMAPIv2.0) for Windows XP. Standard Edition (32-bit x86) Microsoft Windows. Gcr.io/google_containers/hyperkube:v0.21.2ĭisk space used: 1.Description of the Image Mastering API v2.0. REGISTRY_STORAGE_FILESYSTEM_ROOTDIRECTORY="/mnt/three/docker-registry/registry-data"įind $REGISTRY_STORAGE_FILESYSTEM_ROOTDIRECTORY -print | \Įcho "Number of images: `cat /tmp/a2 | awk `"Įcho "Disk space used: `du -hs $REGISTRY_STORAGE_FILESYSTEM_ROOTDIRECTORY`" # if REGISTRY_STORAGE_FILESYSTEM_ROOTDIRECTORY is mounted on your system Let me know of any changes you would make, thanks. It works on any of my systems that has the REGISTRY_STORAGE_FILESYSTEM_ROOTDIRECTORY mounted. I wrote a script, named view-private-registry to search registry V2 REGISTRY_STORAGE_FILESYSTEM_ROOTDIRECTORY. I started with registry V2 from the marketing better security and performance. I do not want to rip and replace V2 with V1 even though V1 works and has several tools that work with V1 including search and delete. Don't even think about deleting an image. Registry V2 is like dropping images into a black bag, hope you remember what you dropped in and what you named the image. You can list your image by tag or by the image name itself as mentioned in task number 8 in this documentation.ĭocker registry search functionality v2 is not supported at the time of this writing. So there's no search endpoint in the v2 registry yet. It is worth looking at this particular Github issue about the v2 registry for a deep-dive into a recent discussion on the state of the v2 registry, as well as some discussion about where they've been taking it. It took me some time and serious reading to understand the dichotomy here between the registries. It's even written in a completely different language (v1 was a Python project, whereas v2 uses Go, which is more in line with the rest of the Docker projects). It's important here to note that the v2 registry is a completely different project than the v1 registry. You can check the source itself for the route endpoints, and you'll see that most of the API endpoints involve simple operations like uploading and tagging, but no implementation yet of the search endpoint. The problem here is that the new v2 Docker registry doesn't support that particular endpoint yet, as of this question and answer. UPDATE (12 November 2015): The API endpoints still do not yet exist and are not yet in the Docker Registry roadmap. UPDATE (14 April 2016): Still not here in the distribution roadmap, but here is a particular issue about search.
0 kommentar(er)
