ECIR (Container Image Registry) Documentation#308
Conversation
…fork and work from Ben Carpenter and suggestions for A Jackson.
|
Updated to include some of B Carpenter additional updates. |
BenjaminCarpenter480
left a comment
BenjaminCarpenter480
left a comment
There was a problem hiding this comment.
Looks good to me just some minor points for us to fix. I think worth another check from someone else as I have become quite familiar with a lot of the terms though/
…projects with a bit making different between types of project and working with to update robot section with coming soon notice
BenjaminCarpenter480
left a comment
BenjaminCarpenter480
left a comment
There was a problem hiding this comment.
This looks good to me, minor typo to be fixed
|
|
||
| User tokens can be accessed from the User Profile from the dropdown under your Username at the top right hand corner of the page. These will be needed to log into the registry from Docker and other container services. | ||
|
|
||
| {: class="border-img"} |
There was a problem hiding this comment.
This doesn't seem to be rendering quite right - at least not on GitHub, may be different in EIDF docs later which I'm less familiar with!
There was a problem hiding this comment.
Occurs a few times throughout all docs - I take this to mean this works just fine in the official docs pages.
There was a problem hiding this comment.
this is fixed when it is served via rendered pages with the Github action or via mkdocs.
|
|
||
| ECIR hosts public cache projects for commonly used images. If you use an image which is commonly pulled from public repositories, using a cache copy can reduce the impact on public services. | ||
|
|
||
| Using ECIR for pulling and storing images should help with quick deployment and access control of images for projects. Reducing overhead of EIDF Services pulling repeatedly from external registries. |
There was a problem hiding this comment.
images for projects, reducing overhead instead? Or just This reduces overhead ....
| * Nvidia NGC Registry [https://nvcr.io](https://catalog.ngc.nvidia.com/) - Project nvidia-cache | ||
| * Quay.io [https://quay.io](http://quay.io) - Project quay-cache | ||
|
|
||
| To use a cache project, the ECIR address and the project name should be pre-pending the name of the image, for example to pull the image, `nvidia/pytorch:25.05-py3` from the Nvidia (NVCR.io) registry, you would use: |
There was a problem hiding this comment.
Does this mean if I want to use an image from NVCR, instead of using docker pull nvcr.io/image_name I should pull from docker pull registry.eidf.ac.uk/nvidia-cache/image_name? Does that automatically add the NVCR image into the cache? Or does the image need to be pulled from NVCR, that adds it to the cache, and in the future I could pull from nvidia-cache?
It's not entirely clear to me how images get added to the cache, maybe this could be spelled out more clearly?
There was a problem hiding this comment.
added automatic into summary and what to prepend images with to use the proxies.
| {: class="border-img"} | ||
| *Missing SBOM Output Report* | ||
|
|
||
| Then you will have to click the folder next to the artifact name. |
… and wording in faq and index
BenjaminCarpenter480
left a comment
BenjaminCarpenter480
left a comment
There was a problem hiding this comment.
This looks good to me, addresses problems suggested!
3 participants
EIDF Documentation Pull Request
Description
Public version of the ECIR documentation added under the code collaboration heading in data services beside gitlab.
This contains work from A Grant, B Carpenter and suggestions from A Jackson.
This is the initial documentation to allow users to start with the Harbor registry in EIDF.
Type of change
Please delete options that are not relevant.
What has to be reviewed
Checklist