dgdosen

6 ms·

31.
by dgdosen 6y ago
shocking == clickbait
32.
by dgdosen 6y ago
Clarifying a bit - I can't start up the Docker Desktop Kubernetes - If I take a look at the image downloaded (docker/desktop-kubernetes) it only shows tags for amd64. When I try to spin up kubernetes, the UI just shows 'start
33.
by dgdosen 6y ago
It's been taking a while, and the kubernetes is still 'starting...' - Did you have the same issue?
34.
by dgdosen 6y ago
I just have two versions of iTerm - one started via x86_64, and one started natively as arm64. 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 of
35.
by dgdosen 6y ago
Clarifying - I think my 'processor usage' issue is from running lazydocker (and exiting). Not sure what the issue is.
36.
by dgdosen 6y ago
speed is just dependent upon the speed of the remote docker instance... and latency... for me - perf is great.
37.
by dgdosen 6y ago
I'm running docker-machine on an M1 mac right now (via rosetta), installed via homebrew.
38.
by dgdosen 6y ago
Similarly, I installed docker-machine and docker (via Homebrew) on my M1 mac via Rosetta 2, and connect to a remote docker host, similar in configuration to this blog post (which really has a misleading title). That works - but it pegs proc
39.
by dgdosen 6y ago
Seemed to work fine for me... I'm now trying to install both versions of brew and spin up terminal sessions accordingly. Are these 'good practices' for Arm Macs?: 1) When spinning up an iTerm session, figure out if it's
40.
by dgdosen 6y ago
Just wondering - what doesn't run? Or what popular software isn't compiled to run on aarch64?
41.
by dgdosen 9y ago
I too, would like a good answer to this. My gut says that (other than VMWare) the Macbook would be fine. You'd probably get a bit better battery life and performance out of the non-y chips, but IMO, nothing significant. I see a Kaby