cchwala
commented
1 year ago From the mybinder docs I would say that it is better to use the start file that is run just before the user sessions starts. The postBuild is ran when the container is built, which, in our case, is now done from the separate env repository, where we actually do not yet have the submodules available. Hence, my hope would be to run the start script from our code repo directly when a new binder instance is launched.
From the docs for the start file
A script that can contain simple commands to be run at runtime (as an ENTRYPOINT to the docker container). If you want this to be a shell script, make sure the first line is #!/bin/bash. The last line must be exec "$@" or equivalent.
Use this to set environment variables that software installed in your container expects to be set. This script is executed each time your binder is started and should at most take a few seconds to run.
overeem11
Sub-modules are not installed, they are only a code-clone of another repository into the sandbox project. In order to make this usable in notebooks, there is a need to add the path to each of the sub-module in an automatic way to the project. This may be realized by using the postBuild process.