Hello, maintainer of Parcels here. We use Binder, but have been encountering the following uninformative error after trying to launch binder during step 39 of repo2docker
:
The command '/bin/sh -c TIMEFORMAT='time: %3R' bash -c 'time ${MAMBA_EXE} env update -p ${NB_PYTHON_PREFIX} --file ".binder/environment.yml" && time ${MAMBA_EXE} clean --all -f -y && ${MAMBA_EXE} list -p ${NB_PYTHON_PREFIX} '' returned a non-zero code: 137
I was able to successfully build locally using repo2docker
so I’m quite sure it isn’t an error on our end. My only thoughts is its a resource limitation imposed by binder.org
. We also aren’t the only ones encountering this problem, see this open issue related to jupyterlab/jupyterlab-demo
.
Does anyone have a suggested work around? Binder is super practical for our users to get introduced to our software. I saw some unrelated mention of repo2docker
GitHub Actions, perhaps that could help - but I don’t know where that fits into the grand scheme of things.
Links:
https://mybinder.org/v2/gh/OceanParcels/parcels/master?labpath=docs%2Fexamples%2Fparcels_tutorial.ipynb