binder-workspace-demo

binder-workspace-demo copied to clipboard

I followed the well documented instructions and can confirm that the recipe provided on this page once worked for me. Over time, however, I changed contents of my repo color-matcher and its jupyter file triggering new image builds with a blank workspace. To give an example, please have a look at the respective binder link.

During the many attempts of different image builds, the following lines caught my attention:

Step 46/50 : RUN chmod +x binder/postBuild ---> Running in 0dba22a546ed Removing intermediate container 0dba22a546ed ---> a35230f353d1 Step 47/50 : RUN ./binder/postBuild ---> Running in 0ca626a51ea7 Saved workspace: /home/jovyan/.jupyter/lab/workspaces/lab-a511.jupyterlab-workspace Removing intermediate container 0ca626a51ea7 ---> b6d44587ec91

Are there any clues as to the roots of this once working, now failing behavior?

Quick update

After forking this repo, I end up with the default workspace using the corresponding Binder URL:

https://mybinder.org/v2/gh/hahnec/binder-workspace-demo/master?urlpath=lab

So, it appears that the herein presented solution does not work anymore for newly built images. Is it that Binder does not support this workspace feature anymore? Or is there a problem in the image build process?

Thanks for pinging this @hahnec! There may have been a regression upstream, I'll look into it

Hi Ian, the problem seems to persist. Are there any news from your side? Were you able to have a look in the meantime?