Open jessestuart opened 6 years ago
Could be unrelated — but I should mention that to get the image to build, I initially had to pull out the GPG checks, as pgp.mit.edu has been down for (at least) the past several hours. Apparently this isn't uncommon?
I took the liberty of adding the hashicorp public key to the SKS key server recommended in that thread, and was able to build after making that change. ¯\_(ツ)_/¯
Hey hey team Hashicorp,
Was surprised today to find that — after a couple months using the mutli-arch friendly
1.1.0
image (see related discussion in e.g., #67), the recently published1.2.0
image only supportsamd64
. I'm assuming a hiccup/misconfiguration somewhere in the CI pipeline, but haven't been able to track it down.Using
manifest-tool
on 1.2.0: (output abridged)Compared to the same command with 1.1.0:
So I did some poking around:
consul
in the Docker Hub "official" /library
repo since the1.1.0
release — just bumping the version and commit hash (verified that the hash is correct).bashbrew
, etc.) to know where to look next. From the Travis logs:Any thoughts on this? In the meantime, and if anyone else is looking to upgrade a multiarch deployment, I've built an image compatible with & tested on
arm64
,armv7
, andamd64
, which you can pull fromjessestuart/consul:1.2.0
. Would be nice to sort out this regression, though :) Happy to take a further look if anyone has thoughts on where to investigate apart from the places mentioned above.