flaky-battery-82056
10/26/2022, 10:32 AMcool-gpu-12218
10/26/2022, 11:47 AMsalmon-london-38845
10/26/2022, 3:32 PMkubectl
and helm
seem to be working from the terminal, but the docker
command just hangs.
I tried Factory Resetting, reinstalling, using a different version of k8s and deleting the .kube folder, but I can’t seem to recover it to a working state.
Any ideas? It would be great if I didn’t have to reinstall my Mac.microscopic-megabyte-8477
10/26/2022, 4:16 PMbind
mountsflaky-battery-82056
10/26/2022, 6:53 PMbulky-memory-85762
10/27/2022, 6:00 AMminiature-doctor-7866
10/27/2022, 7:27 AMdazzling-smartphone-17242
10/27/2022, 5:27 PMprehistoric-postman-89559
10/27/2022, 9:21 PMastonishing-yacht-3529
10/27/2022, 9:46 PMnerdctl push rep_name/order-saga
INFO[0000] pushing as a reduced-platform image (application/vnd.docker.distribution.manifest.v2+json, sha256:3b1208939a7ef78e70376c2a0445cf86eedd1a929c8242b9de58894b5149620f)
manifest-sha256:3b1208939a7ef78e70376c2a0445cf86eedd1a929c8242b9de58894b5149620f: waiting |--------------------------------------|
config-sha256:b8998e7a09ce31b3e677df1a18b647f5eccb4729a7fb323612ccbe7d3eaf39da: waiting |--------------------------------------|
elapsed: 1.2 s total: 0.0 B (0.0 B/s)
FATA[0001] server message: insufficient_scope: authorization failed
miniature-advantage-69986
10/28/2022, 11:07 AMsteep-airplane-89460
10/28/2022, 1:57 PMwitty-honey-18052
10/28/2022, 5:16 PMwsl.exe --update
in powershell. That made RD start successfully, but docker ps
didn't show any workloads in wsl. Next I did a factory reset of RD, then re-enabled the ubuntu distro, and things were working again.witty-honey-18052
10/28/2022, 5:16 PMquaint-smartphone-76573
10/28/2022, 7:43 PMhttps://rancher-users.slack.com/files/U048LURN691/F048EEHRTE2/image.png▾
quick-keyboard-83126
10/28/2022, 8:20 PMkind-iron-72902
10/28/2022, 8:21 PMquick-keyboard-83126
10/28/2022, 8:26 PMquick-keyboard-83126
10/28/2022, 8:26 PMquick-keyboard-83126
10/28/2022, 8:26 PMquick-keyboard-83126
10/28/2022, 8:44 PMquick-keyboard-83126
10/28/2022, 8:44 PMquick-keyboard-83126
10/28/2022, 8:44 PMfast-garage-66093
10/28/2022, 8:45 PMkind-iron-72902
10/28/2022, 8:45 PMkind-iron-72902
10/28/2022, 8:46 PMnone
credential helper if your machine is secureswift-nest-83896
10/31/2022, 10:38 AMswift-nest-83896
10/31/2022, 11:39 AMmany-machine-56470
10/31/2022, 3:03 PMbuildx
with Rancher Desktop. The build goes fine by providing the --output=push
option but when the time comes for exporting, the following error shows up
#8 DONE 308.4s
#10 exporting to client
#10 copying files linux/amd64 42.15kB 0.0s done
#10 copying files linux/arm64 24.19kB 0.0s done
#10 ERROR: error from receiver: failed to create device push/linux_amd64/dev/console: operation not permitted
------
> exporting to client:
------
ERROR: failed to solve: error from receiver: failed to create device push/linux_amd64/dev/console: operation not permitted
This same behavior is seen when using --output=image
except that the error says failed to create device image/linux_amd64/dev/console
My machine is a MacBook Pro with an M1 Max CPU and I'm using a container registry at gitlab
Has anyone gotten buildx
to work on Ranched Desktop?purple-action-15801
10/31/2022, 3:50 PM