Closed RichardBruskiewich closed 5 years ago
I guess that's because the image comes with a collection of pre-installed modules, and one of them is probably not yet 3.x ready. I'm going to check this. In the meantime, you can play with TRIPAL_ENABLE_MODULES to enable only the modules you need
Ok, I've pushed an update of the docker image, it no longer tries to install deprecated modules. I'm closing it as I think you shouldn't have this problem anymore, feel free to reopen if you still have problem!
While running the latest (Oct 2/18) docker-compose.yml build on the v3.x branch, the build of the web container, although giving the impression that it was building, was in fact caught in some kind of bizarre infinite loop of configuration (hence, never actually completes its provisioning/initialization)?
Here is one full cycle of the docker log output for the issue (I'm making an educated guess.. perhaps wrong? - of where the cycle starts). I do notice (highlighted here) that whatever script is running, it appears to be picking up the 7.x-2.1 release of the Tripal code, NOT the 7.x-3.x. I suspect that this is because the latest release of the repo is set to 2.1, so when https://updates.drupal.org/release-history/tripal/7.x is accessed, that is all that is seen.