Image found but not launching?

I’m having trouble launching. Build seemed to go ok, but shows launching server for a long time, then Launch Attempt 1 failed … but no other log messages.

Any insight?

Hmmm, on the original build page the end of the log showed:

{"aux": {"ID": "sha256:094899f1dc6d0cc4899dfa4f485a2ccb57ee6f039f8cefac1b267c9f19ead601"}}[Warning] One or more build-args [NB_USER NB_UID] were not consumed
Successfully built 094899f1dc6d
Successfully tagged gcr.io/binder-prod/r2d-f18835fd-howisonlab-2dsoftcite-2ddataset-ac023a:a1dd9f72aa3739af9c03c7a239061a11b82c228f
Pushing image
Pushing image
Pushing image
Pushing image
Pushing image
Pushing image
Pushing image
Pushing image
Pushing image
Pushing image
Successfully pushed gcr.io/binder-prod/r2d-f18835fd-howisonlab-2dsoftcite-2ddataset-ac023a:a1dd9f72aa3739af9c03c7a239061a11b82c228fBuilt image, launching...
Launching server...
Launch attempt 1 failed, retrying...
Launch attempt 2 failed, retrying...
Launch attempt 3 failed, retrying...
Internal Server Error

It looks like this is your repo:

That Dockerfile is based on rocker/tidyverse, but repo2docker and mybinder have specific requirements:

I noticed the Docker Hub readme for https://hub.docker.com/r/rocker/tidyverse/ says there’s a rocker/binder image, maybe worth investigating?

You could also try installing the tidyverse using an environment.yml file like so https://github.com/betatim/r-conda
Dockerfiles are advanced usage of Binder and can be tricky to debug

Thanks y’all. I’m coming to understand the options here, where having one’s own Dockerfile is some advanced stuff. I have it because I use it locally on my laptop with this repo, which I’d like to keep doing. I’m looking into repo2docker locally (which seems like a great option anyway!) which would let me take the Dockerfile (and maybe the docker-compose.yml which I use for mounting local folders) out of the repo.

But assuming I can’t take the Dockerfile out, is there any way to have Binder ignore it?

Assuming I’m looking at the correct bit of code if you’ve got a binder/ or .binder/ directory repo2docker will use that directory instead of the root of the repo.

Awesome. Found documentation here: https://mybinder.readthedocs.io/en/latest/faq.html#can-i-put-my-configuration-files-outside-the-root-of-my-repository

Looks like that’s the go! Although i’m really intrigued by repo2docker locally, so probably will pursue both.

Just linking some docs to confirm the priority order of the directories :slight_smile: https://repo2docker.readthedocs.io/en/latest/usage.html#where-to-put-configuration-files

If its useful, this repo has a couple of environment configurations. binder contains a Dockerfile that works with mybinder.org and env-configuration contains repo2docker files: https://github.com/alan-turing-institute/QUIPP-pipeline This may be useful for you as running r2d locally has a flag to say where the config files are