anybody tried running epinio on rancher desktop...(moby) via M1 Pro... the k3d seems to be crashing
04/22/2023, 6:51 PM
Ah, that's interesting. So the cluster is running but the Epinio server is crashing? Or is it related to k3d? I don't have the possibility to run this configuration unfortunately
04/22/2023, 9:13 PM
actually, epinio pods works for a while... then when i push some apps. and create some services.. all pods start failing
I am trying to figure out if this is an issue with rancher desktop or that + arm64 (M1 pro)
something like this... for M1 on rancher desktop
just install docker desktop for M1 pro... it is better... even my neuvector pod that fails (my rancher desktop)is working M1's docker desktop.
However, i do find some problems (not really epinio isssue) in docker desktop M1. RabbitMq backing service crashes (seg fault) and mongodb times out..
Maybe they are using amd64 images in bitami's helmcharts ?
04/22/2023, 11:40 PM
I bet it is trying to run the x86_64 images via qemu. I have an M1 so will try to replicate when I have a chance!
Neuvector doesn’t have arm support (yet). And Paketo buildpacks also don’t support arm so you would have to use a custom builder (which IIRC, you do)
04/23/2023, 1:23 AM
i just install DockerDesktop in M1... now only 1 pod fails... that is ok like u said... it might not support arm.
anyway, it is very confusing what works and what does not... it rancher desktop or image that is amd64 running on arm64 etc etc
unfortunately, all our engineers is going to get arm64 machine (M2) soon... will be confusing for them when they are testing locally
btw, i install rancher desktop (moby) on my old intel mac.... and deploy neuvector, the same 2 pods that does not start in rancher desktop (moby) in M1 also did not start properly in intel based rancher desktop
I think there is also some parity difference between rancher deskop vs docker desktop. unfortunately, i am not suppose to use docker desktop becos of licensing