-
Notifications
You must be signed in to change notification settings - Fork 46
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 error docker rest VV 2.0 #75
Comments
Let me check this out. It looks like you created the folders on your local system? https://github.com/openvar/rest_variantValidator/blob/master/docs/DOCKER.md
$ mkdir ~/variantvalidator_data
$ mkdir ~/variantvalidator_data/share i.e. a directory called share in your home directory I will try spark up a new install on my machine now and see if debugging is needed |
OK, I get the following $ ls ~/variantvalidator_data
share
$ ls ~/variantvalidator_data/share/
applications ca-certificates fonts icons jupyter logs man seqrepo Re-building now |
Hi @AnotherSimon please confirm you created the requested directories as above in this issue. I'm not seeing this error |
There was one more issue I encountered when building the docker version on a different server. For vdb image to be built, I had to edit
Note that the line switching to user root may or may not be necessary. (it's a copy-pasta solution) Not sure why this only happened on this particular server. |
Thanks for the update. Leave it with me. I'll get back to you. |
A bit late to the 2.0 party but I seem to be getting a build error using docker on version c034e95.
Followed the instructions at DOCKER.md (seemingly without errors) up to
docker-compose up
at which point I see the following error:Is there supposed to be an underscore in the leaf paths on the docker containers? (like
.../volumes/rest_variantvalidator_seqdata/_data
)I also noticed that there isn't any data in the folder
~/variantvalidator_data/share/
on the host system. I do believe there are some folders that should be created here but docker-compose build --no-cache does not seem to have done this.This problem persists after issuing the command
docker system prune -a --volumes
.The text was updated successfully, but these errors were encountered: