This message was deleted.
# rancher-desktop
a
This message was deleted.
h
You may need to quit and restart your terminal to update the PATH variable to point to the new links or reference your .bash_profile for the correct 'export' command.
As far as your Containers tab, you could try a 'Troubleshooting/Factory Reset' if you're not worried about losing any configuration. If it still hangs after that, you can try 'Troubleshooting/Logs/Enable debug mode', then we can look at your logs...
w
and rancher includes a docker-cli binary so you can keep all your docker syntax once you confirm that PATH is correct
just make sure you set in RD prefs to use moby instead of containerd
now your "old" containers were spawned from images stored in Docker Desktop I assume? did you export the images or push them into a registry somewhere?
RD has its own VM and image cache so they won't magic over from the Docker Desktop image cache?
👍 1
m
Thanks for all of your comments, Guys. @handsome-jewelry-53515 - I’ve got the ‘automatically update your PATH’ set so hopings that it’s done that right! Also, tried a ‘Factory Reset’ but it makes no diff. I’ve completely disabled K8s as I’m not using it in this case. The ‘Starting virtual machine’ seems to hang. @wide-mechanic-33041 - Yep, I’d already set it to Moby. See screenshots below. How would I access the docker-cli binary? What folder would it be in so’s I can cdheck my path variable? I can easily recreate the images (or download them) - not sure where docker had stored them, didn’t pay too much attention to that. Here’s the ‘Show Logs’: 2023-11-09T104536.534Z: mainEvents settings-update: {“version”10,“application”{“adminAccess”false,“debug”false,“extensions”{“allowed”{“enabled”false,“list”[]},“installed”{}},“pathManagementStrategy”“rcfiles”,“telemetry”{“enabled”true},“updater”{“enabled”true},“autoStart”false,“startInBackground”false,“hideNotificationIcon”false,“window”{“quitOnClose”false}},“containerEngine”{“allowedImages”{“enabled”false,“patterns”[]},“name”“moby”},“virtualMachine”{“memoryInGB”6,“numberCPUs”2,“hostResolver”true},“WSL”{“integrations”{}},“kubernetes”{“version”“”,“port”6443,“enabled”true,“options”{“traefik”true,“flannel”true},“ingress”{“localhostOnly”false}},“portForwarding”{“includeKubernetesServices”false},“images”{“showAll”true,“namespace”“k8s.io”},“diagnostics”{“showMuted”false,“mutedChecks”{}},“experimental”{“virtualMachine”{“type”“qemu”,“useRosetta”false,“socketVMNet”false,“mount”{“type”“reverse-sshfs”,“9p”{“securityModel”“none”,“protocolVersion”“9p2000.L”,“msizeInKib”128,“cacheMode”“mmap”}},“networkingTunnel”false,“proxy”{“enabled”false,“address”“”,“password”“”,“port”3128,“username”“”,“noproxy”:[“0.0.0.0/8",“10.0.0.0/8”,“127.0.0.0/8",“169.254.0.0/16”,“172.16.0.0/12",“192.168.0.0/16”,“224.0.0.0/4",“240.0.0.0/4”]}}}} 2023-11-09T104539.399Z: UnhandledRejectionWarning: [Error: ENOENT: no such file or directory, open ‘/Users/russellwebb/Library/Caches/rancher-desktop/updater-longhorn.json’] { errno: -2, code: ‘ENOENT’, syscall: ‘open’, path: ‘/Users/russellwebb/Library/Caches/rancher-desktop/updater-longhorn.json’ } 2023-11-09T104554.472Z: Still processing the first-run dialog: not opening main window 2023-11-09T104604.711Z: mainEvents settings-update: {“version”10,“application”{“adminAccess”false,“debug”false,“extensions”{“allowed”{“enabled”false,“list”[]},“installed”{}},“pathManagementStrategy”“rcfiles”,“telemetry”{“enabled”true},“updater”{“enabled”true},“autoStart”false,“startInBackground”false,“hideNotificationIcon”false,“window”{“quitOnClose”false}},“containerEngine”{“allowedImages”{“enabled”false,“patterns”[]},“name”“moby”},“virtualMachine”{“memoryInGB”6,“numberCPUs”2,“hostResolver”true},“WSL”{“integrations”{}},“kubernetes”{“version”“”,“port”6443,“enabled”false,“options”{“traefik”true,“flannel”true},“ingress”{“localhostOnly”false}},“portForwarding”{“includeKubernetesServices”false},“images”{“showAll”true,“namespace”“k8s.io”},“diagnostics”{“showMuted”false,“mutedChecks”{}},“experimental”{“virtualMachine”{“type”“qemu”,“useRosetta”false,“socketVMNet”false,“mount”{“type”“reverse-sshfs”,“9p”{“securityModel”“none”,“protocolVersion”“9p2000.L”,“msizeInKib”128,“cacheMode”“mmap”}},“networkingTunnel”false,“proxy”{“enabled”false,“address”“”,“password”“”,“port”3128,“username”“”,“noproxy”:[“0.0.0.0/8”,“10.0.0.0/8",“127.0.0.0/8”,“169.254.0.0/16",“172.16.0.0/12”,“192.168.0.0/16",“224.0.0.0/4”,“240.0.0.0/4"]}}}} 2023-11-09T104618.289Z: mainEvents settings-update: {“version”10,“application”{“adminAccess”false,“debug”false,“extensions”{“allowed”{“enabled”false,“list”[]},“installed”{}},“pathManagementStrategy”“rcfiles”,“telemetry”{“enabled”true},“updater”{“enabled”true},“autoStart”false,“startInBackground”false,“hideNotificationIcon”false,“window”{“quitOnClose”false}},“containerEngine”{“allowedImages”{“enabled”false,“patterns”[]},“name”“moby”},“virtualMachine”{“memoryInGB”6,“numberCPUs”2,“hostResolver”true},“WSL”{“integrations”{}},“kubernetes”{“version”“1.27.7”,“port”6443,“enabled”false,“options”{“traefik”true,“flannel”true},“ingress”{“localhostOnly”false}},“portForwarding”{“includeKubernetesServices”false},“images”{“showAll”true,“namespace”“k8s.io”},“diagnostics”{“showMuted”false,“mutedChecks”{}},“experimental”{“virtualMachine”{“type”“qemu”,“useRosetta”false,“socketVMNet”false,“mount”{“type”“reverse-sshfs”,“9p”{“securityModel”“none”,“protocolVersion”“9p2000.L”,“msizeInKib”128,“cacheMode”“mmap”}},“networkingTunnel”false,“proxy”{“enabled”false,“address”“”,“password”“”,“port”3128,“username”“”,“noproxy”:[“0.0.0.0/8",“10.0.0.0/8”,“127.0.0.0/8",“169.254.0.0/16”,“172.16.0.0/12",“192.168.0.0/16”,“224.0.0.0/4",“240.0.0.0/4”]}}}} 2023-11-09T104618.414Z: mainEvents settings-update: {“version”10,“application”{“adminAccess”false,“debug”false,“extensions”{“allowed”{“enabled”false,“list”[]},“installed”{}},“pathManagementStrategy”“rcfiles”,“telemetry”{“enabled”true},“updater”{“enabled”true},“autoStart”false,“startInBackground”false,“hideNotificationIcon”false,“window”{“quitOnClose”false}},“containerEngine”{“allowedImages”{“enabled”false,“patterns”[]},“name”“moby”},“virtualMachine”{“memoryInGB”6,“numberCPUs”2,“hostResolver”true},“WSL”{“integrations”{}},“kubernetes”{“version”“1.27.7",“port”6443,“enabled”false,“options”{“traefik”true,“flannel”true},“ingress”{“localhostOnly”false}},“portForwarding”{“includeKubernetesServices”false},“images”{“showAll”true,“namespace”“k8s.io”},“diagnostics”{“showMuted”false,“mutedChecks”{}},“experimental”{“virtualMachine”{“type”“qemu”,“useRosetta”false,“socketVMNet”false,“mount”{“type”“reverse-sshfs”,“9p”{“securityModel”“none”,“protocolVersion”“9p2000.L”,“msizeInKib”128,“cacheMode”“mmap”}},“networkingTunnel”false,“proxy”{“enabled”false,“address”“”,“password”“”,“port”3128,“username”“”,“noproxy”:[“0.0.0.0/8”,“10.0.0.0/8",“127.0.0.0/8”,“169.254.0.0/16",“172.16.0.0/12”,“192.168.0.0/16",“224.0.0.0/4”,“240.0.0.0/4"]}}}} 2023-11-09T104618.620Z: UnhandledRejectionWarning: Error: ENOENT: no such file or directory, watch ‘/Users/russellwebb/.kube/config’ at FSWatcher.<computed> (nodeinternal/fs/watchers244:19) at Object.watch (nodefs2264:34) at /Applications/Rancher Desktop.app/Contents/Resources/app.asar/dist/app/background.js:41:107277 at Array.map (<anonymous>) at ao.watchForChanges (/Applications/Rancher Desktop.app/Contents/Resources/app.asar/dist/app/background.js:41:107265) { errno: -2, syscall: ‘watch’, code: ‘ENOENT’, path: ‘/Users/russellwebb/.kube/config’, filename: ‘/Users/russellwebb/.kube/config’ } Here’s my $PATH variable: russellwebb@SAG-CNF9MTP2X4 ~ % echo $PATH /Users/russellwebb/.rd/bin/Users/russellwebb/.pyenv/shims/opt/homebrew/bin/opt/homebrew/sbin/usr/local/bin/System/Cryptexes/App/usr/bin/usr/bin/bin/usr/sbin/sbin/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Applications/VMware Fusion Tech Preview.app/Contents/Public:/Users/russellwebb/Desktop/kafka_2.13-3.3.1/bin:/Users/russellwebb/Documents/Spark/bin russellwebb@SAG-CNF9MTP2X4 ~ %
I can’t see rancher in the PATH! That was with opening a new iTerm. Ah, but…docker can be seen!
…..and the cli docker command runs now. Ha! That’s cos rd IS in the PATH. I see it now.
I think the log still seems to be trying to get K8s to run!! It’s looking for kubectls’ config file!? Error: ENOENT: no such file or directory, watch ‘/Users/russellwebb/.kube/config’
I’m now trying to run docker in the way I used to: russellwebb@SAG-CNF9MTP2X4 ~ % docker run -d -e http_proxy= -e https_proxy= -e STREAMSETS_DEPLOYMENT_SCH_URL=https://eu01.hub.streamsets.com -e STREAMSETS_DEPLOYMENT_ID=32b43f18-bb78-4d15-837b-0ac45aafa218:2c8340d4-fe0a-11ec-aea6-d72c58a19f4d -e STREAMSETS_DEPLOYMENT_TOKEN=eyJ0eXAiOiJKV1QiLCJhbGciOiJub25lIn0.eyJzIjoiNTcxZjdjNjFhZDQ2OGY2YmUwNGNmMWEzYzc1ODMzMzA1YjEwNTQzMmNmYTdhZTYwZTUxM2NiMGU5ODJiMWM0OTM5NDQzZjI0NDQ2YzZiZTU5ODEyMTFkNGJhOGUwZGE4YmQ0YzAzOWMwNjY4OWZhMjhlNzg2NDAwYzcyYWI2MTMiLCJ2IjoxLCJpc3MiOiJldTAxIiwianRpIjoiNTkzZDU1YTYtMGU1Yy00YzMzLWIxNzgtNmNjYjlkOTlkZTgzIiwibyI6IjJjODM0MGQ0LWZlMGEtMTFlYy1hZWE2LWQ3MmM1OGExOWY0ZCJ9. -e ENGINE_SHUTDOWN_TIMEOUT=10 streamsets/datacollector:5.7.1 docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?. See ‘docker run --help’. but it seems to be looking for the docker daemon itself!?
w
well it needs to connect to the socket which sends traffic into the linux VM hosting dockerd. you mentioned you are on moby already. what does docker info show?
m
russellwebb@SAG-CNF9MTP2X4 ~ % docker info Client: Version: 24.0.6-rd Context: default Debug Mode: false Plugins: buildx: Docker Buildx (Docker Inc.) Version: v0.11.2 Path: /Users/russellwebb/.docker/cli-plugins/docker-buildx compose: Docker Compose (Docker Inc.) Version: v2.22.0 Path: /Users/russellwebb/.docker/cli-plugins/docker-compose WARNING: Plugin “/Users/russellwebb/.docker/cli-plugins/docker-dev” is not valid: failed to fetch metadata: fork/exec /Users/russellwebb/.docker/cli-plugins/docker-dev: no such file or directory WARNING: Plugin “/Users/russellwebb/.docker/cli-plugins/docker-extension” is not valid: failed to fetch metadata: fork/exec /Users/russellwebb/.docker/cli-plugins/docker-extension: no such file or directory WARNING: Plugin “/Users/russellwebb/.docker/cli-plugins/docker-init” is not valid: failed to fetch metadata: fork/exec /Users/russellwebb/.docker/cli-plugins/docker-init: no such file or directory WARNING: Plugin “/Users/russellwebb/.docker/cli-plugins/docker-sbom” is not valid: failed to fetch metadata: fork/exec /Users/russellwebb/.docker/cli-plugins/docker-sbom: no such file or directory WARNING: Plugin “/Users/russellwebb/.docker/cli-plugins/docker-scan” is not valid: failed to fetch metadata: fork/exec /Users/russellwebb/.docker/cli-plugins/docker-scan: no such file or directory WARNING: Plugin “/Users/russellwebb/.docker/cli-plugins/docker-scout” is not valid: failed to fetch metadata: fork/exec /Users/russellwebb/.docker/cli-plugins/docker-scout: no such file or directory Server: ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? errors pretty printing info russellwebb@SAG-CNF9MTP2X4 ~ %
w
so looks like DD left some bits around the file system. may need to clean those up manually. does your ~/.rd/bin/docker show up in your PATH? is the docker binaries in ~/.rd showing up when you do a
which docker
?
m
yes it does (see above).
w
do you see the context change after RD starts up?
docker context ls
should point at *`rancher-desktop * Rancher Desktop moby context unix:///Users/user/.rd/docker.sock`*
m
Aha! I get this: russellwebb@SAG-CNF9MTP2X4 ~ % docker context ls NAME DESCRIPTION DOCKER ENDPOINT ERROR default * Current DOCKER_HOST based configuration unix:///var/run/docker.sock desktop-linux Docker Desktop unix:///Users/russellwebb/.docker/run/docker.sock russellwebb@SAG-CNF9MTP2X4 ~ %
How do I change it?
This is still trying to start up K8s !!? No idea why! I don’t need k8s! After 15 mins of it hanging like this:
it gives this: