i d like to use `nektos act` a `dockerd` client on a gitlab rancher-users #rancher-desktop

Channels

Title

quick-keyboard-83126

11/27/2022, 9:22 PM

i'd like to use

nektos/act

dockerd

client) on a gitlab runner. The gitlab runner doesn't appear to have privileged mode enabled, and i don't have the energy to figure out if i (a non-admin) can enable it. Can I install rancher-desktop (or use a rancher-desktop docker container) to get a rancher that is backed by a qemu so that I don't have to deal w/ the host docker which i probably can't touch?

jolly-forest-99711

11/28/2022, 6:46 PM

The gitlab runner would be running Linux right? I'm not sure that RD works without a graphical desktop, which I'm assuming a gitlab runner wouldn't have - that's the first stumbling block. @fast-garage-66093 do you know? Also, RD can run docker without root permission. But to do this, it modifies the docker context. I'm not sure that

act

would honor that setting. You might also consider

colima

. It looks like it's supported on Linux, and I believe it is CLI only.

quick-keyboard-83126

11/28/2022, 6:50 PM

I'm not tied to rancher. If it's easier to do with Colima, that's fine with me. Yes, the GitLab runner is Linux. I think there's a way for Rancher Desktop to be headless...

fast-garage-66093

11/28/2022, 7:34 PM

There is no way right now to disable the

sudo

prompt for docker on a fresh install. I've done this by manually writing the

settings.json

file before starting Rancher Desktop: https://github.com/rancher-sandbox/rancher-desktop/blob/main/bats/tests/helpers/vm.bash#L46-L56

Creating the

settings.json

file also avoids running the first-run dialog, so you can configure everything up-front and don't have to wait for the container engine to restart after changing settings.

quick-keyboard-83126

11/28/2022, 7:35 PM

note that I need a

qemu

that doesn't expect to have

kvm

support from the kernel as at least ime the docker container i'm running in is hostile to such things

fast-garage-66093

11/28/2022, 7:36 PM

I think it depends on how you install Rancher Desktop on Linux, but I don't think we install qemu for you; you have to bring your own (the AppImage install may be different)

So this requirement would be the same for any Lima based solution

quick-keyboard-83126

11/28/2022, 7:37 PM

I'll follow whatever advice someone gives me -- the more prescriptive the better 🙂

fast-garage-66093

11/28/2022, 7:38 PM

@jolly-forest-99711 would know best how to deal with qemu install issues on Linux

👍 1

quick-keyboard-83126

11/28/2022, 7:39 PM

The docker container I run in has

root

, it's just not

full root

(CAPS?).

fast-garage-66093

11/28/2022, 7:42 PM

I'm sorry, maybe I don't get what you are trying to do: are you wanting to run RD (and qemu) inside a docker container?

quick-keyboard-83126

11/28/2022, 7:45 PM

I have a GitHub Actions workflow and I want to run it in GitLab. There's a docker oriented tool that does a generally tolerable job of emulating the GitHub Actions environment called

act

(nektos/act). GitLab supports its own CI world via GitLab hosted runners which are also implemented in Docker. But, afaict the docker that they offer doesn't allow a docker-in-docker to work because it doesn't have --privileged or something (because it doesn't want to be attacked by guest processes). So, basically I want the GitLab runner to run a qemu of a normal linux that could expose a normal docker that act could talk to which would let it emulate GitHub Actions.

I don't really care what system is responsible for managing the qemu, but since I'm more or less familiar w/ Rancher, if I can use Rancher, I'd be happy to do so. -- I really don't want to have to figure out all of the knobs for bare-bones qemu (down to building a kernel and a root file system and setting up the whatevers...)

fast-garage-66093

11/28/2022, 7:48 PM

I don't know if this will be possible to run nested virtualization without root support. Are you even sure they have nested virtualization enabled on their VMs?

quick-keyboard-83126

11/28/2022, 7:49 PM

I am not sure of anything 🙂

I can run arbitrary commands to ask it questions if you happen to have useful commands for me to run 🙂

fast-garage-66093

11/28/2022, 7:49 PM

For Lima we moved our Linux actions to Cirrus-CI for similar reasons (Github Linux runners don't allow nested virtualization due to the VM type they run on Azure)

quick-keyboard-83126

11/28/2022, 7:49 PM

But, in theory qemu is supposed to have a "slow" mode where it emulates everything -- I'm perfectly fine w/ it running in slow mode.

(Not your fault) It's really frustrating how complicated this stuff is... All I want is a slow VM to very slowly emulate things like a normal VM would emulate things and give me answers 🙂 -- and maybe a 🐴 .

fast-garage-66093

11/28/2022, 7:53 PM

There may be a way to configure qemu to do this by setting an environment variable, like

QEMU_SYSTEM_X86_64="qemu-system-x86_64 -cpu Haswell-v4"

👍 1

But it will require experimentation, and I have no time to look into it now

quick-keyboard-83126

11/28/2022, 7:54 PM

If it's the kind of thing you'd be able to figure out in a couple of weeks, that'd probably save me months of agony. I spent way too much time yesterday trying to figure this stuff out.

I'd really love to have this stuff written up and given a high link/page rank.

fast-garage-66093

11/28/2022, 7:58 PM

It looks like you cannot override this with Lima when you are running a native VM; the accelerator is hard-coded to `kvm`: https://github.com/lima-vm/lima/blob/7f9f3fafd7523a1bd1ef93a276b57529a304b637/pkg/qemu/qemu.go#L651-L665

You could run an

aarch64

VM on an

x86_64

runner to get software emulation via `tcg`; not sure if that would be an option?

You could also create a feature request against Lima to make this configurable... I'm not sure if this will be enough though

quick-keyboard-83126

11/28/2022, 8:03 PM

I think filing a bug against lima asking for a config knob is something I should be capable of doing

fast-garage-66093

11/28/2022, 8:03 PM

I'm wrong, you can override it with the env var: https://github.com/lima-vm/lima/blob/7f9f3fafd7523a1bd1ef93a276b57529a304b637/pkg/qemu/qemu.go#L370

quick-keyboard-83126

11/28/2022, 8:03 PM

ok, so, a doc bug against lima to make it easy for someone to figure out how to do this? 🙂

fast-garage-66093

11/28/2022, 8:06 PM

In your

lima.yaml

try this:

cpuType:
  x86_64: qemu64,+ssse3

So this wouldn't even require the environment variable.

It is documented at https://github.com/lima-vm/lima/blob/7f9f3fafd7523a1bd1ef93a276b57529a304b637/examples/default.yaml#L217-L224

quick-keyboard-83126

11/28/2022, 8:07 PM

not in a way that a dumb human like myself can understand 🙂

fast-garage-66093

11/28/2022, 8:08 PM

Well, as you can see, it took me a while to figure it out myself 🙂

Maybe try it locally first; as this is still all conjecture from reading code and config files... 🙂

quick-keyboard-83126

11/28/2022, 8:09 PM

Yeah, that's fun, since i'm on m1 🙂 which means i get to docker run --platform linux/amd64 some-image-with-qemu?

fast-garage-66093

11/28/2022, 8:10 PM

On M1 you automatically get the emulated CPU if you are running an amd64 image

quick-keyboard-83126

11/28/2022, 8:11 PM

I know :)

but the goal is to test the nested layer

fast-garage-66093

11/28/2022, 8:12 PM

I have to leave the rest with you now...

quick-keyboard-83126

11/28/2022, 8:26 PM

So much fun

FATA[0037] failed to run [qemu-img info --output=json /home/user/.lima/default/basedisk]: stdout="", stderr="": exec: "qemu-img": executable file not found in $PATH

(apt install -y qemu-utils)

ERRO[0011] [hostagent] failed to run [ssh-keygen -t ed25519 -q -N -f /home/user/.lima/_config/user]: "": exec: "ssh-keygen": executable file not found in $PATH fields.level=fatal

(apt install -y openssh-client)

user@70c3b6683e0c:~$ ./bin/limactl start
INFO[0000] Using the existing instance "default"
INFO[0000] Hint: To create another instance, run the following command: limactl start --name=NAME <template://default>
INFO[0000] Attempting to download the nerdctl archive from "<https://github.com/containerd/nerdctl/releases/download/v1.0.0/nerdctl-full-1.0.0-linux-amd64.tar.gz>"  digest="sha256:b7f76a3bf1b8161eb94ebe885945feb2887dfc0d274f9da908a17bc0ef853eb9"
INFO[0000] Using cache "/home/user/.cache/lima/download/by-url-sha256/86e8280c3d639367efe7a50660ecfc4eade10b1696a9deeba27fdbf086d11098/data"
FATA[0001] exiting, status={Running:false Degraded:false Exiting:true Errors:[] SSHLocalPort:0} (hint: see "/home/user/.lima/default/ha.stderr.log")

{"level":"fatal","msg":"exec: \"qemu-system-x86_64\": executable file not found in $PATH","time":"2022-11-28T20:25:55Z"}

fast-garage-66093

11/28/2022, 8:28 PM

Looks like you don't have qemu installed

quick-keyboard-83126

11/28/2022, 8:28 PM

i installed

qemu

, but apparently it's a nothing! https://termbin.com/2il6

fast-garage-66093

11/28/2022, 8:29 PM

Install

qemu-system-x86_64

quick-keyboard-83126

11/28/2022, 8:29 PM

working on it, it's apparently

qemu-system-x86-64

...

user@70c3b6683e0c:~$ ./bin/limactl start
INFO[0000] Using the existing instance "default"
INFO[0000] Hint: To create another instance, run the following command: limactl start --name=NAME <template://default>
INFO[0000] Attempting to download the nerdctl archive from "<https://github.com/containerd/nerdctl/releases/download/v1.0.0/nerdctl-full-1.0.0-linux-amd64.tar.gz>"  digest="sha256:b7f76a3bf1b8161eb94ebe885945feb2887dfc0d274f9da908a17bc0ef853eb9"
INFO[0000] Using cache "/home/user/.cache/lima/download/by-url-sha256/86e8280c3d639367efe7a50660ecfc4eade10b1696a9deeba27fdbf086d11098/data"
INFO[0001] [hostagent] Starting QEMU (hint: to watch the boot progress, see "/home/user/.lima/default/serial.log")
INFO[0001] SSH Local Port: 60022
INFO[0001] [hostagent] Waiting for the essential requirement 1 of 5: "ssh"
INFO[0001] [hostagent] Driver stopped due to error: "exit status 1"
INFO[0001] [hostagent] Shutting down the host agent
WARN[0001] [hostagent] failed to exit SSH master
INFO[0001] [hostagent] Shutting down QEMU with ACPI
WARN[0001] [hostagent] failed to open the QMP socket "/home/user/.lima/default/qmp.sock", forcibly killing QEMU
WARN[0001] [hostagent] failed to kill QEMU
INFO[0011] [hostagent] Waiting for the essential requirement 1 of 5: "ssh"

user@70c3b6683e0c:~$ cat /home/user/.lima/default/ha.stderr.log
{"level":"debug","msg":"Creating iso file /home/user/.lima/default/cidata.iso","time":"2022-11-28T20:29:49Z"}
{"level":"debug","msg":"Using /tmp/diskfs_iso1803760783 as workspace","time":"2022-11-28T20:29:49Z"}
{"level":"debug","msg":"OpenSSH version 8.9.1 detected","time":"2022-11-28T20:29:50Z"}
{"level":"debug","msg":"AES accelerator seems available, prioritizing <mailto:aes128-gcm@openssh.com|aes128-gcm@openssh.com> and <mailto:aes256-gcm@openssh.com|aes256-gcm@openssh.com>","time":"2022-11-28T20:29:50Z"}
{"level":"debug","msg":"Start udp server listening on: 127.0.0.1:54423","time":"2022-11-28T20:29:50Z"}
{"level":"debug","msg":"Start tcp server listening on: 127.0.0.1:44469","time":"2022-11-28T20:29:50Z"}
{"level":"debug","msg":"firmware candidates = [/home/user/.local/share/qemu/edk2-x86_64-code.fd /usr/share/qemu/edk2-x86_64-code.fd /usr/share/OVMF/OVMF_CODE.fd /usr/share/qemu/ovmf-x86_64-code.bin /usr/share/edk2-ovmf/x64/OVMF_CODE.fd]","time":"2022-11-28T20:29:50Z"}
{"level":"info","msg":"Starting QEMU (hint: to watch the boot progress, see \"/home/user/.lima/default/serial.log\")","time":"2022-11-28T20:29:50Z"}
{"level":"debug","msg":"qCmd.Args: [/usr/bin/qemu-system-x86_64 -m 4096 -cpu host -machine q35,accel=kvm -smp 4,sockets=1,cores=4,threads=1 -drive if=pflash,format=raw,readonly=on,file=/usr/share/OVMF/OVMF_CODE.fd -boot order=c,splash-time=0,menu=on -drive file=/home/user/.lima/default/diffdisk,if=virtio,discard=on -cdrom /home/user/.lima/default/cidata.iso -netdev user,id=net0,net=192.168.5.0/24,dhcpstart=192.168.5.15,hostfwd=tcp:127.0.0.1:60022-:22 -device virtio-net-pci,netdev=net0,mac=52:55:55:dd:50:87 -device virtio-rng-pci -display none -device virtio-vga -device virtio-keyboard-pci -device virtio-mouse-pci -device qemu-xhci,id=usb-bus -parallel none -chardev socket,id=char-serial,path=/home/user/.lima/default/serial.sock,server=on,wait=off,logfile=/home/user/.lima/default/serial.log -serial chardev:char-serial -chardev socket,id=char-qmp,path=/home/user/.lima/default/qmp.sock,server=on,wait=off -qmp chardev:char-qmp -name lima-default -pidfile /home/user/.lima/default/qemu.pid]","time":"2022-11-28T20:29:50Z"}
{"level":"info","msg":"Waiting for the essential requirement 1 of 5: \"ssh\"","time":"2022-11-28T20:29:50Z"}
{"level":"debug","msg":"executing script \"ssh\"","time":"2022-11-28T20:29:50Z"}
{"level":"debug","msg":"executing ssh for script \"ssh\": /usr/bin/ssh [ssh -F /dev/null -o IdentityFile=\"/home/user/.lima/_config/user\" -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o NoHostAuthenticationForLocalhost=yes -o GSSAPIAuthentication=no -o PreferredAuthentications=publickey -o Compression=no -o BatchMode=yes -o IdentitiesOnly=yes -o Ciphers=\"^aes128-gcm@openssh.com,aes256-gcm@openssh.com\" -o User=user -o ControlMaster=auto -o ControlPath=\"/home/user/.lima/default/ssh.sock\" -o ControlPersist=5m -p 60022 127.0.0.1 -- /bin/bash]","time":"2022-11-28T20:29:50Z"}
{"level":"debug","msg":"stdout=\"\", stderr=\"ssh: connect to host 127.0.0.1 port 60022: Connection refused\\r\\n\", err=failed to execute script \"ssh\": stdout=\"\", stderr=\"ssh: connect to host 127.0.0.1 port 60022: Connection refused\\r\\n\": exit status 255","time":"2022-11-28T20:29:50Z"}
{"level":"debug","msg":"qemu[stderr]: Could not access KVM kernel module: No such file or directory","time":"2022-11-28T20:29:50Z"}
{"level":"debug","msg":"qemu[stderr]: qemu-system-x86_64: failed to initialize kvm: No such file or directory","time":"2022-11-28T20:29:50Z"}
{"level":"info","msg":"Driver stopped due to error: \"exit status 1\"","time":"2022-11-28T20:29:50Z"}
{"level":"info","msg":"Shutting down the host agent","time":"2022-11-28T20:29:50Z"}
{"level":"debug","msg":"shutting down the SSH master","time":"2022-11-28T20:29:50Z"}
{"level":"debug","msg":"executing ssh for exiting the master: /usr/bin/ssh [ssh -F /dev/null -o IdentityFile=\"/home/user/.lima/_config/user\" -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o NoHostAuthenticationForLocalhost=yes -o GSSAPIAuthentication=no -o PreferredAuthentications=publickey -o Compression=no -o BatchMode=yes -o IdentitiesOnly=yes -o Ciphers=\"^aes128-gcm@openssh.com,aes256-gcm@openssh.com\" -o User=user -o ControlMaster=auto -o ControlPath=\"/home/user/.lima/default/ssh.sock\" -o ControlPersist=5m -O exit -p 60022 127.0.0.1]","time":"2022-11-28T20:29:50Z"}
{"error":"failed to execute `ssh -O exit -p 60022 127.0.0.1`, out=\"Control socket connect(/home/user/.lima/default/ssh.sock): No such file or directory\\r\\n\": exit status 255","level":"warning","msg":"failed to exit SSH master","time":"2022-11-28T20:29:50Z"}
{"level":"info","msg":"Shutting down QEMU with ACPI","time":"2022-11-28T20:29:50Z"}
{"error":"dial unix /home/user/.lima/default/qmp.sock: connect: connection refused","level":"warning","msg":"failed to open the QMP socket \"/home/user/.lima/default/qmp.sock\", forcibly killing QEMU","time":"2022-11-28T20:29:50Z"}
{"error":"os: process already finished","level":"warning","msg":"failed to kill QEMU","time":"2022-11-28T20:29:50Z"}
{"level":"info","msg":"Waiting for the essential requirement 1 of 5: \"ssh\"","time":"2022-11-28T20:30:00Z"}
{"level":"debug","msg":"executing script \"ssh\"","time":"2022-11-28T20:30:00Z"}
{"level":"debug","msg":"executing ssh for script \"ssh\": /usr/bin/ssh [ssh -F /dev/null -o IdentityFile=\"/home/user/.lima/_config/user\" -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o NoHostAuthenticationForLocalhost=yes -o GSSAPIAuthentication=no -o PreferredAuthentications=publickey -o Compression=no -o BatchMode=yes -o IdentitiesOnly=yes -o Ciphers=\"^aes128-gcm@openssh.com,aes256-gcm@openssh.com\" -o User=user -o ControlMaster=auto -o ControlPath=\"/home/user/.lima/default/ssh.sock\" -o ControlPersist=5m -p 60022 127.0.0.1 -- /bin/bash]","time":"2022-11-28T20:30:00Z"}
{"level":"debug","msg":"stdout=\"\", stderr=\"ssh: connect to host 127.0.0.1 port 60022: Connection refused\\r\\n\", err=failed to execute script \"ssh\": stdout=\"\", stderr=\"ssh: connect to host 127.0.0.1 port 60022: Connection refused\\r\\n\": exit status 255","time":"2022-11-28T20:30:00Z"}
{"level":"info","msg":"Waiting for the essential requirement 1 of 5: \"ssh\"","time":"2022-11-28T20:30:10Z"}
{"level":"debug","msg":"executing script \"ssh\"","time":"2022-11-28T20:30:10Z"}
{"level":"debug","msg":"executing ssh for script \"ssh\": /usr/bin/ssh [ssh -F /dev/null -o IdentityFile=\"/home/user/.lima/_config/user\" -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o NoHostAuthenticationForLocalhost=yes -o GSSAPIAuthentication=no -o PreferredAuthentications=publickey -o Compression=no -o BatchMode=yes -o IdentitiesOnly=yes -o Ciphers=\"^aes128-gcm@openssh.com,aes256-gcm@openssh.com\" -o User=user -o ControlMaster=auto -o ControlPath=\"/home/user/.lima/default/ssh.sock\" -o ControlPersist=5m -p 60022 127.0.0.1 -- /bin/bash]","time":"2022-11-28T20:30:10Z"}
{"level":"debug","msg":"stdout=\"\", stderr=\"ssh: connect to host 127.0.0.1 port 60022: Connection refused\\r\\n\", err=failed to execute script \"ssh\": stdout=\"\", stderr=\"ssh: connect to host 127.0.0.1 port 60022: Connection refused\\r\\n\": exit status 255","time":"2022-11-28T20:30:10Z"}

fast-garage-66093

11/28/2022, 8:31 PM

qemu-system-x86_64: failed to initialize kvm

quick-keyboard-83126

11/28/2022, 8:31 PM

ok, it looks like it tried yeah. that

user@70c3b6683e0c:~$ cat lima.yaml
cpuType:
  x86_64: qemu64,+ssse3

fast-garage-66093

11/28/2022, 8:31 PM

Did you make the changes to

lima.yaml

quick-keyboard-83126

11/28/2022, 8:31 PM

was it supposed to be a

lima.yaml

in a specific directory?

fast-garage-66093

11/28/2022, 8:33 PM

For the instance you are starting. So when you run

limactl start

you need to choose "edit" and modify the setting the config it uses.

quick-keyboard-83126

11/28/2022, 8:33 PM

^C
user@70c3b6683e0c:~$ perl -pi -e 's/x86_64:/x86_64: qemu64,+ssse3/' ./.lima/default/lima.yaml
user@70c3b6683e0c:~$ ./bin/limactl start
INFO[0000] Using the existing instance "default"
INFO[0000] Hint: To create another instance, run the following command: limactl start --name=NAME <template://default>
FATA[0000] errors inspecting instance: [host agent is running but driver is not]
user@70c3b6683e0c:~$ ./bin/limactl stop
FATA[0000] expected status "Running", got "Broken" (maybe use `limactl stop -f`?)

fast-garage-66093

11/28/2022, 8:34 PM

You can put the lines into

~/.lima/_config/default.yaml

(or

overrride.yaml

) to have them merged automatically.

quick-keyboard-83126

11/28/2022, 8:34 PM

root@70c3b6683e0c:/# su - user
user@70c3b6683e0c:~$ cat /home/user/.lima/default/ha.stderr.log
{"level":"debug","msg":"Creating iso file /home/user/.lima/default/cidata.iso","time":"2022-11-28T20:33:28Z"}
{"level":"debug","msg":"Using /tmp/diskfs_iso3948462047 as workspace","time":"2022-11-28T20:33:28Z"}
{"level":"debug","msg":"OpenSSH version 8.9.1 detected","time":"2022-11-28T20:33:28Z"}
{"level":"debug","msg":"AES accelerator seems available, prioritizing <mailto:aes128-gcm@openssh.com|aes128-gcm@openssh.com> and <mailto:aes256-gcm@openssh.com|aes256-gcm@openssh.com>","time":"2022-11-28T20:33:28Z"}
{"level":"debug","msg":"Start udp server listening on: 127.0.0.1:33288","time":"2022-11-28T20:33:28Z"}
{"level":"debug","msg":"Start tcp server listening on: 127.0.0.1:40407","time":"2022-11-28T20:33:28Z"}
{"level":"debug","msg":"firmware candidates = [/home/user/.local/share/qemu/edk2-x86_64-code.fd /usr/share/qemu/edk2-x86_64-code.fd /usr/share/OVMF/OVMF_CODE.fd /usr/share/qemu/ovmf-x86_64-code.bin /usr/share/edk2-ovmf/x64/OVMF_CODE.fd]","time":"2022-11-28T20:33:29Z"}
{"level":"info","msg":"Starting QEMU (hint: to watch the boot progress, see \"/home/user/.lima/default/serial.log\")","time":"2022-11-28T20:33:29Z"}
{"level":"debug","msg":"qCmd.Args: [/usr/bin/qemu-system-x86_64 -m 4096 -cpu qemu64,+ssse3 null -machine q35,vmport=off -accel tcg,thread=multi,tb-size=512 -global ICH9-LPC.disable_s3=1 -smp 4,sockets=1,cores=4,threads=1 -drive if=pflash,format=raw,readonly=on,file=/usr/share/OVMF/OVMF_CODE.fd -boot order=c,splash-time=0,menu=on -drive file=/home/user/.lima/default/diffdisk,if=virtio,discard=on -cdrom /home/user/.lima/default/cidata.iso -netdev user,id=net0,net=192.168.5.0/24,dhcpstart=192.168.5.15,hostfwd=tcp:127.0.0.1:60022-:22 -device virtio-net-pci,netdev=net0,mac=52:55:55:dd:50:87 -device virtio-rng-pci -display none -device virtio-vga -device virtio-keyboard-pci -device virtio-mouse-pci -device qemu-xhci,id=usb-bus -parallel none -chardev socket,id=char-serial,path=/home/user/.lima/default/serial.sock,server=on,wait=off,logfile=/home/user/.lima/default/serial.log -serial chardev:char-serial -chardev socket,id=char-qmp,path=/home/user/.lima/default/qmp.sock,server=on,wait=off -qmp chardev:char-qmp -name lima-default -pidfile /home/user/.lima/default/qemu.pid]","time":"2022-11-28T20:33:29Z"}
{"level":"info","msg":"Waiting for the essential requirement 1 of 5: \"ssh\"","time":"2022-11-28T20:33:29Z"}
{"level":"debug","msg":"executing script \"ssh\"","time":"2022-11-28T20:33:29Z"}
{"level":"debug","msg":"executing ssh for script \"ssh\": /usr/bin/ssh [ssh -F /dev/null -o IdentityFile=\"/home/user/.lima/_config/user\" -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o NoHostAuthenticationForLocalhost=yes -o GSSAPIAuthentication=no -o PreferredAuthentications=publickey -o Compression=no -o BatchMode=yes -o IdentitiesOnly=yes -o Ciphers=\"^aes128-gcm@openssh.com,aes256-gcm@openssh.com\" -o User=user -o ControlMaster=auto -o ControlPath=\"/home/user/.lima/default/ssh.sock\" -o ControlPersist=5m -p 60022 127.0.0.1 -- /bin/bash]","time":"2022-11-28T20:33:29Z"}
{"level":"debug","msg":"stdout=\"\", stderr=\"ssh: connect to host 127.0.0.1 port 60022: Connection refused\\r\\n\", err=failed to execute script \"ssh\": stdout=\"\", stderr=\"ssh: connect to host 127.0.0.1 port 60022: Connection refused\\r\\n\": exit status 255","time":"2022-11-28T20:33:29Z"}
{"level":"debug","msg":"qemu[stderr]: qemu-system-x86_64: Property 'qemu64-x86_64-cpu.ssse3 null' not found","time":"2022-11-28T20:33:29Z"}
{"level":"info","msg":"Driver stopped due to error: \"exit status 1\"","time":"2022-11-28T20:33:29Z"}
{"level":"info","msg":"Shutting down the host agent","time":"2022-11-28T20:33:29Z"}
{"level":"debug","msg":"shutting down the SSH master","time":"2022-11-28T20:33:29Z"}
{"level":"debug","msg":"executing ssh for exiting the master: /usr/bin/ssh [ssh -F /dev/null -o IdentityFile=\"/home/user/.lima/_config/user\" -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o NoHostAuthenticationForLocalhost=yes -o GSSAPIAuthentication=no -o PreferredAuthentications=publickey -o Compression=no -o BatchMode=yes -o IdentitiesOnly=yes -o Ciphers=\"^aes128-gcm@openssh.com,aes256-gcm@openssh.com\" -o User=user -o ControlMaster=auto -o ControlPath=\"/home/user/.lima/default/ssh.sock\" -o ControlPersist=5m -O exit -p 60022 127.0.0.1]","time":"2022-11-28T20:33:29Z"}
{"error":"failed to execute `ssh -O exit -p 60022 127.0.0.1`, out=\"Control socket connect(/home/user/.lima/default/ssh.sock): No such file or directory\\r\\n\": exit status 255","level":"warning","msg":"failed to exit SSH master","time":"2022-11-28T20:33:29Z"}
{"level":"info","msg":"Shutting down QEMU with ACPI","time":"2022-11-28T20:33:29Z"}
{"error":"dial unix /home/user/.lima/default/qmp.sock: connect: connection refused","level":"warning","msg":"failed to open the QMP socket \"/home/user/.lima/default/qmp.sock\", forcibly killing QEMU","time":"2022-11-28T20:33:29Z"}
{"error":"os: process already finished","level":"warning","msg":"failed to kill QEMU","time":"2022-11-28T20:33:29Z"}
{"level":"info","msg":"Waiting for the essential requirement 1 of 5: \"ssh\"","time":"2022-11-28T20:33:39Z"}
{"level":"debug","msg":"executing script \"ssh\"","time":"2022-11-28T20:33:39Z"}
{"level":"debug","msg":"executing ssh for script \"ssh\": /usr/bin/ssh [ssh -F /dev/null -o IdentityFile=\"/home/user/.lima/_config/user\" -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o NoHostAuthenticationForLocalhost=yes -o GSSAPIAuthentication=no -o PreferredAuthentications=publickey -o Compression=no -o BatchMode=yes -o IdentitiesOnly=yes -o Ciphers=\"^aes128-gcm@openssh.com,aes256-gcm@openssh.com\" -o User=user -o ControlMaster=auto -o ControlPath=\"/home/user/.lima/default/ssh.sock\" -o ControlPersist=5m -p 60022 127.0.0.1 -- /bin/bash]","time":"2022-11-28T20:33:39Z"}
{"level":"debug","msg":"stdout=\"\", stderr=\"ssh: connect to host 127.0.0.1 port 60022: Connection refused\\r\\n\", err=failed to execute script \"ssh\": stdout=\"\", stderr=\"ssh: connect to host 127.0.0.1 port 60022: Connection refused\\r\\n\": exit status 255","time":"2022-11-28T20:33:39Z"}
{"level":"info","msg":"Waiting for the essential requirement 1 of 5: \"ssh\"","time":"2022-11-28T20:33:49Z"}
{"level":"debug","msg":"executing script \"ssh\"","time":"2022-11-28T20:33:49Z"}
{"level":"debug","msg":"executing ssh for script \"ssh\": /usr/bin/ssh [ssh -F /dev/null -o IdentityFile=\"/home/user/.lima/_config/user\" -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o NoHostAuthenticationForLocalhost=yes -o GSSAPIAuthentication=no -o PreferredAuthentications=publickey -o Compression=no -o BatchMode=yes -o IdentitiesOnly=yes -o Ciphers=\"^aes128-gcm@openssh.com,aes256-gcm@openssh.com\" -o User=user -o ControlMaster=auto -o ControlPath=\"/home/user/.lima/default/ssh.sock\" -o ControlPersist=5m -p 60022 127.0.0.1 -- /bin/bash]","time":"2022-11-28T20:33:49Z"}
{"level":"debug","msg":"stdout=\"\", stderr=\"ssh: connect to host 127.0.0.1 port 60022: Connection refused\\r\\n\", err=failed to execute script \"ssh\": stdout=\"\", stderr=\"ssh: connect to host 127.0.0.1 port 60022: Connection refused\\r\\n\": exit status 255","time":"2022-11-28T20:33:49Z"}
{"level":"info","msg":"Waiting for the essential requirement 1 of 5: \"ssh\"","time":"2022-11-28T20:33:59Z"}
{"level":"debug","msg":"executing script \"ssh\"","time":"2022-11-28T20:33:59Z"}
{"level":"debug","msg":"executing ssh for script \"ssh\": /usr/bin/ssh [ssh -F /dev/null -o IdentityFile=\"/home/user/.lima/_config/user\" -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o NoHostAuthenticationForLocalhost=yes -o GSSAPIAuthentication=no -o PreferredAuthentications=publickey -o Compression=no -o BatchMode=yes -o IdentitiesOnly=yes -o Ciphers=\"^aes128-gcm@openssh.com,aes256-gcm@openssh.com\" -o User=user -o ControlMaster=auto -o ControlPath=\"/home/user/.lima/default/ssh.sock\" -o ControlPersist=5m -p 60022 127.0.0.1 -- /bin/bash]","time":"2022-11-28T20:33:59Z"}
{"level":"debug","msg":"stdout=\"\", stderr=\"ssh: connect to host 127.0.0.1 port 60022: Connection refused\\r\\n\", err=failed to execute script \"ssh\": stdout=\"\", stderr=\"ssh: connect to host 127.0.0.1 port 60022: Connection refused\\r\\n\": exit status 255","time":"2022-11-28T20:33:59Z"}
{"level":"info","msg":"Waiting for the essential requirement 1 of 5: \"ssh\"","time":"2022-11-28T20:34:09Z"}
{"level":"debug","msg":"executing script \"ssh\"","time":"2022-11-28T20:34:09Z"}
{"level":"debug","msg":"executing ssh for script \"ssh\": /usr/bin/ssh [ssh -F /dev/null -o IdentityFile=\"/home/user/.lima/_config/user\" -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o NoHostAuthenticationForLocalhost=yes -o GSSAPIAuthentication=no -o PreferredAuthentications=publickey -o Compression=no -o BatchMode=yes -o IdentitiesOnly=yes -o Ciphers=\"^aes128-gcm@openssh.com,aes256-gcm@openssh.com\" -o User=user -o ControlMaster=auto -o ControlPath=\"/home/user/.lima/default/ssh.sock\" -o ControlPersist=5m -p 60022 127.0.0.1 -- /bin/bash]","time":"2022-11-28T20:34:09Z"}
{"level":"debug","msg":"stdout=\"\", stderr=\"ssh: connect to host 127.0.0.1 port 60022: Connection refused\\r\\n\", err=failed to execute script \"ssh\": stdout=\"\", stderr=\"ssh: connect to host 127.0.0.1 port 60022: Connection refused\\r\\n\": exit status 255","time":"2022-11-28T20:34:09Z"}

fast-garage-66093

11/28/2022, 8:35 PM

Maybe try

cpuType:
  x86_64: qemu64

Oh, wait, the problem is the spurious

null

afterwards

I don't see where the

null

can come from, in:

-cpu qemu64,+ssse3 null -machine q35,vmport=off

quick-keyboard-83126

11/28/2022, 8:41 PM

ah, that's sure a nice looking null 🙂

here's the current ps output:

user@70c3b6683e0c:~$ ps aux|grep qemu
root         1  0.0  0.1 150236 16100 pts/0    Ssl  20:15   0:00 /usr/bin/qemu-x86_64 /usr/bin/bash bash
root     15148  0.0  0.1 152244 15316 pts/0    Sl   20:29   0:00 /usr/bin/qemu-x86_64 /usr/bin/su su - user
user     15151  0.0  0.1 150268 15624 pts/0    Sl   20:29   0:00 /usr/bin/qemu-x86_64 /bin/bash -bash
root     15380  0.0  0.1 150060 16152 pts/1    Ssl  20:33   0:00 /usr/bin/qemu-x86_64 /usr/bin/bash bash
user     15501  0.1  0.8 1340280 68132 pts/0   Sl+  20:36   0:00 /usr/bin/qemu-x86_64 ./bin/limactl ./bin/limactl start
user     15508  0.2  0.8 1565996 72512 pts/0   Sl+  20:36   0:00 /usr/bin/qemu-x86_64 /home/user/bin/limactl /home/user/bin/limactl hostagent --pidfile /home/user/.lima/default/ha.pid --socket /home/user/.lima/default/ha.sock --nerdctl-archive /home/user/.cache/lima/download/by-url-sha256/86e8280c3d639367efe7a50660ecfc4eade10b1696a9deeba27fdbf086d11098/data default
user     15535  126 14.8 5848928 1208540 pts/0 Sl+  20:36   5:56 /usr/bin/qemu-x86_64 /usr/bin/qemu-system-x86_64 /usr/bin/qemu-system-x86_64 -m 4096 -cpu qemu64 -machine q35,vmport=off -accel tcg,thread=multi,tb-size=512 -global ICH9-LPC.disable_s3=1 -smp 4,sockets=1,cores=4,threads=1 -drive if=pflash,format=raw,readonly=on,file=/usr/share/OVMF/OVMF_CODE.fd -boot order=c,splash-time=0,menu=on -drive file=/home/user/.lima/default/diffdisk,if=virtio,discard=on -cdrom /home/user/.lima/default/cidata.iso -netdev user,id=net0,net=192.168.5.0/24,dhcpstart=192.168.5.15,hostfwd=tcp:127.0.0.1:60022-:22 -device virtio-net-pci,netdev=net0,mac=52:55:55:dd:50:87 -device virtio-rng-pci -display none -device virtio-vga -device virtio-keyboard-pci -device virtio-mouse-pci -device qemu-xhci,id=usb-bus -parallel none -chardev socket,id=char-serial,path=/home/user/.lima/default/serial.sock,server=on,wait=off,logfile=/home/user/.lima/default/serial.log -serial chardev:char-serial -chardev socket,id=char-qmp,path=/home/user/.lima/default/qmp.sock,server=on,wait=off -qmp chardev:char-qmp -name lima-default -pidfile /home/user/.lima/default/qemu.pid
root     16803  0.0  0.1 152244 15088 pts/1    Sl   20:39   0:00 /usr/bin/qemu-x86_64 /usr/bin/su su - user
user     16806  0.0  0.2 150276 17168 pts/1    Sl   20:39   0:00 /usr/bin/qemu-x86_64 /bin/bash -bash
user     16832  0.2  0.2 156588 18652 pts/0    Sl+  20:41   0:00 /usr/bin/qemu-x86_64 /usr/bin/ssh ssh -F /dev/null -o IdentityFile="/home/user/.lima/_config/user" -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o NoHostAuthenticationForLocalhost=yes -o GSSAPIAuthentication=no -o PreferredAuthentications=publickey -o Compression=no -o BatchMode=yes -o IdentitiesOnly=yes -o Ciphers="^aes128-gcm@openssh.com,aes256-gcm@openssh.com" -o User=user -o ControlMaster=auto -o ControlPath="/home/user/.lima/default/ssh.sock" -o ControlPersist=5m -p 60022 127.0.0.1 -- /bin/bash
user     16836  0.0  0.0 147792  7376 pts/1    Sl+  20:41   0:00 /usr/bin/qemu-x86_64 /usr/bin/grep grep --color=auto qemu

fast-garage-66093

11/28/2022, 8:42 PM

Ok, that looks better, so it went away when you removed the

,+ssse3

substring?

quick-keyboard-83126

11/28/2022, 8:42 PM

I think so

fast-garage-66093

11/28/2022, 8:44 PM

So it is working now?

View count: 161

Back to #rancher-desktop Join thread in Slack