Package seemd no installed after Renku transition

1

I am still struggling with the Renku transition from Legacy to 2.0.

I tried to clone the project on Github and make the link to the new repository, but it seems that python packages are not installed when I start a Renku session, as it used to be (using Renku Legacy). The package pygimli for example seems not to be installed. Did I miss something for the Renku transition?

One of my project is public (but I also tried on other private projects and I seem to have the same issue). Here is the link to my public project:

Thanks!

1 Like
2

I think the best option for your projects is to set them up so that the images are built as GitHub actions. To do this, you need to create a GitHub workflow and put it in the .github/workflows/ folder.

I have forked the repository for your project and made this change. You can see the workflow here 4pm-pji/.github/workflows/build.yml at main · ciyer/4pm-pji · GitHub .

In Renku, you will need to create a session launcher that references the image built in GitHub.

  • Container image:ghcr.io/[namespace]/[project]:[sha]
  • Default URL path:/lab
  • Port:8888
  • Working directory:/home/jovyan/work
  • Mount directory:/home/jovyan/work
  • UID:1000
  • GID:1000
  • Command: ["sh","-c"]
  • Args:
["jupyter server --ServerApp.ip=$RENKU_SESSION_IP --ServerApp.port=$RENKU_SESSION_PORT --ServerApp.allow_origin=* --ServerApp.base_url=$RENKU_BASE_URL_PATH --ServerApp.root_dir=$RENKU_WORKING_DIR --ServerApp.allow_remote_access=True --ContentsManager.allow_hidden=True --ServerApp.token=\"\" --ServerApp.password=\"\""]

The reference used in the Container image section can be obtained by following the Package link on the main page of the repository.

image
image728Ă—240 6.88 KB

To see an example, look at the pji-test [ghcr] launcher on this Renku project: Reproducible Data Science | Open Research | Renku

Please feel free to ask a follow-up if any part of these instructions are unclear or you require more details.

3

Dear @cramakri,

Thank you very much for your time andyour project test, that I could try successfully.
But I however do not managed yet to reproduce it in my own project. I tried to copy excatly what you did (except of the commit id in the container image).
But I did not ahve to chane anything from the build.yml file, right? 4pm-pji/.github/workflows/build.yml at main · ColineMollaret/4pm-pji · GitHub

The is an "Error in Session” while I attempt to launch the Session. Can you see it on my project? Otherwise I could copy-paste the logs here?

4

@colinem The correct container image reference is ghcr.io/colinemollaret/4pm-pji:sha-6173fb5 not ghcr.io/coline.mollaret/4pm-pji:sha-6173fb5 (there is no extra dot .)

You can view the correct image reference on the GitHub packages page → Package 4pm-pji · GitHub

2 Likes
5

I added a launcher that uses the image reference specified by @leafty, and it works for me, so that should fix the issue you were having.

I forgot to mention in my original post, that this approach will not work for private projects until version 2.9.0 is deployed: This is currently scheduled for Wed (Oct. 15th, 2025). So, starting next week, you should be able to use the same strategy to migrate your private projects.

6

Many thanks @cramakri and @leafty ! And great to know that I can use the same strategy very soon for my private projects!

7

Dear @cramakri and @leafty, I am trying to make the link between Github private repositories and renku provate projects, but do not manage successfully for the moment.

On the Renku Code Repositories section, it says:This repository does not exist or you do not have access to it.
Is step of accessibility different for public and private project, or do I miss something else? Thanks

8

For a private repository, there is an additional step that you need to do, but it is unfortunately not well communicated in the UI at the moment.

You need to go to the Integrations page Reproducible Data Science | Open Research | Renku and make sure that Renku has access to the private repo. Click on the Update settings for GitHub.com button.

image
image1224Ă—882 77.7 KB

This will take you to a page on GitHub, where you can select which of your repos Renku has access to.

The UX around this should be better, and we should make some improvements around this.

9

Thanks @cramakri I did it now and the code repository is solved.
But my (Docker) image is still inaccessible. I tried several things but feel a bit lost. I created in github a workflow as an Action, and copied there the build.yml (which works for my public project). But as it is now a private project, it is maybe not the way to go?

10

There is a misconfiguration on our side that is preventing private images hosted on GitHub from working. We are working on it right now and will let you know as soon as it has been fixed.

1 Like
11

We have fixed the issues, and you should be able to get it to work now.

You need to go to the same integrations page linked above and connect the “Github Container Registry” integration

image
image984Ă—380 23.9 KB

If you see a message that this integration is “Not connected” for you, then you should click the Connect button to remedy that. After that, your docker image should be accessible.

12

@cramakri Thanks! I did this Connect /Integration step. But this does not solve my problem. I am unsure what step I miss: the image is still inaccessible.

I am not sure if I am only lost in the procedure Notion or if I miss something.

13

Hello @colinem with “inaccessible” you mean Renku is showing you a red pill? When I use my private image, I see this:

Selection_010
Selection_010987Ă—222 17.4 KB

The image name is ghcr.io/eikek/privim:latest in my case. It should be analogous to public images - you need to go through the setup “connecting to the GitHub image registry” first. Note that this is a separate one than used by the code repositories.

14

Hello @colinem , if you’re connected to the GitHub integration, the image should show up as available regardless of any misconfigured “Advanced” or “Docker” settings – the Container Image URL should be enough.

If you still see the red badge next to the image, you could do the following steps:

  1. Go to the Integrations page (click on the user icon on the top-right and then on “Integrations”) and check that you are connected to Github Container Registry. Mind that there is another integration for Github called GitHub.com that is used only for the repos and isn’t relevant for checking the images served by ghcr.io

  2. Try to click on the “Reconnect” button (or “Disconnect” and then “Connect”) and be sure the integration shows again the green badge next to the status.

  3. If your image is still marked as red, the Container Image URL might be wrong. To verify that, you could try to docker pull from your laptop and see if it works.

If these steps don’t work, we could organize a call together to give it a try together and see what’s broken.

15

Hi @eike and @lorenzo
Thanks for your help. Yes by unaccessible, I mean that it appears red.

image
image483Ă—269 15.8 KB

I did the integrations, and well noticed both GitHub.com and Girthub Containder Registry windows. Both appears Connected in green.

I was not able to verify the Containder Image URL with docker pull.
I would be happy if we can organize a call.