jupyter lab buildwith a custom dockerfile? It builds locally with
jupyter-repo2docker. Here is the error we get, in this case the
Step 9/14 : RUN jupyter serverextension enable --sys-prefix jupyter_server_proxy && jupyter labextension install @jupyterlab/server-proxy && jupyter lab build ---> Running in 0f73ee8aa8dd Enabling: jupyter_server_proxy\ - Writing config: /opt/conda/etc/jupyter - Validating... jupyter_server_proxy OK Building jupyterlab assets (build:prod:minimize) An error occured. RuntimeError: JupyterLab failed to build See the log file for details: /tmp/jupyterlab-debug-zn0wcl2n.log Removing intermediate container 0f73ee8aa8dd The command '/bin/bash -o pipefail -c jupyter serverextension enable --sys-prefix jupyter_server_proxy && jupyter labextension install @jupyterlab/server-proxy && jupyter lab build' returned a non-zero code: 1
[W 2020-09-14 19:54:43.245 JupyterHub log:174] 403 POST /hub/api/users/binder-examples-requirements-a3bknnqf (email@example.com) 5.98ms. I figure this is a problem with the API token. I looked in the pods and on binderhub
/etc/binderhub/secret/binder.hub-tokenis identical to
/etc/jupyterhub/secret/values.yaml. Is there anything else I can check to figure out why I'm getting these 403s?
Hi all, when I try to get at https://mybinder.org/v2/gh/imagejan/image-processing-courses/update-2019?filepath=03-image-processing-filtering.ipynb I get:
Found built image, launching... Launching server... Internal Server Error
Is that a known problem? That link/repo was working well in the past.
New > Terminalin the classic interface to get a terminal