Closed noelmcloughlin closed 3 years ago
For those coming across this issue, a temporary solution is to override the pillar defaults as below:
docker:
pkg:
compose:
binary:
options: ''
source: 'https://github.com/docker/compose/releases/download/1.29.1/docker-compose-Linux-x86_64'
source_hash: '8097769d32e34314125847333593c8edb0dfc4a5b350e4839bef8c2fe8d09de7'
Using the releases from the Docker Compose Github
Can we use the github.com sources by default in the formula yaml files as well? That seems to work if I test it.
However, with the current use of bintray.org the source always points 'latest', but the source_hash is hard-coded. I'm a bit confused by that. Isn't the hash of the 'latest' changing all the time?
Looking at https://github.com/docker/compose/releases each release tarball (tar.gz) has a checksum (tar.gz.sha256).
If source_hash: null
then formula will automatically calculate correct source_hash
value so null
is best for github source.
https://github.com/saltstack-formulas/docker-formula/blob/4cc1e706e4778e1aabef0023da668eaafef8afff/docker/map.jinja#L55-L59
@noelmcloughlin Thanks, that seems to work: #290
Fixed by #290.
Describe the bug
Jfrog has shutdown bintray: https://www.infoq.com/news/2021/02/jfrog-jcenter-bintray-closure/