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
{{ message }}
This repository has been archived by the owner on Dec 14, 2023. It is now read-only.
At present, we sometimes find ourselves unable to build certain containers because our base image doesn't change much, and consequently isn't rebuilt very often. That means that the apt package links occasionally 404 as a result of old packages getting removed from the repository when new ones become available (additional context here).
One way to solve this problem would be to create a cron to rebuild the base image daily or weekly.
The text was updated successfully, but these errors were encountered:
We're supposedly limited to 2000 Action minutes/month but I think in our case they're effectively unlimited for some reason? Is this limit for private repos only?
Easy way to trigger the base image rebuild would be to print out the docker pull commands instead of running them directly from the ./dev/pull.py script, grep out the base containers (being careful to leave others that might be matching the base string), and pull only those, i.e. instead of:
./dev/pull.py
one can do something like:
./dev/pull.py -p | grep -v '/base' | bash
(We're reverse-grepping for slash-base here so that it doesn't match images such as solr-base.)
At present, we sometimes find ourselves unable to build certain containers because our
base
image doesn't change much, and consequently isn't rebuilt very often. That means that theapt
package links occasionally 404 as a result of old packages getting removed from the repository when new ones become available (additional context here).One way to solve this problem would be to create a cron to rebuild the
base
image daily or weekly.The text was updated successfully, but these errors were encountered: