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
Since there are multiple tools that can depend on other there may be the need to update the Docker Image also when one of the dependencies get updated. The solution is to add a new boolean parameter in the config.py called "build_always" that behaves in this way:
If "build_always" is True the image is built anyway (even if the version on Docker Hub is the same)
If the --push option is specified and there is already a version with the same tag nameon Docker Hub then the digest of the newly build image is checked against the digest of the image on Docker Hub. If they are different the new image is pushed on Docker Hub keeping the same tag version.
In this way it is possible to have a multi-dependency Docker Image.
The text was updated successfully, but these errors were encountered:
The alternative is to use a different tag name (say daily) and keep the other tags untouched. The same behaviour of the digest applies the same way, but on a "special" tagname. What do you think is the best solution?
Since there are multiple tools that can depend on other there may be the need to update the Docker Image also when one of the dependencies get updated. The solution is to add a new boolean parameter in the config.py called "build_always" that behaves in this way:
In this way it is possible to have a multi-dependency Docker Image.
The text was updated successfully, but these errors were encountered: