Skip to content

move environment to separate directory#674

Open
rokroskar wants to merge 2 commits intoi4Ds:mainfrom
rokroskar:main
Open

move environment to separate directory#674
rokroskar wants to merge 2 commits intoi4Ds:mainfrom
rokroskar:main

Conversation

@rokroskar
Copy link
Copy Markdown

To build the image automatically in renkulab, it's cleaner to have the directory separated from the project.toml since otherwise the buildpack either assumes poetry or that the local package is being installed.

See an example project which is a copy of the original. The Jupyter launcher is built automatically by renkulab from a fork which includes the changes proposed here. See the renku docs for more info on building images from code repositories.

@anawas
Copy link
Copy Markdown
Collaborator

anawas commented Dec 19, 2025

Hi rokroskar
I appreciate your input. I tried to run Karabo on Renkulab many times. We will come back to your PR asap. For the moment we have other priorities. I keep this PR open though.

@rokroskar
Copy link
Copy Markdown
Author

Hi @anawas - I've also looked at the image you build and there are a few problems that make it difficult to use as an interactive workspace image:

  1. it only contains the root user - it should ideally have a non-root user with a known uid/gid. The newer (Noble) ubuntu images include the ubuntu user already, so you might just need to switch to a version of the nvidia base images that use that version if it is compatible with the rest of your stack. Otherwise you can simply add a karabo user somewhere in the build.
  2. Related to the above, I can run it with user 1000, but then the HOME variable is not set, which is expected by a number of systems (e.g. jupyter)
  3. The image is pretty large. The images built automatically on Renku ends up being much smaller - you may want to check where the Dockerfile you have might be a bit inefficient.

I have a working launcher that gets around some of these problems if you'd like to have a look!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants