Hey guys, do you think It's possible to run pulumi...
# general
m
Hey guys, do you think It's possible to run pulumi-kubernetes-operator on apple (with M2)? I have following logs: exec /usr/bin/tini: exec format error │ │ Stream closed EOF for lunacrafts-labs/lunacrafts-labs-pulumi-kubernetes-operator-c1945de1-6b668cpktvj (pulumi-kubernetes-operator) This issue indicates issues with processor architecture https://github.com/pulumi/pulumi-kubernetes-operator/issues/430
f
it's still in progress and reliant on https://github.com/pulumi/pulumi-kubernetes-operator/issues/515 at this point
šŸ™Œ 1
m
So just to confirm, It's not really possible to run this operator? No workarounds for this one?
šŸ‘€ 1
f
yeah, hangon, those issues are for the images - what command exactly are you running that is giving that error message?
b
@mammoth-gold-93338 I've got the operator running on Kind on my M3 mac. I'm running the images from docker hub (without any alpha tags) so it's definitely running the amd64 version. How were you deploying the operator (yaml/helm/pulumi)?
m
Hey Piers. I use those yamls https://github.com/pulumi/pulumi-kubernetes-operator/tree/master/deploy/yaml However it doesn't seems like image incompatibility, image seems to be pulled correctly. But a package within seems to be broken. exec /usr/bin/tini: exec format error I recall now, I had exact same issue with rook-ceph-toolbox. Broken package was different, but error was literally the same.
b
How are you running k8s on your laptop? I’m wondering if whatever you're using is trying to run the container as an
arm64
one
m
I run on minikube:
Copy code
#!/bin/sh

current_dir=$(pwd)

minikube start --memory=max \
  --cpus=max \
  --disk-size=20g \
  --extra-disks 1 \
  --driver qemu \
  --mount \
  --mount-string="${current_dir}:/mirrorboards" \
  --extra-config=controller-manager.cluster-signing-cert-file=/var/lib/minikube/certs/ca.crt \
  --extra-config=controller-manager.cluster-signing-key-file=/var/lib/minikube/certs/ca.key
I guess it must be this qemu driver. I'm redeploying it without it right now. Honestly I don't know why I've got it there, It was just recommended by rook-ceph guys.
That was it... It's working now
b
A quick google suggests this issue from a couple of years ago (that doesn't look like it's been fixed) suggests that minikube with qemu runs with the same architecture as the underlying OS: https://github.com/kubernetes/minikube/issues/14206
šŸ™ 1
But if you set
GOARCH
to be
amd64
when running minikube, that might work ĀÆ\_(惄)_/ĀÆ
But also, if you don't need qemu and it's working then that's also a win
m
Yeah I'll try to go without it, hopefully rook-ceph will still work, otherwise I'm gonna try this GOARCH flag. Thanks for your support guys, this kubernetes stuff is complicated sometimes
b
That it is šŸ™‚