Open TG9541 opened 8 years ago
Hi @TG9541, thanks for reporting,
I will give a look, I fear they updated their install method again.
I suggest you to pull the image I built 21 days ago: https://hub.docker.com/r/moul/readthedocs/ instead of rebuilding a new one
Hi @moul, thanks, I'll try that. This sure is a moving target :-)
@moul: I pulled the image above, changed the docker-compose.yml to use the image, and I still get the same error when I run the docker-compose line above. Maybe I am supposed to add a "docker.py" for configuration?
Ok perfect,
No you are not supposed to add this file by yourself, this file used to exist in the readthedocs codebase, here is where I hardcode import it: https://github.com/moul/docker-readthedocs/blob/master/config/etc/default/rtd-config.py
I just removed the deprecated import (automated docker build in progress)
Can you give a new try ?
Thanks, that fixed it :-)
By the way, the docker-as-the-build-environment feature was what initially caught my interest. I'd have to pass-in the docker daemon socket (e.g. like -v /var/run/docker.sock:/var/run/docker.sock
). Isn't the docker.py import the file where I should provide the configuration?
@TG9541 happy I could help :)
I didn't heard about this docker-as-the-build-environment feature before,
but in general, to practice "docker in docker (a.k.a dind)", passing the -v /var/run/docker.sock:/var/run/docker.sock
is the way to go.
If you only need to introspect the docker images, you can just pass -v /var/lib/docker:/var/lib/docker:ro
in read-only, but in your case, I think you will require a full socket access
Good luck !
I tried running docker-readthedocs, but it looks like a docker related dependency is missing. I'm new to RTD, and hence I can't easily say how far off the Dockerfile in moul/docker-readthedocs is from building successfully.
Commands to reproduce the problem:
Here is the "tail" of the build log with the error message: