Starting session fails on git-clone init container
See original GitHub issueI have deployed renku using helm in an on prem cluster. All the components seems to work fine, the only problem that I am facing out is that when I am trying to launch a new session, using a custom image, made from a notebook template, the git-clone container is not able to clone the repo.
It complains that :
No git repo found, setting up repo and cloning into https://<domain>/gitlab
I think that it should use https://<domain>/gitlab/path/to/.git
to clone the repo in which I have the template or I am missing something ?
My renku chart version is the 0.12.3
Thank you very much for your help and for developing this great project.
Issue Analytics
- State:
- Created a year ago
- Comments:16 (8 by maintainers)
Top Results From Across the Web
[nginx] Init container fails to clone the git repo #13626 - GitHub
Push config to repo, reconcile it with flux. helmrelease will stay in a CrashLoopBackOff. Are you using any custom parameters or values? helmrelease...
Read more >Gitsync in kubernetes not deploying properly - Stack Overflow
I have already created secret using known_hosts and ssh. However I face following error. "msg"="failed to sync repo, aborting" "error"="error ...
Read more >Troubleshooting Git - GitLab Docs
git clone over HTTP fails with transfer closed with outstanding read data remaining error · If this error occurs when cloning a large...
Read more >Deployment fails after a while - initContainer and git clone
Now I'm changing that to an apache install with PHP 7.4 and trying to clone from my repo to it so instead of...
Read more >InitContainer - :: Kubernetes From Scratch - Ansil
Incase of InitContainer failure , Pod startup will fail and never start other containers. We can specify more than one initcontainer if needed....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Could you try redeploying and set this value:
It turns off the network policy that is configured for the notebook session pods. It might be that something funny is happening there.
Thank you @rokroskar and @olevski for your support. Setting
notebooks.amalthea.networkPolicies.enabled=false
solve the problem.