Cert-manager: arm64 issue; cert-manager-acmesolver created with incorrect arch

Created on 12 Mar 2019  路  2Comments  路  Source: jetstack/cert-manager

Describe the bug:
When using arm64 version of cert-manager a cert-manager-acmesolver pod with incorrect architecture

Expected behaviour:
cert-manager-acmesolver pod to use arm64 image

Steps to reproduce the bug:
https://github.com/jetstack/cert-manager/blob/master/docs/tutorials/acme/quick-start/index.rst
I was following this tutorial; In step seven after apply the ingress a cert-manager-acmesolver pod is created but it's unable to start due to "exec format error"

Environment details::

  • Kubernetes version v1.12.2;
  • Provisioner: kubeadm
  • cert-manager version: release-0.7 (arch arm64)
  • Install method: static manifests.

/kind bug

areacmhttp01 aredeploy help wanted kinbug prioritimportant-soon

Most helpful comment

You will need to add the --acme-http01-solver-image=quay.io/jetstack/cert-manager-acmesolver-arm64:v0.7.0 flag to your cert-manager-controller deployment to make this work.

We should auto-detect this however, and probably default the image used to be the same arch as the controller is built for.

/area deploy
/area acme/http01
/priority important-soon
/help
/milestone Next

All 2 comments

You will need to add the --acme-http01-solver-image=quay.io/jetstack/cert-manager-acmesolver-arm64:v0.7.0 flag to your cert-manager-controller deployment to make this work.

We should auto-detect this however, and probably default the image used to be the same arch as the controller is built for.

/area deploy
/area acme/http01
/priority important-soon
/help
/milestone Next

@munnerz:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

You will need to add the --acme-http01-solver-image=quay.io/jetstack/cert-manager-acmesolver-arm64:v0.7.0 flag to your cert-manager-controller deployment to make this work.

We should auto-detect this however, and probably default the image used to be the same arch as the controller is built for.

/area deploy
/area acme/http01
/priority important-soon
/help
/milestone Next

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Was this page helpful?
0 / 5 - 0 ratings