Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build failing on eclib repo #155

Closed
fperez opened this Issue Mar 12, 2019 · 4 comments

Comments

Projects
None yet
4 participants
@fperez
Copy link

fperez commented Mar 12, 2019

When trying to build @JohnCremona's eclib, the error below is happening. Cc @willingc as per conversation at meeting...

Waiting for build to start...
/usr/local/lib/python3.7/site-packages/repo2docker/utils.py:214: FutureWarning:Possible nested set at position 1815
  """, re.VERBOSE)
Picked Git content provider.
Cloning into '/tmp/repo2dockerggxtxu2s'...
HEAD is now at cffc972 removed hardwired docdir in docs/Makefile.am so users can set it in configure
Building conda environment for python=Using CondaBuildPack builder
Building conda environment for python=Building conda environment for python=Step 1/48 : FROM buildpack-deps:bionic
 ---> 5a0b17f040e2
Step 2/48 : ENV DEBIAN_FRONTEND=noninteractive
 ---> Using cache
 ---> 03f7b0dcebf0
Step 3/48 : RUN apt-get -qq update &&     apt-get -qq install --yes --no-install-recommends locales > /dev/null &&     apt-get -qq purge &&     apt-get -qq clean &&     rm -rf /var/lib/apt/lists/*
 ---> Using cache
 ---> 2bc64aa7ae1c
Step 4/48 : RUN echo "en_US.UTF-8 UTF-8" > /etc/locale.gen &&     locale-gen
 ---> Using cache
 ---> 53b8cc18ff96
Step 5/48 : ENV LC_ALL en_US.UTF-8
 ---> Using cache
 ---> 9f6bc52870c3
Step 6/48 : ENV LANG en_US.UTF-8
 ---> Using cache
 ---> e443da622fcb
Step 7/48 : ENV LANGUAGE en_US.UTF-8
 ---> Using cache
 ---> 334b6ee98402
Step 8/48 : ENV SHELL /bin/bash
 ---> Using cache
 ---> 8ecac7906f14
Step 9/48 : ARG NB_USER
 ---> Using cache
 ---> 6791c24df8d5
Step 10/48 : ARG NB_UID
 ---> Using cache
 ---> 47be89abe339
Step 11/48 : ENV USER ${NB_USER}
 ---> Using cache
 ---> 5178b1743797
Step 12/48 : ENV HOME /home/${NB_USER}
 ---> Using cache
 ---> d23a88a42dc6
Step 13/48 : RUN adduser --disabled-password     --gecos "Default user"     --uid ${NB_UID}     ${NB_USER}
 ---> Using cache
 ---> 9bfc58bec727
Step 14/48 : RUN wget --quiet -O - https://deb.nodesource.com/gpgkey/nodesource.gpg.key |  apt-key add - &&     DISTRO="bionic" &&     echo "deb https://deb.nodesource.com/node_10.x $DISTRO main" >> /etc/apt/sources.list.d/nodesource.list &&     echo "deb-src https://deb.nodesource.com/node_10.x $DISTRO main" >> /etc/apt/sources.list.d/nodesource.list
 ---> Using cache
 ---> 17ec8788f420
Step 15/48 : RUN apt-get -qq update &&     apt-get -qq install --yes --no-install-recommends        less        nodejs        unzip        > /dev/null &&     apt-get -qq purge &&     apt-get -qq clean &&     rm -rf /var/lib/apt/lists/*
 ---> Using cache
 ---> a0d9e606192c
Step 16/48 : EXPOSE 8888
 ---> Using cache
 ---> e12ab055883c
Step 17/48 : ENV APP_BASE /srv
 ---> Using cache
 ---> 0a8f6d2a8f74
Step 18/48 : ENV NPM_DIR ${APP_BASE}/npm
 ---> Using cache
 ---> 0b58425f6729
Step 19/48 : ENV NPM_CONFIG_GLOBALCONFIG ${NPM_DIR}/npmrc
 ---> Using cache
 ---> cf4ec121d6bc
Step 20/48 : ENV CONDA_DIR ${APP_BASE}/conda
 ---> Using cache
 ---> 84e58c7c8ec4
Step 21/48 : ENV NB_PYTHON_PREFIX ${CONDA_DIR}
 ---> Using cache
 ---> 8977f2fc4c60
Step 22/48 : ENV KERNEL_PYTHON_PREFIX ${NB_PYTHON_PREFIX}
 ---> Using cache
 ---> dc4741f75046
Step 23/48 : ENV PATH ${CONDA_DIR}/bin:${NPM_DIR}/bin:${PATH}
 ---> Using cache
 ---> f1f8c9f25642
Step 24/48 : COPY conda/install-miniconda.bash /tmp/install-miniconda.bash
 ---> Using cache
 ---> 15a33d57beb2
Step 25/48 : COPY conda/environment.frozen.yml /tmp/environment.yml
 ---> Using cache
 ---> 4aebf902ebdf
Step 26/48 : RUN mkdir -p ${NPM_DIR} && chown -R ${NB_USER}:${NB_USER} ${NPM_DIR}
 ---> Using cache
 ---> e8d3c7dc6491
Step 27/48 : USER ${NB_USER}
 ---> Using cache
 ---> 7077bf285dca
Step 28/48 : RUN npm config --global set prefix ${NPM_DIR}
 ---> Using cache
 ---> 6b9050513c19
Step 29/48 : USER root
 ---> Using cache
 ---> c555f9ff6ac3
Step 30/48 : RUN bash /tmp/install-miniconda.bash && rm /tmp/install-miniconda.bash /tmp/environment.yml
 ---> Using cache
 ---> bf88d8e14628
Step 31/48 : ARG REPO_DIR=${HOME}
 ---> Using cache
 ---> e8df4cd41d82
Step 32/48 : ENV REPO_DIR ${REPO_DIR}
 ---> Using cache
 ---> f38c2edc032c
Step 33/48 : WORKDIR ${REPO_DIR}
 ---> Using cache
 ---> 9151b3193a52
Step 34/48 : ENV PATH ${HOME}/.local/bin:${REPO_DIR}/.local/bin:${PATH}
 ---> Using cache
 ---> 2b70c64a2ba9
Step 35/48 : USER root
 ---> Using cache
 ---> 354d632835b7
Step 36/48 : COPY src/ ${REPO_DIR}
 ---> d6e3923c3ee5
Step 37/48 : RUN chown -R ${NB_USER}:${NB_USER} ${REPO_DIR}
 ---> Running in 0653a2f2ebba
Failed to connect to event stream
@choldgraf

This comment has been minimized.

Copy link
Member

choldgraf commented Mar 12, 2019

one quick note: sometimes this is just a logging break, but the build is still happening - you see Failed to connect to event stream, but if you were to re-click that Binder link quickly you'll be re-connected to a build that's still in progress. No idea if that's the case here or not, but just something I've noticed :-)

@betatim

This comment has been minimized.

Copy link
Member

betatim commented Mar 12, 2019

I think this issue is about JupyterLab workspaces which contain the username in the file that specifies which workspaces to open. Is that right @fperez ?

@fperez

This comment has been minimized.

Copy link
Author

fperez commented Mar 19, 2019

This binder indeed had that issue, but I thought we had it working and I don't know why it would pop up this specific error.

In any case, it's mostly in case it's something meaningful to track down for the binder side, for now I'm not working on that repo so it's OK to close as far as I'm concerned :)

@willingc

This comment has been minimized.

Copy link
Contributor

willingc commented Mar 19, 2019

Let's close for now. If it pops up again, we can reopen. Thanks.

@willingc willingc closed this Mar 19, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.