55 karma · joined May 21, 2016
When I try to spin up kubernetes, the UI just shows 'starting...' while the logs show the image won't work with this architecture.
Anyone else see this? Any workaround?
For now, I'm mostly using Rosetta2 for running iTerm. It works great. I do fine sluggishness on some initial builds, but then it's off to the races.
for me - perf is great.
That works - but it pegs processor usage on the M1 mac...
Are these 'good practices' for Arm Macs?:
1) When spinning up an iTerm session, figure out if it's 'Darwin x86_64' or 'Darwin arm64' - and configure paths accordingly. so they use the right brew binaries.
2) Easily double check what version of a running package/keg based on what arch is displayed in Activity Monitor.
3) That way, you can just use brew with Rosetta to start (which I did) then build up native arm Brew over time. and let the Rosetta brew fall away.