Meshery-istio image doesnt work for arm64

[pdsouza01]

Current Behavior

Pods doesn't come up with image : https://hub.docker.com/layers/layer5/meshery-istio/stable-latest/images/sha256-1fea8fd2cbf4d91298899a99d93285c339815866ad0f8833b3d34a0e85da222e?context=explore

I debugged it and looks like the image in dockerhub (https://hub.docker.com/layers/layer5/meshery-istio/stable-latest/images/sha256-1fea8[…]99a99d93285c339815866ad0f8833b3d34a0e85da222e?context=explore) for arm is build with amd64 tag

Expected Behavior

Screenshots/Logs

kubectl get pods -n meshery NAME                                    READY   STATUS             RESTARTS   AGE meshery-app-mesh-d8bb6fb98-26lgd        0/1     CrashLoopBackOff   300        25h meshery-cilium-77c894d948-ksp5h         0/1     CrashLoopBackOff   300        25h meshery-consul-c4f966fb-d424r           0/1     CrashLoopBackOff   300        25h meshery-dbcf8bbc9-gwmmn                 0/1     CrashLoopBackOff   301        25h meshery-istio-54f78f78-9qshc            0/1     CrashLoopBackOff   300        25h meshery-kuma-66fb8d8fb9-pvf6w           1/1     Running            0          25h meshery-linkerd-747f88f674-ws6zr        0/1     CrashLoopBackOff   300        25h meshery-nginx-sm-78b6dd775d-b6shd       0/1     CrashLoopBackOff   300        25h meshery-nsm-578546d5c6-ldg9x            0/1     CrashLoopBackOff   300        25h meshery-operator-586c6f895d-vs4l8       0/2     CrashLoopBackOff   600        25h meshery-osm-5cb545d586-k7njp            1/1     Running            0          25h meshery-traefik-mesh-747f68fc68-7d8nh   0/1     CrashLoopBackOff   300        25h

kubectl describe pod meshery-istio-54f78f78-9qshc -n meshery Name:         meshery-istio-54f78f78-9qshc Namespace:    meshery Priority:     0 Node:         node01.local Start Time:   Thu, 07 Jul 2022 12:53:13 -0700 Labels:       app.kubernetes.io/instance=meshery app.kubernetes.io/name=meshery-istio pod-template-hash=54f78f78 Annotations:   Status:       Running IP:           10.42.0.141 IPs: IP:           10.42.0.141 Controlled By:  ReplicaSet/meshery-istio-54f78f78 Containers: meshery-istio: Container ID:   docker://853944c0a049687c1b4cffd44604d2d8f2894ad3ede098c4d2461da46ab0b45d Image:          layer5/meshery-istio:stable-latest Image ID:       docker-pullable://layer5/meshery-istio@sha256:18e226886f2f10b0f076dbf02b1b5ac569d2fb54e317414086178c904557e0e1 Port:           10000/TCP Host Port:      0/TCP State:          Waiting Reason:       CrashLoopBackOff Last State:     Terminated Reason:       Error Exit Code:    1 Started:      Fri, 08 Jul 2022 14:11:06 -0700 Finished:     Fri, 08 Jul 2022 14:11:06 -0700 Ready:          False Restart Count:  301 Environment:     Mounts: /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-7m897 (ro) Conditions: Type              Status Initialized       True Ready             False ContainersReady   False PodScheduled      True Volumes: kube-api-access-7m897: Type:                    Projected (a volume that contains injected data from multiple sources) TokenExpirationSeconds:  3607 ConfigMapName:           kube-root-ca.crt ConfigMapOptional:        DownwardAPI:             true QoS Class:                   BestEffort Node-Selectors:               Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s node.kubernetes.io/unreachable:NoExecute op=Exists for 300s Events: Type     Reason            Age                     From     Message ----     ------            ----                    ----     ------- Warning  DNSConfigForming  4m24s (x7254 over 25h)  kubelet  Search Line limits were exceeded, some search paths have been omitted, the applied search l ine is: meshery.svc.rke.rancher-local svc.rke.rancher-local rke.rancher-local

kubectl logs meshery-istio-54f78f78-9qshc -n meshery exec /meshery-istio: exec format error

Environment

• Host OS: Linux
• Platform: Kubernetes
• Meshery Server Version: stable-v
• Meshery Client Version: stable-v
• Meshery Adapter Version: stable-latest

---

Contributor Guides and Resources

• 🛠 Meshery Build & Release Strategy
• 📚 Instructions for contributing to documentation
  • Meshery documentation site and source
• 🎨 Wireframes and designs for Meshery UI in Figma
• 🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack

[welcome[bot]]

Thanks for opening this issue. A contributor will be by to give feedback soon. In the meantime, please review the Layer5 Contributors' Welcome Guide and sure to join the community Slack.

[leecalcote]

Thank you, @pdsouza01 👍

[leecalcote]

Notes from @Revolyssup:

@Preema Merlin Dsouza Thank you for catching this one! I just noticed that it is because inside the Dockerfile, OS/Arch is hardcoded here and here. It should be passed as a build argument inside the workflow here and the Dockerfile needs to be updated accordingly.

This issue is up for grabs.

[leecalcote]

@pdsouza01 will you be tomorrow's CI meeting? If so, let's be sure that this gets on the agenda.

[AugustasV]

I will look what I can do about it

[AugustasV]

@pdsouza01 what about now? It works properly for me

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

Checking in... it has been awhile since we've heard from you on this issue. Are you still working on it? Please let us know and please don't hesitate to contact a MeshMate or any other community member for assistance.

---

        Be sure to join the community, if you haven't yet and please leave a :star: star on the project :smile: on the project.

[AugustasV]

It works as expected. Create new issue if problem still persist.