https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
q
How do I get rancher to let me run the amd64 instead of arm64 image?
f
Specify 
--platform linux/amd64
in your docker/nerdctl run command
If you are talking about k8s, then you can't. 
kubelet
will only run images of the same architecture as itself. I have some ideas on running a second k8s node with a different architecture in a container, but not sure if/when we would get around to looking at this idea. Probably not until after adding support for Virtualization Framework and Rosetta2, which should become an options in the next quarter.
q
I'm not using k8s. This is just docker run. I did a docker pull and now it's poisoned with the arm image. Even though had I not, I'd be able to use docker run --platform linux/amd64.
f
It seems to work for me; is this not what you want:
Copy code
$ uname -a
Darwin studio 22.2.0 Darwin Kernel Version 22.2.0: Fri Nov 11 02:03:51 PST 2022; root:xnu-8792.61.2~4/RELEASE_ARM64_T6000 arm64

$ docker run --platform linux/arm64 busybox uname -a
Unable to find image 'busybox:latest' locally
latest: Pulling from library/busybox
b2bcf7a3443b: Pull complete
Digest: sha256:3b3128d9df6bbbcc92e2358e596c9fbd722a437a62bafbc51607970e9e3b8869
Status: Downloaded newer image for busybox:latest
Linux c3763bbf1eb5 5.15.78-0-virt #1-Alpine SMP Fri, 11 Nov 2022 10:19:45 +0000 aarch64 GNU/Linux

$ docker run --platform linux/amd64 busybox uname -a
Unable to find image 'busybox:latest' locally
latest: Pulling from library/busybox
45a0cdc5c8d3: Pull complete
Digest: sha256:3b3128d9df6bbbcc92e2358e596c9fbd722a437a62bafbc51607970e9e3b8869
Status: Downloaded newer image for busybox:latest
Linux cb52a5429efe 5.15.78-0-virt #1-Alpine SMP Fri, 11 Nov 2022 10:19:45 +0000 x86_64 GNU/Linux
q
I'm not by the computer atm...
f
It is possible that the 
amd64
image simply doesn't run with 
qemu-static-x86_64
emulation, but if it does, then this is the way to request them
q
I can definitely run amd64 and arm64
It has something to do w/ gcr's 
@sha
notation confusing docker `it has something to do with gcr and having two images for the same
If i reset rancher from scratch i can switch which image i can use
and then i'm stuck w/ it until reset rancher again...
f
If there is a public image that can be used to repro this, then please file a bug.
q
Sadly, the image is something we made for my employer, but i suspect it's related to gcr, so i probably should be able to construct a thing for it
3 Views
Open in Slack
PreviousNext
Powered by