Describe the bug:
Apparently the latest version of the image comes with a binary compiled for arm instead of amd64 as previous versions did, hence breaking compatibility.
I have verified it by running the image locally in my laptop and by inspecting the image using dive.
I'm not familiar with the build process using bazel so I have not gone further. Have been running cert-manager during months without problem and apparently the last push to quay.io/jetstack/cert-manager-acmesolver updated the canary tag 20h ago and introduced this breaking change according to quay.
Expected behaviour:
The docker image should contain a amd64 binary.
Steps to reproduce the bug:
Run the following command from a amd64 machine:
$ docker run --rm -ti quay.io/jetstack/cert-manager-acmesolver:canary bash
standard_init_linux.go:190: exec user process caused "exec format error"
Anything else we need to know?:
Environment details::
/kind bug
Thanks for the report - I have confirmed this and tracked it down to only the latest image tag:
$ docker run --entrypoint=uname --rm -ti quay.io/jetstack/cert-manager-acmesolver:2e95421d -a
Linux 9d97cb920973 4.9.125-linuxkit #1 SMP Fri Sep 7 08:20:28 UTC 2018 x86_64 Linux
$ docker run --entrypoint=uname --rm -ti quay.io/jetstack/cert-manager-acmesolver:a06d888a -a
Linux ff55648c09bf 4.9.125-linuxkit #1 SMP Fri Sep 7 08:20:28 UTC 2018 armv7l Linux
It appears the build job in question failed after pushing the acmesolver image, which seems highly suspect (https://storage.googleapis.com/jetstack-logs/logs/post-cert-manager-release-canary/1124363456384864256/build-log.txt)
We've been working on a new release tool in time for v0.8 that recently merged, and there are clearly some issues still at the moment.
For the time being, please use a versioned release of cert-manager - I'll put a patch together to fix this up shortly!
/priority critical-urgent
/milestone v0.8
I've tracked the issue here down and fixed it in #1639 馃槃