Manifests are derived from a specific image, not the magical latest tag (#1759)

Again, sorry for using my admin powers.
This commit is contained in:
Matt Robinson 2019-04-15 14:30:36 -04:00 committed by GitHub
parent a81d13920f
commit ac66260638
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -224,9 +224,9 @@ push-images: ## Push Docker images to Docker Hub (jenkins)
docker push storjlabs/satellite:${TAG}${CUSTOMTAG}-amd64 \
&& docker push storjlabs/satellite:${TAG}${CUSTOMTAG}-arm32v6 \
&& for t in ${TAG}${CUSTOMTAG} ${LATEST_TAG}; do \
docker manifest create storjlabs/$$c:$$t storjlabs/$$c:$$t-amd64 storjlabs/$$c:$$t-arm32v6 \
&& docker manifest annotate storjlabs/$$c:$$t storjlabs/$$c:$$t-amd64 --os linux --arch amd64 \
&& docker manifest annotate storjlabs/$$c:$$t storjlabs/$$c:$$t-arm32v6 --os linux --arch arm --variant arm32v6 \
docker manifest create storjlabs/$$c:$$t storjlabs/$$c:${TAG}${CUSTOMTAG}-amd64 storjlabs/$$c:${TAG}${CUSTOMTAG}-arm32v6 \
&& docker manifest annotate storjlabs/$$c:$$t storjlabs/$$c:${TAG}${CUSTOMTAG}-amd64 --os linux --arch amd64 \
&& docker manifest annotate storjlabs/$$c:$$t storjlabs/$$c:${TAG}${CUSTOMTAG}-arm32v6 --os linux --arch arm --variant arm32v6 \
&& docker manifest push --purge storjlabs/$$c:$$t \
; done \
; done