we have an external docker registry (independent of gitlab) which we are using the host the Renku images.
The images are build in gitlab using an independent docker-in-docker container, and being checked into the registry correctly.
`7511508: digest: sha256:0b891f1b72a52a433f9fbb033ed9905b83156cafb19dde2cde95ea3e739267e0 size: 7201 ` ` Cleaning up project directory and file based variables
00:00` `Job succeeded`
However, renku seems to be querying gitlab for the images and getting no {"error":"404 Not Found"}
.
/api/v4/projects/20278/registry
and getting
{"error":"404 Not Found"}
How to solve?
@diarmuidcire the current version of Renku is strongly tied to a single Gitlab instance - as you must have noticed. All Renku projects are just Gitlab projects and all Docker images used in Renku sessions are built by Gitlab CI/CD pipelines and stored on the Gitlab registry. Currently there is no easy way for Renku to authenticate with a registry that is not tied to the Gitlab and check for images there.
An alternative that may (or may not) be suitable is to “pin” the image you wish to use. This image has to be public and this means that when you make changes to your code the pinned image will not be automatically updated. If the image is pinned then it is always used for that session. The image that you pin to the project can be hosted on any registry as long as that image is public.
We are working on a revamped version of Renku that will make this possible. But even there this feature is still just in early stages of scoping and planning.
understood. Im using gitlab registry now anway. So Im sorted.