-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add rclone to conda-requirements.txt #19
Conversation
@minrk I also would like to add the associated configuration files but I am not sure where to add them. |
what files should go where? That probably belongs in the Dockerfile |
that is what I thought but we also need to have the user credentials for our buckets. Below is what I have put in
|
it shouldn't need the access key or profile with env_auth = true, so I think the same file works for everyone. This config worked for me:
|
then I can add it in the repo and docker file, right? |
We'll still need to copy it into home in an initContainer here, so might as well create it there, rather than needing to update the image. I can do that, if you want. |
Out of curiosity, why can't we copy it in the docker file (and have the config file in https://github.com/destination-earth/DestinE_ESA_GFTS/tree/main/jupyterhub/images/user) e.g. updating the current Dockerfile with something like:
|
$HOME is a mounted volume in the container, it doesn't come from the image. Files in $HOME in the image will not be available in the container. That would work if we had no persistence of your home directory. |
Ok! I got it. just to understand: in here, would you generate the config file on the fly? |
yes, that's right |
Ok. then let me try... |
No description provided.