Giter VIP home page Giter VIP logo

Comments (30)

xqzhou avatar xqzhou commented on August 23, 2024 2

Public key attached

-----BEGIN PUBLIC KEY-----
MIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEAxB4B5U5qSV+wPlCGfq2H
t/KKLo3kM239aHQeI8QQyci1DXOhYnGqj4064GUSiXXHZnRWwBcHIKXEY4AFKGGJ
XMfdLjK87emAuWnPgc/pcYKck0mPwTX6XYXrGAjz7Qb/k34BMA/1mpjeZHJoCTgF
dn2Wfv10t3vFP1wm5t/Gz/txtctIYnAPmAA9E40YD1Xh61cx335bj4K7YNgKkaZq
8uB7k9/Lu7K88fPR28etv2jQFbr5qQCXFcCzUVRsNyERm5L36bySEM42fpOHSpuX
q0yBr0g25KmVGwCTGHZTVGoMrPHsNyRK+VQ4a8xEN6UmjHVrjiwAfrZtXE0EawEm
PEm6mGG0O9XED9GjRKotL7yH6skiuzjvHJ+la6JtQh6YyU2TLuZ7MKuE5kJRse1v
hf/Ypv7GiHJhRf7Z3NhFFbBzn91j0g25c90lXlH2KYgiqkCbsBHymSl/ZZrpyrHm
EGcYo1RUvjRr/jdtaOkOjHOq0J4ihNldQJyQyUeehNaJlc58lmXld6Ss1bhQ56yU
bq4rK3yR/a3LTZLdhi54vwvV362Lcz4om0gNfI8hP5kjP7SQMicm2L4UcmqlT7Wr
gPnsqa7LpbqaAO2oM+m25rxaQqPL5B3/qs8pcY+VgCDroITVT+mmj5vu1h7SRLOA
Tr3sQw0MB/csqx8Q5F/Gl1kCAwEAAQ==
-----END PUBLIC KEY-----

from lima.

jandubois avatar jandubois commented on August 23, 2024 2

One way of doing this would be calling ssh-keygen -l -f and checking for stdout and return code.

I would simply check that file contains just a single line, and that the line starts with ssh-. If it does, we stuff it into authorized keys and be done with it.

The most important part is that we don't break the YAML format for the user-data file because that will break cloud-init and leave us with a broken VM. It doesn't hurt if the key is not valid; it just means it will never match.

from lima.

AkihiroSuda avatar AkihiroSuda commented on August 23, 2024 1

Please try v0.6.3, which fixes DNS issues #199

from lima.

jandubois avatar jandubois commented on August 23, 2024 1

@terorie I have no idea how you can get "Can't assign requested address" for 127.0.0.1.

I thought that maybe you still had a stray instance of the hostagent running on your machine, but that should have given you a port conflict, and not an address error. Given that a reboot has cleared the issue, I guess there is nothing else left to try.

from lima.

AkihiroSuda avatar AkihiroSuda commented on August 23, 2024 1

@network-shark
You are hitting this:

Please use Lima v0.9.0

from lima.

AkihiroSuda avatar AkihiroSuda commented on August 23, 2024

https://github.com/AkihiroSuda/lima/blob/86d6a938c1595aff1f352ff5c3344958311494b7/pkg/limayaml/default.yaml#L54

Could you try ssh.loadDotSSHPubKeys=false? (requires Lima v0.5.0)

from lima.

ndeloof avatar ndeloof commented on August 23, 2024

created default.yaml file with updated loadDotSSHPubKeys: false

$ limactl start default.yaml
...
INFO[0598] [hostagent] Waiting for the essential requirement 1 of 4: "ssh" 
FATA[0607] did not receive an event with the "running" status

from lima.

cheimu avatar cheimu commented on August 23, 2024

Same issue here

from lima.

AkihiroSuda avatar AkihiroSuda commented on August 23, 2024

@cheimu Any error in serial.log or ha.*.log under ~/.lima/default?

from lima.

cheimu avatar cheimu commented on August 23, 2024

@cheimu Any error in serial.log or ha.*.log under ~/.lima/default?

No errors and logs are all about installing things such as buildkit.

from lima.

riptl avatar riptl commented on August 23, 2024

Same here. The serial.log indicates a network issue.

==> /Users/richard/.lima/default/serial.log <==
[   55.544906] cloud-init[1299]: + command -v apt-get
[   55.545159] cloud-init[1299]: + DEBIAN_FRONTEND=noninteractive
[   55.545938] cloud-init[1299]: + export DEBIAN_FRONTEND
[   55.546824] cloud-init[1299]: + apt-get update
[   85.654631] cloud-init[1299]: Err:1 http://archive.ubuntu.com/ubuntu hirsute InRelease
[   85.654841] cloud-init[1299]:   Temporary failure resolving 'archive.ubuntu.com'
[   85.655332] cloud-init[1299]: Err:2 http://security.ubuntu.com/ubuntu hirsute-security InRelease
[   85.655849] cloud-init[1299]:   Temporary failure resolving 'security.ubuntu.com'
[  115.699092] cloud-init[1299]: Err:3 http://archive.ubuntu.com/ubuntu hirsute-updates InRelease
[  115.699726] cloud-init[1299]:   Temporary failure resolving 'archive.ubuntu.com'
[  145.737890] cloud-init[1299]: Err:4 http://archive.ubuntu.com/ubuntu hirsute-backports InRelease
[  145.738171] cloud-init[1299]:   Temporary failure resolving 'archive.ubuntu.com'
[  145.908147] cloud-init[1299]: Reading package lists...
[  145.912782] cloud-init[1299]: W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/hirsute/InRelease  Temporary failure resolving 'archive.ubuntu.com'
[  145.913515] cloud-init[1299]: W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/hirsute-updates/InRelease  Temporary failure resolving 'archive.ubuntu.com'
[  145.913863] cloud-init[1299]: W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/hirsute-backports/InRelease  Temporary failure resolving 'archive.ubuntu.com'
[  145.914386] cloud-init[1299]: W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/hirsute-security/InRelease  Temporary failure resolving 'security.ubuntu.com'
[  145.915365] cloud-init[1299]: W: Some index files failed to download. They have been ignored, or old ones used instead.

from lima.

riptl avatar riptl commented on August 23, 2024

With v0.6.3 the DNS error is gone but instance startup still fails at the same SSH step for me.

The last log lines in serial.log:

[   54.611756] cloud-init[1303]: LIMA| Exiting with code 0
<14>Sep  5 06:02:36 cloud-init: #############################################################
<14>Sep  5 06:02:36 cloud-init: -----BEGIN SSH HOST KEY FINGERPRINTS-----
<14>Sep  5 06:02:36 cloud-init: 1024 SHA256:... root@lima-default (DSA)
<14>Sep  5 06:02:36 cloud-init: 256 SHA256:... root@lima-default (ECDSA)
<14>Sep  5 06:02:36 cloud-init: 256 SHA256:... root@lima-default (ED25519)
<14>Sep  5 06:02:36 cloud-init: 3072 SHA256:... root@lima-default (RSA)
<14>Sep  5 06:02:36 cloud-init: -----END SSH HOST KEY FINGERPRINTS-----
<14>Sep  5 06:02:36 cloud-init: #############################################################
-----BEGIN SSH HOST KEY KEYS-----
...
[   54.652444] cloud-init[1303]: Cloud-init v. 21.2-3-g899bfaa9-0ubuntu2~21.04.1 finished at Sun, 05 Sep 2021 06:02:36 +0000. Datasource DataSourceNoCloud [seed=/dev/sr0][dsmode=net].  Up 54.61 seconds

There are no errors otherwise.

The SSH port 127.0.0.1:60022 as shown in limactl list is not open.

from lima.

jandubois avatar jandubois commented on August 23, 2024

@terorie This looks fine. Could you attach the full serial.log to the issue, as well as the ha.stderr.log?

from lima.

riptl avatar riptl commented on August 23, 2024

Here they are. Sorry for the delay.

ha.stderr.log
ha.stdout.log
serial.log

from lima.

riptl avatar riptl commented on August 23, 2024

I've tried flushing my routing table & recreating the default gateway to fix the Can't assign requested address manually but no luck. Will try using a different random port for SSH. Maybe that helps. EDIT: Still no luck.

from lima.

riptl avatar riptl commented on August 23, 2024

Ok I've tried switching the laptop off and on again. That worked. Sorry for the noise.

from lima.

jandubois avatar jandubois commented on August 23, 2024

@cheimu @ndeloof Please report back if switching to Lima v0.6.3 fixes the problem for you!

from lima.

xqzhou avatar xqzhou commented on August 23, 2024

I'm running lima v0.6.3 and having the same issue.

INFO[0000] Using the existing instance "default"
INFO[0000] Downloading "https://github.com/containerd/nerdctl/releases/download/v0.11.1/nerdctl-full-0.11.1-linux-amd64.tar.gz" (sha256:ce7a6e119b03c3fb8ded3d46d929962fd17417bea1d5bbc07e0fce49494d8a09)
INFO[0001] Using cache "/Users/xq/Library/Caches/lima/download/by-url-sha256/3304d173f1e1824e5be6cf84bf2f78825cf0db416c4c975dbb2458776942629e/data"
INFO[0002] [hostagent] Starting QEMU (hint: to watch the boot progress, see "/Users/xq/.lima/default/serial.log")
INFO[0002] SSH Local Port: 60022
INFO[0002] [hostagent] Waiting for the essential requirement 1 of 4: "ssh"
INFO[0013] [hostagent] Waiting for the essential requirement 1 of 4: "ssh"
INFO[0028] [hostagent] Waiting for the essential requirement 1 of 4: "ssh"
INFO[0038] [hostagent] Waiting for the essential requirement 1 of 4: "ssh"
...
INFO[0556] [hostagent] Waiting for the essential requirement 1 of 4: "ssh"
INFO[0566] [hostagent] Waiting for the essential requirement 1 of 4: "ssh"
INFO[0576] [hostagent] Waiting for the essential requirement 1 of 4: "ssh"
INFO[0587] [hostagent] Waiting for the essential requirement 1 of 4: "ssh"
INFO[0597] [hostagent] Waiting for the essential requirement 1 of 4: "ssh"
FATA[0602] did not receive an event with the "running" status

serial.log

from lima.

jandubois avatar jandubois commented on August 23, 2024

@xqzhou Could you delete the instance and try again, setting loadDotSSHPubKeys to false?

If that fixes your problem, could you look through all your ~/.ssh/*.pub files on your machine and check if any of them have unexpected characters in them (e.g. especially quote characters or newlines)?

Maybe run wc -l ~/.ssh/*.pub and verify that each file contains just a single line?

@AkihiroSuda Is there any reason loadDotSSHPubKeys defaults to true?

from lima.

xqzhou avatar xqzhou commented on August 23, 2024

@jandubois set loadDotSSHPubKeys to false did fix my problem.

A run of wc -l ~/.ssh/*.pub indicates some of my ssh public keys did contain more than one lines.

thanks a lot

from lima.

jandubois avatar jandubois commented on August 23, 2024

@xqzhou Would you mind sharing some of those files? They should be public keys anyways, but you can further anonymize them like this:

$ cat ~/.ssh/*.pub | tr A-Za-z0-9 a
aaa-aaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa+aaaaaa+aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/aaaaaaaaaaaaaaaa+aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/aaaaaaaaaaaaaaaaaaaa+aaaaaaaaaaaaaaaaa/aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/aaaaaaaaa/aaaaaaaaaaaaaaaaaaaaaaa+aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/aaaaaaaaaaaaaaaaaaaaaaa/aaaa+aaaaaaaaaaaaaaaaaaaa/aaaaaaaaaaaaaa+aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa+aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/aaaaaaaaaaaaaa++aaaaaaa/aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/aaaaaaaaaaaaaaaaaaaa== [email protected]
aaa-aaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa+aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/aaaaaaaaaaaaa+aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa+aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa+aaaaaaaaaaaaaaaaaaaaaaaaaa+aaaaaaaaaaaaaaaaaaaaaaaaa/aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa+aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa== [email protected]

I don't care about the keys themselves; I just want to see if there are any other special characters in them that we may need to treat specially (I see that currently we don't even put quotes around the keys, which might confuse the YAML parser).

from lima.

jandubois avatar jandubois commented on August 23, 2024

Oh, it is an OpenSSL public key, not an OpenSSH one.

@AkihiroSuda I think we should simply ignore keys that are not in openssh public key format; wdyt?

from lima.

AkihiroSuda avatar AkihiroSuda commented on August 23, 2024

@AkihiroSuda Is there any reason loadDotSSHPubKeys defaults to true?

Because I wanted ssh apps like rsync to work without specifying custom key.
But Iā€™m not against changing the default value.
If we are going to change the default, we will have to print the key path in human-readable logs.

Oh, it is an OpenSSL public key, not an OpenSSH one.

How does this happen? Is there any app that stores OpenSSL keys under ~/.ssh ?

@AkihiroSuda I think we should simply ignore keys that are not in openssh public key format; wdyt?

SGTM

from lima.

jandubois avatar jandubois commented on August 23, 2024

But Iā€™m not against changing the default value.

Now that we've seen that this can be caused by OpenSSL keys, I would keep the default the same for more more iteration and do this instead:

  • put keys in quotes in the YAML file (probably doesn't make a difference)
  • ignore all *.pub files that are more than a single line and that are not in OpenSSL public key format (should fix the YAML parsing errors)

And then hope we no longer see these issues. But if issues continue to be caused by the authorized keys, then I would argue for changing the default.

from lima.

riptl avatar riptl commented on August 23, 2024

Some systems (PuTTY for Windows) use a similar format. It's somewhat widespread.

---- BEGIN SSH2 PUBLIC KEY ----
...

Seeing PEM DER RSA public keys in the SSH directory is a new one to me.

Either way, I think it's a good idea to check for OpenSSH public key syntax.
One way of doing this would be calling ssh-keygen -l -f and checking for stdout and return code. (EDIT: unless OpenSSH supports these obscure formats that Lima can't handle well šŸ˜“ A regex would suffice then I guess?)

from lima.

RouxAntoine avatar RouxAntoine commented on August 23, 2024

Hello,

First of all big big thank and well done for all lima jobs

i have similar issue with provision.user which is never executed and i found this in guest :

sudo cat /mnt/lima-cidata/boot.sh
#!/bin/sh
set -eu

INFO() {
	echo "LIMA| $*"
}

WARNING() {
	echo "LIMA| WARNING: $*"
}

# shellcheck disable=SC2163
while read -r line; do export "$line"; done <"${LIMA_CIDATA_MNT}"/lima.env

CODE=0

for f in "${LIMA_CIDATA_MNT}"/boot/*; do
	INFO "Executing $f"
	if ! "$f"; then
		WARNING "Failed to execute $f"
		CODE=1
	fi
done

if [ -d "${LIMA_CIDATA_MNT}"/provision.system ]; then
	for f in "${LIMA_CIDATA_MNT}"/provision.system/*; do
		INFO "Executing $f"
		if ! "$f"; then
			WARNING "Failed to execute $f"
			CODE=1
		fi
	done
fi

if [ -d "${LIMA_CIDATA_MNT}"/provision.user ]; then
	until [ -e "/run/user/${LIMA_CIDATA_UID}}/systemd/private" ]; do sleep 3; done
	for f in "${LIMA_CIDATA_MNT}"/provision.user/*; do
		INFO "Executing $f (as user ${LIMA_CIDATA_USER})"
		if ! sudo -iu "${LIMA_CIDATA_USER}" "XDG_RUNTIME_DIR=/run/user/${LIMA_CIDATA_UID}" "$f"; then
			WARNING "Failed to execute $f (as user ${LIMA_CIDATA_USER})"
			CODE=1
		fi
	done
fi

INFO "Exiting with code $CODE"
exit "$CODE"

i think these line until [ -e "/run/user/${LIMA_CIDATA_UID}}/systemd/private" ]; do sleep 3; done prevent user provisionning
due to double }}

but i have not yet find where this double } is introduce
everything seems good here :

lima/pkg/cidata/cidata.TEMPLATE.d/boot.sh

Line 37 in df25c45

until [ -e "/run/user/${LIMA_CIDATA_UID}/systemd/private" ]; do sleep 3; done

lima/pkg/cidata/cidata.TEMPLATE.d/lima.env

Line 2 in df25c45

LIMA_CIDATA_UID={{ .UID }}

lima/pkg/cidata/cidata.go

Line 52 in df25c45

UID: uid,

Oh ! i say nothing bug is here on version 0.6.1

https://github.com/lima-vm/lima/blob/v0.6.1/pkg/cidata/cidata.TEMPLATE.d/boot.sh#L36

fixed in pull request #197

from lima.

cedws avatar cedws commented on August 23, 2024

Happening to me too but the cause is probably different. x86 guest on ARM (M1 Pro).

? Creating an instance "default" Open an editor to override the configuration
INFO[0005] Attempting to download the image from "~/Downloads/impish-server-cloudimg-amd64.img"  digest=
INFO[0005] Attempting to download the image from "https://cloud-images.ubuntu.com/impish/current/impish-server-cloudimg-amd64.img"  digest=
INFO[0006] Using cache "/Users/connoredwards/Library/Caches/lima/download/by-url-sha256/ac74da77a6828e35de7edaa06fdbb33d12ef97cce2726550017e3c1066c88fb1/data"
INFO[0006] Attempting to download the nerdctl archive from "https://github.com/containerd/nerdctl/releases/download/v0.12.1/nerdctl-full-0.12.1-linux-amd64.tar.gz"  digest="sha256:fe9e7e63554795fc4b984c178609a2a9dffa6d69925356f919b8fa30a2f36210"
INFO[0006] Using cache "/Users/connoredwards/Library/Caches/lima/download/by-url-sha256/a1ebbffd3dcb629755d3f6bee929f4f0cf3920ff8b99d5d2b86b29935f0dc8e1/data"
INFO[0006] [hostagent] Starting QEMU (hint: to watch the boot progress, see "/Users/connoredwards/.lima/default/serial.log")
INFO[0006] SSH Local Port: 60022
INFO[0007] [hostagent] Waiting for the essential requirement 1 of 4: "ssh"
INFO[0092] [hostagent] Waiting for the essential requirement 1 of 4: "ssh"
INFO[0132] [hostagent] Waiting for the essential requirement 1 of 4: "ssh"
INFO[0142] [hostagent] Waiting for the essential requirement 1 of 4: "ssh"
INFO[0152] [hostagent] Waiting for the essential requirement 1 of 4: "ssh"
INFO[0188] [hostagent] The essential requirement 1 of 4 is satisfied
INFO[0188] [hostagent] Waiting for the essential requirement 2 of 4: "sshfs binary to be installed"
INFO[0229] [hostagent] Waiting for the essential requirement 2 of 4: "sshfs binary to be installed"
INFO[0270] [hostagent] Waiting for the essential requirement 2 of 4: "sshfs binary to be installed"
INFO[0310] [hostagent] Waiting for the essential requirement 2 of 4: "sshfs binary to be installed"
INFO[0351] [hostagent] Waiting for the essential requirement 2 of 4: "sshfs binary to be installed"
INFO[0373] [hostagent] The essential requirement 2 of 4 is satisfied
INFO[0373] [hostagent] Waiting for the essential requirement 3 of 4: "/etc/fuse.conf to contain \"user_allow_other\""
INFO[0414] [hostagent] Waiting for the essential requirement 3 of 4: "/etc/fuse.conf to contain \"user_allow_other\""
INFO[0455] [hostagent] Waiting for the essential requirement 3 of 4: "/etc/fuse.conf to contain \"user_allow_other\""
INFO[0495] [hostagent] Waiting for the essential requirement 3 of 4: "/etc/fuse.conf to contain \"user_allow_other\""
INFO[0536] [hostagent] Waiting for the essential requirement 3 of 4: "/etc/fuse.conf to contain \"user_allow_other\""
INFO[0576] [hostagent] Waiting for the essential requirement 3 of 4: "/etc/fuse.conf to contain \"user_allow_other\""
FATA[0606] did not receive an event with the "running" status

connoredwards@Connors-MacBook-Pro ~> tail -f /Users/connoredwards/.lima/default/serial.log
[  412.632742] cloud-init[1439]: Setting up uidmap (1:4.8.1-1ubuntu9) ...
[  412.715987] cloud-init[1439]: Setting up dbus-user-session (1.12.20-2ubuntu2) ...
[  412.770665] cloud-init[1439]: Setting up libfuse3-3:amd64 (3.10.3-2) ...
[  412.809644] cloud-init[1439]: Setting up fuse3 (3.10.3-2) ...
[  412.828676] cloud-init[1439]: Installing new version of config file /etc/fuse.conf ...
[  413.318002] cloud-init[1439]: update-initramfs: deferring update (trigger activated)
[  413.364135] cloud-init[1439]: Processing triggers for libc-bin (2.34-0ubuntu3) ...
[  414.130465] cloud-init[1439]: Processing triggers for man-db (2.9.4-2) ...
[  417.906905] cloud-init[1439]: Processing triggers for initramfs-tools (0.140ubuntu6) ...
[  418.897748] cloud-init[1439]: update-initramfs: Generating /boot/initrd.img-5.13.0-19-generic

But I can a shell after it exits:

connoredwards@Connors-MacBook-Pro ~ [1]> lima
connoredwards@lima-default:/Users/connoredwards$

from lima.

cedws avatar cedws commented on August 23, 2024

Oh, more kernel logs just appeared showing it setting up the network. I guess the initramfs generation took too long and the CLI timed out? But it took a really long time...

from lima.

zinking avatar zinking commented on August 23, 2024

yet another occurrence on 0.8.2

[   33.597745] cloud-init[935]:   Connection failed [IP: 91.189.88.152 80]
[   33.655266] cloud-init[935]: E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/universe/f/fuse3/libfuse3-3_3.10.3-2_amd64.deb  Connection failed [IP: 91.189.88.152 80]
[   33.655406] cloud-init[935]: E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/universe/f/fuse3/fuse3_3.10.3-2_amd64.deb  Connection failed [IP: 91.189.88.152 80]
[   33.656347] cloud-init[935]: E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

ping to ip works outside the vm

āžœ  Downloads ping  91.189.88.152
PING 91.189.88.152 (91.189.88.152): 56 data bytes
64 bytes from 91.189.88.152: icmp_seq=0 ttl=47 time=268.820 ms
64 bytes from 91.189.88.152: icmp_seq=1 ttl=47 time=268.563 ms

while fail inside the vm.

I am adopting the option above loadDotSSHPubKeys=false

from lima.

network-shark avatar network-shark commented on August 23, 2024

Installed lima via brew and got

INFO[0512] [hostagent] Waiting for the essential requirement 1 of 5: "ssh"
DEBU[0512] [hostagent] executing script "ssh"
DEBU[0512] [hostagent] executing ssh for script "ssh": /usr/bin/ssh [ssh -F /dev/null -o IdentityFile="/Users/sharky/.lima/_config/user" -o IdentityFile="/Users/sharky/.ssh/id_rsa" -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="^
[email protected],[email protected]" -o User=sharky -o ControlMaster=auto -o ControlPath="/Users/sharky/.lima/default/ssh.sock" -o ControlPersist=5m -p 60022 127.0.0.1 -- /bin/bash]
DEBU[0587] [hostagent] stdout="", stderr="kex_exchange_identification: read: Connection reset by peer\r\nConnection reset by 127.0.0.1 port 60022\r\n", err=failed to execute script "ssh": stdout="", stderr="k
ex_exchange_identification: read: Connection reset by peer\r\nConnection reset by 127.0.0.1 port 60022\r\n": exit status 255
INFO[0597] [hostagent] Waiting for the essential requirement 1 of 5: "ssh"
DEBU[0597] [hostagent] executing script "ssh"
DEBU[0597] [hostagent] executing ssh for script "ssh": /usr/bin/ssh [ssh -F /dev/null -o IdentityFile="/Users/sharky/.lima/_config/user" -o IdentityFile="/Users/sharky/.ssh/id_rsa" -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="^
[email protected],[email protected]" -o User=sharky -o ControlMaster=auto -o ControlPath="/Users/sharky/.lima/default/ssh.sock" -o ControlPersist=5m -p 60022 127.0.0.1 -- /bin/bash]
FATA[0600] did not receive an event with the "running" status

Even with set loadDotSSHPubKeys=false does not help.

MacOS 12.2.1

Serial.log
https://termbin.com/mwbh

from lima.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    šŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. šŸ“ŠšŸ“ˆšŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ā¤ļø Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.