I am seeing a

CrashBackOffLoop

all of a sudden on an M2 MacBook for the

prerequisites-mysql

pod and image it is pulling, when running

helm install prerequisites datahub/datahub-prerequisites

. After inspecting the images, it is pulling down the incorrect image architecture (amd64) for mysql, all other prerequisites are pulling the correct one (arm64). Opened a question/issue here: https://github.com/acryldata/datahub-helm/issues/435 just trying to track down why this started all of a sudden. Was having no issues deploying these helm charts up until yesterday. Any help would be greatly appreciated.

Odd, the architecture isn't controlled by the datahub helm charts (prerequisites) that I am aware of. Typically k8/minikube should be selecting the right image based on its configuration. You might try removing the image from minikube's image cache using `minikube image rm`⁣ on the mysql image and having it re-pull.

Hey @brainy-tent-14503 thanks for the response. I think it may be something with the helm chart and underlying image, if I attempt to pull

arm64

for both the current 9.1.8 helm version:

bitnami/mysql:8.0.29-debian-11-r3

then run the same pull for

latest

the first one isn't found and resorts to

amd64

whereas

latest

will correctly get

arm64

. Screenshots below (the inspect command is for latest). Also, not sure it is relevant but in the Charts.yaml under prerequisites, the repository URL for mysql returns an HTTP 404 (

<https://raw.githubusercontent.com/bitnami/charts/archive-full-index/bitnami>)

I can reproduce, but I don't believe it is something we can fix from our side. The upstream bitnami charts would need to update their image tag. However you can of course override the tag with your values file. A minimum example would be as follows. In addition to that, I'll fix the repo and update the chart version for the upstream chart but the latest upstream chart also shows the same tag being used.

mysql:
  enabled: true
    image:
      tag: latest

Thanks for verifying David! Much appreciated, I'll keep an eye on that PR, but thank you also for the workaround.