Open pierrepo opened 4 years ago
@pierrepo that is when using Plasma, but not with tljh-repo2docker
alone?
If so it might be related to how the PATH
is set up with the entrypoint:
Oups I raise the issue in the wrong repo @jtpio Do you know how to move an issue to another repo (Plasma's one)?
If so it might be related to how the PATH is set up with the entrypoint: https://github.com/plasmabio/plasma/blob/7883a6a1266b69ab49f353bdf9974be408bf0709/tljh-plasma/tljh_plasma/entrypoint/entrypoint.sh
Thanks! I guess the following extra lines should do the trick:
export PATH=${PATH//"/srv/conda/envs/notebook/bin"/"/srv/conda/envs/notebook/bin:/srv/conda/condabin:/srv/conda/bin:/srv/npm/bin"}
chown -R ${NB_USER}:${NB_USER} /srv/conda
Binder allows installation of additional packages within the actual environement by exposing the conda binary and the related base environment. For instance:
leads to
This is very convenient to install extra package we might have forgot (albeit not a very good practice :thinking:):
With tljh-repo2docker, it seems that the conda binary is not accessible:
leads to
indeed, conda binary is in
/srv/conda/bin/
that is not isPATH
:However, it also appears that the base conda environment is not writable to the current user:
gives
Would it be possible to make the conda bin directory available in
PATH
and the base environment writable?