mooneye14
commented
2 years ago Getting the same
Closed ahmetb closed 2 years ago
mooneye14
commented
2 years ago Getting the same
jandubois
commented
2 years ago Could you please verify that this is not a duplicate of #535:
$ id
uid=501(jan) gid=20(staff) groups=20(staff), [...]If your uid is larger than 256000 (which can happen when the ids are assigned by a directory service), then you are hitting a known issue that has already been fixed for the next release.
If this is not the problem, then please attach the lime log files:
$ ls ~/Library/State/rancher-desktop/lima/rancher-desktop/*.log
/Users/jan/Library/State/rancher-desktop/lima/rancher-desktop/ha.stderr.log
/Users/jan/Library/State/rancher-desktop/lima/rancher-desktop/ha.stdout.log
/Users/jan/Library/State/rancher-desktop/lima/rancher-desktop/serial.log
mpptx
commented
2 years ago Same issue. My uid is 501.
~/Library/State/rancher-desktop/lima/rancher-desktop/ha.stderr.log:
{"level":"info","msg":"Starting QEMU (hint: to watch the boot progress, see \"/Users/user/Library/State/rancher-desktop/lima/rancher-desktop/serial.log\")","time":"2021-09-01T15:49:39+02:00"}
{"level":"debug","msg":"qCmd.Args: [/Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/bin/qemu-system-x86_64 -cpu Haswell-v4 -machine q35,accel=hvf -smp 2,sockets=1,cores=2,threads=1 -m 4096 -boot order=d,splash-time=0,menu=on -drive file=/Users/user/Library/State/rancher-desktop/lima/rancher-desktop/basedisk,media=cdrom,readonly=on -drive file=/Users/user/Library/State/rancher-desktop/lima/rancher-desktop/diffdisk,if=virtio -cdrom /Users/user/Library/State/rancher-desktop/lima/rancher-desktop/cidata.iso -netdev user,id=net0,net=192.168.5.0/24,dhcpstart=192.168.5.15,hostfwd=tcp:127.0.0.1:62191-:22 -device virtio-net-pci,netdev=net0,mac=52:55:55:fa:8e:a5 -device virtio-rng-pci -display none -device virtio-vga -device virtio-keyboard-pci -device virtio-mouse-pci -parallel none -chardev socket,id=char-serial,path=/Users/user/Library/State/rancher-desktop/lima/rancher-desktop/serial.sock,server,nowait,logfile=/Users/user/Library/State/rancher-desktop/lima/rancher-desktop/serial.log -serial chardev:char-serial -chardev socket,id=char-qmp,path=/Users/user/Library/State/rancher-desktop/lima/rancher-desktop/qmp.sock,server,nowait -qmp chardev:char-qmp -name lima-rancher-desktop -pidfile /Users/user/Library/State/rancher-desktop/lima/rancher-desktop/qemu.pid]","time":"2021-09-01T15:49:39+02:00"}
{"level":"info","msg":"Waiting for the essential requirement 1 of 4: \"ssh\"","time":"2021-09-01T15:49:39+02:00"}
{"level":"debug","msg":"executing script \"ssh\"","time":"2021-09-01T15:49:39+02:00"}
{"level":"debug","msg":"stdout=\"\", stderr=\"ssh: connect to host 127.0.0.1 port 62191: Connection refused\\r\\n\", err=failed to execute script \"ssh\": stdout=\"\", stderr=\"ssh: connect to host 127.0.0.1 port 62191: Connection refused\\r\\n\": exit status 255","time":"2021-09-01T15:49:39+02:00"}
{"level":"debug","msg":"qemu[stderr]: qemu-system-x86_64: -chardev socket,id=char-serial,path=/Users/user/Library/State/rancher-desktop/lima/rancher-desktop/serial.sock,server,nowait,logfile=/Users/user/Library/State/rancher-desktop/lima/rancher-desktop/serial.log: warning: short-form boolean option 'server' deprecated","time":"2021-09-01T15:49:41+02:00"}
{"level":"debug","msg":"qemu[stderr]: Please use server=on instead","time":"2021-09-01T15:49:41+02:00"}
{"level":"debug","msg":"qemu[stderr]: qemu-system-x86_64: -chardev socket,id=char-serial,path=/Users/user/Library/State/rancher-desktop/lima/rancher-desktop/serial.sock,server,nowait,logfile=/Users/user/Library/State/rancher-desktop/lima/rancher-desktop/serial.log: warning: short-form boolean option 'nowait' deprecated","time":"2021-09-01T15:49:41+02:00"}
{"level":"debug","msg":"qemu[stderr]: Please use wait=off instead","time":"2021-09-01T15:49:41+02:00"}
{"error":"signal: abort trap","level":"info","msg":"QEMU has exited","time":"2021-09-01T15:49:41+02:00"}
{"level":"debug","msg":"qemu[stderr]: qemu-system-x86_64: -chardev socket,id=char-qmp,path=/Users/user/Library/State/rancher-desktop/lima/rancher-desktop/qmp.sock,server,nowait: warning: short-form boolean option 'server' deprecated","time":"2021-09-01T15:49:41+02:00"}
{"level":"debug","msg":"qemu[stderr]: Please use server=on instead","time":"2021-09-01T15:49:41+02:00"}
signal: abort trap~/Library/State/rancher-desktop/lima/rancher-desktop/ha.stdout.log:
{"time":"2021-09-01T15:49:39.703442+02:00","status":{"sshLocalPort":62191}}
{"time":"2021-09-01T15:49:41.557688+02:00","status":{"exiting":true}}~/Library/State/rancher-desktop/lima/rancher-desktop/serial.log:
(file is empty)My uid is 503 and this is on a Macbook 13" 2019 Core i5:
willie
commented
2 years ago Same error and user id as @mooneye14
jandubois
commented
2 years ago @mpptx This looks similar to #532, which we couldn't figure out because the error suddenly went away.
There are several instructions to run lima and qemu on their own, and to try different CPU settings. Could you see if any of that applies to your setup?
@mooneye14 You logs look different, and I'm still working through them, but there is most likely no point in performing the steps from #532. I'll update if I have further ideas...
jandubois
commented
2 years ago @mooneye14 Your logs very much look like the error in #535, but since your uid is less than 256000, the error must be something different.
For the following check you need the socat utility; if you are using brew then you can install it via brew install socat.
Your VM seems to be running, and the SSH daemon is listening on the port, but rejects your key. Since we can't connect via ssh we need to establish a connection via (virtual) serial port. You will not get a prompt when socat connects, but the terminal is waiting for you to enter a username. Just type root↩. Then you have a shell prompt. Ignore the incorrect control sequences. Run cat /mnt/lima-cidata/user-data and share the output. On my (working) setup it looks like this:
$ socat stdio ~/Library/State/rancher-desktop/lima/rancher-desktop/serial.sock
root
root
Welcome to Alpine!
The Alpine Wiki contains a large amount of how-to guides and general
information about administrating Alpine systems.
See <http://wiki.alpinelinux.org/>.
You can setup the system with the command: setup-alpine
You may change this message by editing /etc/motd.
lima-rancher-desktop:~# ^[[60;25Rcat /mnt/lima-cidata/user-data
cat /mnt/lima-cidata/user-data
#cloud-config
# vim:syntax=yaml
growpart:
mode: auto
devices: ['/']
users:
- name: "jan"
uid: "501"
homedir: "/home/jan.linux"
shell: /bin/bash
sudo: ALL=(ALL) NOPASSWD:ALL
lock_passwd: true
ssh-authorized-keys:
- ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIFGNCQ9U3k8ErTkhLHJP+8bCgvi56GJshb6q0cdhWKHw jan@mactop
[...]The ssh-authorized-keys value should be this public key from your host:
$ cat ~/Library/State/rancher-desktop/lima/_config/user.pub
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIFGNCQ9U3k8ErTkhLHJP+8bCgvi56GJshb6q0cdhWKHw jan@mactopSince it is a public key, it is safe to share it. If you have concerns, you can delete the key files on the host and Rancher Desktop will generate a new one on the next start.
While you are still connected via socat you can also run cat /home/*/.ssh/authorized_keys. It should print the same key value:
lima-rancher-desktop:~# ^[[60;25Rcat /home/*/.ssh/authorized_keys
cat /home/*/.ssh/authorized_keys
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIFGNCQ9U3k8ErTkhLHJP+8bCgvi56GJshb6q0cdhWKHw jan@mactopFinally, please capture the output of cat /var/log/lima-init.log as well, just in case the user-data doesn't have enough information to show what went wrong.
spurin
commented
2 years ago To add to the thread, I'm also seeing this on a recently fresh/new version of Big Sur on Mac M1. Please let me know if you'd like any logs or further steps carried out for troubleshooting purposes. My id is 502, here's the log output -
~/Library/State/rancher-desktop/lima/rancher-desktop/ha.stderr.log:
james@MacMini ~ % cat ~/Library/State/rancher-desktop/lima/rancher-desktop/ha.stderr.log
{"level":"info","msg":"Starting QEMU (hint: to watch the boot progress, see \"/Users/james/Library/State/rancher-desktop/lima/rancher-desktop/serial.log\")","time":"2021-09-03T11:35:47+01:00"}
{"level":"debug","msg":"qCmd.Args: [/Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/bin/qemu-system-x86_64 -cpu Haswell-v4 -machine q35,accel=hvf -smp 2,sockets=1,cores=2,threads=1 -m 4096 -boot order=d,splash-time=0,menu=on -drive file=/Users/james/Library/State/rancher-desktop/lima/rancher-desktop/basedisk,media=cdrom,readonly=on -drive file=/Users/james/Library/State/rancher-desktop/lima/rancher-desktop/diffdisk,if=virtio -cdrom /Users/james/Library/State/rancher-desktop/lima/rancher-desktop/cidata.iso -netdev user,id=net0,net=192.168.5.0/24,dhcpstart=192.168.5.15,hostfwd=tcp:127.0.0.1:61857-:22 -device virtio-net-pci,netdev=net0,mac=52:55:55:32:51:6c -device virtio-rng-pci -display none -device virtio-vga -device virtio-keyboard-pci -device virtio-mouse-pci -parallel none -chardev socket,id=char-serial,path=/Users/james/Library/State/rancher-desktop/lima/rancher-desktop/serial.sock,server,nowait,logfile=/Users/james/Library/State/rancher-desktop/lima/rancher-desktop/serial.log -serial chardev:char-serial -chardev socket,id=char-qmp,path=/Users/james/Library/State/rancher-desktop/lima/rancher-desktop/qmp.sock,server,nowait -qmp chardev:char-qmp -name lima-rancher-desktop -pidfile /Users/james/Library/State/rancher-desktop/lima/rancher-desktop/qemu.pid]","time":"2021-09-03T11:35:47+01:00"}
{"level":"info","msg":"Waiting for the essential requirement 1 of 4: \"ssh\"","time":"2021-09-03T11:35:47+01:00"}
{"level":"debug","msg":"executing script \"ssh\"","time":"2021-09-03T11:35:47+01:00"}
{"level":"debug","msg":"stdout=\"\", stderr=\"ssh: connect to host 127.0.0.1 port 61857: Connection refused\\r\\n\", err=failed to execute script \"ssh\": stdout=\"\", stderr=\"ssh: connect to host 127.0.0.1 port 61857: Connection refused\\r\\n\": exit status 255","time":"2021-09-03T11:35:48+01:00"}
{"level":"debug","msg":"qemu[stderr]: qemu-system-x86_64: -chardev socket,id=char-serial,path=/Users/james/Library/State/rancher-desktop/lima/rancher-desktop/serial.sock,server,nowait,logfile=/Users/james/Library/State/rancher-desktop/lima/rancher-desktop/serial.log: warning: short-form boolean option 'server' deprecated","time":"2021-09-03T11:35:48+01:00"}
{"level":"debug","msg":"qemu[stderr]: Please use server=on instead","time":"2021-09-03T11:35:48+01:00"}
{"level":"debug","msg":"qemu[stderr]: qemu-system-x86_64: -chardev socket,id=char-serial,path=/Users/james/Library/State/rancher-desktop/lima/rancher-desktop/serial.sock,server,nowait,logfile=/Users/james/Library/State/rancher-desktop/lima/rancher-desktop/serial.log: warning: short-form boolean option 'nowait' deprecated","time":"2021-09-03T11:35:48+01:00"}
{"level":"debug","msg":"qemu[stderr]: Please use wait=off instead","time":"2021-09-03T11:35:48+01:00"}
{"level":"debug","msg":"qemu[stderr]: qemu-system-x86_64: -chardev socket,id=char-qmp,path=/Users/james/Library/State/rancher-desktop/lima/rancher-desktop/qmp.sock,server,nowait: warning: short-form boolean option 'server' deprecated","time":"2021-09-03T11:35:48+01:00"}
{"level":"debug","msg":"qemu[stderr]: Please use server=on instead","time":"2021-09-03T11:35:48+01:00"}
{"error":"signal: abort trap","level":"info","msg":"QEMU has exited","time":"2021-09-03T11:35:48+01:00"}
{"level":"debug","msg":"qemu[stderr]: qemu-system-x86_64: -chardev socket,id=char-qmp,path=/Users/james/Library/State/rancher-desktop/lima/rancher-desktop/qmp.sock,server,nowait: warning: short-form boolean option 'nowait' deprecated","time":"2021-09-03T11:35:48+01:00"}
{"level":"debug","msg":"qemu[stderr]: Please use wait=off instead","time":"2021-09-03T11:35:48+01:00"}
signal: abort trap~/Library/State/rancher-desktop/lima/rancher-desktop/ha.stdout.log
james@MacMini ~ % cat ~/Library/State/rancher-desktop/lima/rancher-desktop/ha.stdout.log
{"time":"2021-09-03T11:35:47.932889+01:00","status":{"sshLocalPort":61857}}
{"time":"2021-09-03T11:35:48.215792+01:00","status":{"exiting":true}}~/Library/State/rancher-desktop/lima/rancher-desktop/serial.log (is empty)
pulberg
commented
2 years ago 2019 Intel Core i9 MBP
lima-rancher-desktop:~# ^[[60;25Rcat /home/*/.ssh/authorized_keys
cat /home/*/.ssh/authorized_keys
cat: can't open '/home/*/.ssh/authorized_keys': No such file or directory{"level":"debug","msg":"qemu[stderr]: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.x2apic [bit 21]","time":"2021-09-03T15:16:50-05:00"}
{"level":"debug","msg":"qemu[stderr]: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.tsc-deadline [bit 24]","time":"2021-09-03T15:16:50-05:00"}
{"level":"debug","msg":"qemu[stderr]: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]","time":"2021-09-03T15:16:50-05:00"}
{"level":"debug","msg":"qemu[stderr]: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EDX.spec-ctrl [bit 26]","time":"2021-09-03T15:16:50-05:00"}
{"level":"debug","msg":"qemu[stderr]: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:EDX.rdtscp [bit 27]","time":"2021-09-03T15:16:50-05:00"}
{"level":"debug","msg":"qemu[stderr]: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.x2apic [bit 21]","time":"2021-09-03T15:16:50-05:00"}
{"level":"debug","msg":"qemu[stderr]: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.tsc-deadline [bit 24]","time":"2021-09-03T15:16:50-05:00"}
{"level":"debug","msg":"qemu[stderr]: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]","time":"2021-09-03T15:16:50-05:00"}
{"level":"debug","msg":"qemu[stderr]: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EDX.spec-ctrl [bit 26]","time":"2021-09-03T15:16:50-05:00"}
{"level":"debug","msg":"qemu[stderr]: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:EDX.rdtscp [bit 27]","time":"2021-09-03T15:16:50-05:00"}
{"level":"debug","msg":"qemu[stderr]: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.x2apic [bit 21]","time":"2021-09-03T15:16:50-05:00"}
{"level":"debug","msg":"qemu[stderr]: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.tsc-deadline [bit 24]","time":"2021-09-03T15:16:51-05:00"}
{"level":"debug","msg":"qemu[stderr]: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]","time":"2021-09-03T15:16:51-05:00"}
{"level":"debug","msg":"qemu[stderr]: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EDX.spec-ctrl [bit 26]","time":"2021-09-03T15:16:51-05:00"}
{"level":"debug","msg":"qemu[stderr]: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:EDX.rdtscp [bit 27]","time":"2021-09-03T15:16:51-05:00"}
{"level":"debug","msg":"qemu[stderr]: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.x2apic [bit 21]","time":"2021-09-03T15:16:51-05:00"}
{"level":"debug","msg":"qemu[stderr]: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.tsc-deadline [bit 24]","time":"2021-09-03T15:16:51-05:00"}
{"level":"debug","msg":"qemu[stderr]: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]","time":"2021-09-03T15:16:51-05:00"}
{"level":"debug","msg":"qemu[stderr]: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EDX.spec-ctrl [bit 26]","time":"2021-09-03T15:16:51-05:00"}
{"level":"debug","msg":"qemu[stderr]: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:EDX.rdtscp [bit 27]","time":"2021-09-03T15:16:51-05:00"}
{"level":"info","msg":"Waiting for the essential requirement 1 of 4: \"ssh\"","time":"2021-09-03T15:17:00-05:00"}
{"level":"debug","msg":"executing script \"ssh\"","time":"2021-09-03T15:17:00-05:00"}
{"level":"debug","msg":"stdout=\"\", stderr=\"kex_exchange_identification: Connection closed by remote host\\r\\n\", err=failed to execute script \"ssh\": stdout=\"\", stderr=\"kex_exchange_identification: Connection closed by remote host\\r\\n\": exit status 255","time":"2021-09-03T15:17:00-05:00"}
{"level":"info","msg":"Waiting for the essential requirement 1 of 4: \"ssh\"","time":"2021-09-03T15:17:10-05:00"}
{"level":"debug","msg":"executing script \"ssh\"","time":"2021-09-03T15:17:10-05:00"}
{"level":"debug","msg":"stdout=\"\", stderr=\"pulberg@127.0.0.1: Permission denied (publickey,password,keyboard-interactive).\\r\\n\", err=failed to execute script \"ssh\": stdout=\"\", stderr=\"pulberg@127.0.0.1: Permission denied (publickey,password,keyboard-interactive).\\r\\n\": exit status 255","time":"2021-09-03T15:17:10-05:00"}
{"level":"info","msg":"Waiting for the essential requirement 1 of 4: \"ssh\"","time":"2021-09-03T15:17:20-05:00"}@pulberg Thanks! That shows that lima-init has failed somehow. I really need the content of /mnt/lima-cidata/user-data to see what might have happened (and ideally the content of /var/log/lima-init.log as well).
jandubois
commented
2 years ago @spurin Your failure looks similar to #532.
There are several instructions to run lima and qemu on their own, and to try different CPU settings in the discussion of #532. Could you see if any of that applies to your setup?
pulberg
commented
2 years ago I have applied the updated lima .iso as well
lima-rancher-desktop:~# ^[[60;25Rcat /mnt/lima-cidata/user-data
cat /mnt/lima-cidata/user-data
#cloud-config
# vim:syntax=yaml
growpart:
mode: auto
devices: ['/']
users:
- name: "pulberg"
uid: "740863103"
homedir: "/home/pulberg.linux"
shell: /bin/bash
sudo: ALL=(ALL) NOPASSWD:ALL
lock_passwd: true
ssh-authorized-keys:
- ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAINRgZTKM8VhSKhVyn9mtjUjJuYHGXM5++TibniGv/cF9 pulberg@z204333
write_files:
- content: |
#!/bin/sh
set -eux
LIMA_CIDATA_MNT="/mnt/lima-cidata"
LIMA_CIDATA_DEV="/dev/disk/by-label/cidata"
mkdir -p -m 700 "${LIMA_CIDATA_MNT}"
mount -o ro,mode=0700,dmode=0700,overriderockperm,exec,uid=0 "${LIMA_CIDATA_DEV}" "${LIMA_CIDATA_MNT}"
export LIMA_CIDATA_MNT
exec "${LIMA_CIDATA_MNT}"/boot.sh
owner: root:root
path: /var/lib/cloud/scripts/per-boot/00-lima.boot.sh
permissions: '0755'lima-rancher-desktop:~# ^[[60;25Rcat /var/log/lima-init.log
cat /var/log/lima-init.log
+ ln -s /var/log/lima-init.log /var/log/cloud-init-output.log
+ LIMA_CIDATA_MNT=/mnt/lima-cidata
+ LIMA_CIDATA_DEV=/dev/disk/by-label/cidata
+ mkdir -p -m 700 /mnt/lima-cidata
+ mount -o 'ro,mode=0700,dmode=0700,overriderockperm,exec,uid=0' /dev/disk/by-label/cidata /mnt/lima-cidata
+ export LIMA_CIDATA_MNT
+ . /mnt/lima-cidata/lima.env
+ LIMA_CIDATA_USER=pulberg
+ LIMA_CIDATA_UID=740863103
+ LIMA_CIDATA_MOUNTS=1
+ LIMA_CIDATA_MOUNTS_0_MOUNTPOINT=/Users/pulberg/Library/Caches/rancher-desktop/k3s
+ LIMA_CIDATA_CONTAINERD_USER=
+ LIMA_CIDATA_CONTAINERD_SYSTEM=
+ LIMA_CIDATA_SLIRP_GATEWAY=192.168.5.2
+ awk '/^local-hostname:/ {print $2}' /mnt/lima-cidata/meta-data
+ LIMA_CIDATA_HOSTNAME=lima-rancher-desktop
+ hostname lima-rancher-desktop
+ LIMA_CIDATA_HOMEDIR=/home/pulberg.linux
+ adduser -h /home/pulberg.linux -u 740863103 -D pulberg
adduser: number 740863103 is not in 0..256000 range@pulberg adduser: number 740863103 is not in 0..256000 range shows that you are still running the old ISO.
Try selecting "Reset Kubernetes" on the "Kubernetes Settings" page. That should delete the old VM and create a new one using the new ISO.
pulberg
commented
2 years ago I also found that it looks like there is a typo in the code looking for the alpine image name -
time="2021-09-03T16:28:51-05:00" level=info msg="Attempting to download the image from \"/Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/alpline-lima-v0.1.0-std-3.13.5.iso
alpline should be alpine
After resetting kubernetes i get the error pretty much instantly now -
There was an unknown error starting Kubernetes: Error: /Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl exited with code 1There is also no serial.sock or any log files now, just cidata.iso and lima.yaml
jandubois
commented
2 years ago I also found that it looks like there is a typo in the code looking for the alpine image name -
Yes, there is, but it is inconsequential. The downloaded ISO is renamed to that name during packaging, and will be loaded from that name at runtime. The name can really be anything.
After resetting kubernetes i get the error pretty much instantly now - [...] There is also no
serial.sockor any log files now, just cidata.iso and lima.yaml
That's not what I expected. Let's start over: Make sure RD is not running, and then delete the whole State directory (it will be recreated automatically when RD runs):
rm -rf ~/Library/State/rancher-desktopThen run RD again, and see if it now works. If it doesn't, and there are no logs in ~/Library/State/rancher-desktop/lima/rancher-desktop/ then look for the logs in ~/Library/State/rancher-desktop/logs/.
pulberg
commented
2 years ago ok, reset everything, RD running now, mostly...it's been in "Waiting for image manager to be ready" for about 15min now
jandubois
commented
2 years ago @pulberg Can you run kim image ls from the commandline?
Maybe try kim builder install --force to see if that fixes things. It would be weird though, as this should be a fresh install after you deleted everything.
pulberg
commented
2 years ago ➜ kim image ls
WARN[0000] Cannot find available builder daemon, attempting automatic installation...
INFO[0000] Applying node-role `builder` to `lima-rancher-desktop`
INFO[0000] Asserting namespace `kube-image`
INFO[0000] Asserting TLS secrets
INFO[0000] Asserting service/endpoints
INFO[0000] Installing builder daemon
WARN[0000] builder already installed
Error: unknown service porttrying the force option
mook-as
commented
2 years ago On a mac, you need to user kim builder install --force --endpoint-addr=127.0.0.1 instead. (It's fine to run that if you've already run the other one.)
pulberg
commented
2 years ago kim builder install --force
Error: Get "https://127.0.0.1:6443/api/v1/nodes": dial tcp 127.0.0.1:6443: connect: connection refused
vivanov83
commented
2 years ago kim builder install --force --endpoint-addr=127.0.0.1
Im getting this output. Is trying to connect to AWS even the command is specifying localhost.
kim builder install --force --endpoint-addr=127.0.0.1 Error: Get "https://***********************.ca-central-1.eks.amazonaws.com/api/v1/nodes": dial tcp ****:443: i/o timeout
adduser: number 1575537784 is not in 0..256000 range I tried Reset Kubernetes many times, without any success still stuck in the middle of nowhere :(
larssb
commented
2 years ago Having the same err. on MacOS v12.0 Beta of Monterey. I'm seeing the following in the lima.log:
time="2021-09-07T09:32:08+02:00" level=fatal msg="open /Users/lars/Library/State/rancher-desktop/lima: no such file or directory"
Could not parse lima status, assuming machine is unavailable.
time="2021-09-07T09:32:09+02:00" level=fatal msg="open /Users/lars/Library/State/rancher-desktop/lima: no such file or directory"
Could not parse lima status, assuming machine is unavailable.
time="2021-09-07T09:32:13+02:00" level=info msg="Terminal is not available, proceeding without opening an editor"
time="2021-09-07T09:32:13+02:00" level=info msg="Attempting to download the image from \"/Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/alpline-lima-v0.1.0-std-3.13.5.iso\""
time="2021-09-07T09:32:13+02:00" level=info msg="Downloaded image from \"/Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/alpline-lima-v0.1.0-std-3.13.5.iso\""
time="2021-09-07T09:32:13+02:00" level=fatal msg="failed to run [qemu-img create -f qcow2 /Users/lars/Library/State/rancher-desktop/lima/rancher-desktop/diffdisk 107374182400]: \"dyld[74677]: Library not loaded: @executable_path/../opt/glib/lib/libglib-2.0.0.dylib\\n Referenced from: /Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/Cellar/qemu/6.0.0/bin/qemu-img\\n Reason: tried: '/Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/Cellar/qemu/6.0.0/bin/../opt/glib/lib/libglib-2.0.0.dylib' (no such file), '/usr/lib/libglib-2.0.0.dylib' (no such file)\\n\": signal: abort trap"
Error starting lima: Error: /Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl exited with code 1
at ChildProcess.<anonymous> (/Applications/Rancher Desktop.app/Contents/Resources/app.asar/dist/app/background.js:1:3150)
at ChildProcess.emit (events.js:315:20)
at Process.ChildProcess._handle.onexit (internal/child_process.js:277:12)What can one do? And thank you
jandubois
commented
2 years ago @larssb Your error seems to be a duplicate of #518. It will be fixed in the next release, but there is also a workaround documented in https://github.com/rancher-sandbox/rancher-desktop/issues/518#issuecomment-901633974.
mooneye14
commented
2 years ago cat /var/log/lima-init.log Was able to connect and verify that the ssh keys are the same as well.
lima-rancher-desktop:~#
lima-rancher-desktop:~# ^[[57;25Rcat /mnt/lima-cidata/user-data cat /mnt/lima-cidata/user-data
growpart: mode: auto devices: ['/']
users:
write_files:
set -eux LIMA_CIDATA_MNT="/mnt/lima-cidata" LIMA_CIDATA_DEV="/dev/disk/by-label/cidata" mkdir -p -m 700 "${LIMA_CIDATA_MNT}" mount -o ro,mode=0700,dmode=0700,overriderockperm,exec,uid=0 "${LIMA_CIDATA_DEV}" "${LIMA_CIDATA_MNT}" export LIMA_CIDATA_MNT exec "${LIMA_CIDATA_MNT}"/boot.sh owner: root:root path: /var/lib/cloud/scripts/per-boot/00-lima.boot.sh permissions: '0755' lima-rancher-desktop:~# ^[[57;25Rcat /home//.ssh/authorized_keys cat /home//.ssh/authorized_keys ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIDTJQtO9lsLzHY4YIoX2ngP+I45wB9yTsaHuVcQiD13B userFirst.userLast@Work-0ZELVDL
lima-rancher-desktop:~# ^[[57;25Rcat /var/log/lima-init.log cat /var/log/lima-init.log
(edited by mook-as: formatting changes only.)
jandubois
commented
2 years ago Thanks @mooneye14, the limia-init.log shows the problem: chown does not support user or group names that include a ..
This will be fixed by a new ISO image via https://github.com/lima-vm/alpine-lima/pull/13
jandubois
commented
2 years ago This issue is getting too crowded, with so many people reporting the same symptoms, but different underlying causes.
We know about 3 issues:
These issues have been already fixed for the next release.
I've created separate issues for any problems related to kim builder mentioned in this issue (#591, #592).
And there is one problem left where qemu exits with "signal: abort trap" (in ha.stderr.log). We don't know yet what is causing this (and why it sometimes seems to fix itself). There are instructions in #532 to collect further information.
I'm going to close this issue now; if you still get the "limactl exited with code 1" error, and it is not covered by any of the scenarios listed above, please open a new separate issue. This includes any further instances of #532.
vivanov83
commented
2 years ago kim builder install --force Error: Get "https://127.0.0.1:6443/api/v1/nodes": dial tcp 127.0.0.1:6443: connect: connection refused
I'm getting the same :(
Happened in v0.4.1