Ask quick dev questions about mybinder.org, BinderHub, and repo2docker. Use discourse.jupyter.org for user questions, support, and discussion.
minrk on master
make cryptono optional disable… Merge pull request #2172 from m… (compare)
minrk on master
Deploy cryptnono cryptnono (ht… Merge pull request #2171 from y… (compare)
sgibson91 on 2171
sgibson91 on 2171
Deploy cryptnono cryptnono (ht… Merge df295d999c603f7ac299e148e… (compare)
choldgraf on master
Add supporters page (#262) (compare)
Hi,
I am having an issue with git-lfs and repo2docker . I added a git-lfs pull
command in the post-build command of my repo.
When executed on binder, the git-lfs pull works 🎉. However, when I execute it locally via repo2docker, I get an error :
batch request: Warning: Permanently added the ECDSA host key for IP address '140.82.121.4' to the list of known hosts.
git@github.com: Permission denied (publickey).: exit status 255
error: failed to fetch some objects from 'https://github.com/adrienpacifico/python_data_science.git/info/lfs'
Does someone know why?
Hi all, trying to build a repository for our library : pyAgrum (https://gitlab.com/agrumery/aGrUM), I received this message :
Sorry, agrumery%2FaGrUM/0.22.9 has been temporarily disabled from launching. Please contact admins for more info!
Sorry if we have unintentionally done something wrong but without more info, I cannot fix the problem ... So, how to contact admins for more info ? :-)
Thanks,
jupyter nbclassic
or jupyter lab
directly, without using jupyter-server-proxy
start
script: exec jupyter nbclassic --ip 0.0.0.0 "${@:3}"
2022-04-25T12:00:31Z [Normal] Started container notebook
Spawn failed: Server at http://10.0.10.47:8888/user/jtpio-4e9a3d435-c4150c10abbb1d7-g4vsup0y/ didn't respond in 30 seconds
Launch attempt 2 failed, retrying...
Server requested
repo2docker-entrypoint
based on the git history: https://github.com/jupyterhub/repo2docker/commits/main/repo2docker/buildpacks/repo2docker-entrypoint
using the following in the
start
script:exec jupyter nbclassic --ip 0.0.0.0 "${@:3}"
OK so after trying a couple of different combinations, the following command seems to be working on Binder: exec jupyter nbclassic "${@:4}"
while locally with jupyter-repo2docker
it should be exec jupyter nbclassic "${@:3}"
(the difference is the 3)
not sure exactly where, but probably Binder passes an extra argument when starting the container
python3 -c "some startup code" [extra args for server app]
--
and slice there.