Closed nsheff closed 6 years ago
Something wrong with that cache, I think...
docker run --rm -it --volume /mnt/q:/mnt/q databio/lolaweb bash
R
LOLA::loadRegionDB("/mnt/q/shefflab/LOLAweb/databases//LOLACore/mm10/")"
I am trying regenerating the cache now.
that didn't work. it may be a LOLA version thing. can we try updating the dev container to the latest R/bioconductor/LOLA version?
turns out it's not a LOLA version problem, but could be a GenomicRanges version problem. I still think we should update...
ok yeah i think the shinyBase container image we are pulling should include the bioconductor (not github) version of LOLA:
https://github.com/databio/shinyBase/blob/master/Dockerfile#L29
that gets pulled in via the LOLAweb dockerfile ... but i can't remember if that base image gets rebuilt automatically? every time we push a change to databio/shinyBase ? manually?
@nmagee is going to get sick of explaining this to me :)
it only gets rebuilt if we push a change to databio/shinyBase or trigger it manually.
Ok, I rebuilt it locally and pushed changes -- can we trigger a re-deploy of the containers @nmagee to see if this solves the problem?
Hey, just getting home and seeing this message. Yes I’ll go ahead and do a new pull and redeploy.
Since you rebuilt the shinyBase container and pushed it up to Docker Hub, I just went to the TravisCI page for LOLAweb and triggered the rebuild there. That actually sends an SQS message that will spawn them out onto the servers in a seamless way.
I’m seeing the new Dev containers up and running there now. Can one of you guys verify that your fix is in place and working okay?
Yes, that worked! So, turns out I was right, it was probably some kind GRanges version issue. it's working now on mm10.
@nmagee thanks for redeploy -- at some point can you write down some brief instructions or a link somewhere so that in the future I don't have to bother you to do that? I forgot we were using travis for those builds and that was the way to rebuild it...
it's giving this error: