You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In working with the project, one notices a fair number of errors reported in the docker-compose build log. It is hard to say which are worth worrying about. A survey of the error messages can be crudely extracted by:
docker-compose logs |grep -i error
I wonder if we may wish to do a more careful audit of the build process to see what can be cleaned up.
It is unclear how best to robust reboot the system. Even after a (relatively) successful power up sequence, attempting restarting of the Tripal container (alone), i.e.
docker-compose restart tripal
goes partway then hits fails with an exit code of 1.
Bring the whole system "down" first, then rebooting it in sequence is a bit time consuming.
The text was updated successfully, but these errors were encountered:
In working with the project, one notices a fair number of errors reported in the docker-compose build log. It is hard to say which are worth worrying about. A survey of the error messages can be crudely extracted by:
I wonder if we may wish to do a more careful audit of the build process to see what can be cleaned up.
It is unclear how best to robust reboot the system. Even after a (relatively) successful power up sequence, attempting restarting of the Tripal container (alone), i.e.
goes partway then hits fails with an exit code of 1.
Bring the whole system "down" first, then rebooting it in sequence is a bit time consuming.
The text was updated successfully, but these errors were encountered: