https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
w
w
Thanks Justin I am not sure if this is the same issue
Copy code
stderr: 'time="2023-01-24T20:07:30Z" level=debug msg="OpenSSH version 9.0.1 detected"\n' +
    'time="2023-01-24T20:07:30Z" level=debug msg="OpenSSH version 9.0.1 detected"\n' +
    'time="2023-01-24T20:07:30Z" 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>"\n' +
    'time="2023-01-24T20:07:30Z" level=debug msg="executing scp (may take a long time)): [/usr/bin/scp -F /dev/null -o IdentityFile=\\"/Users/afinzel/Library/Application Support/rancher-desktop/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=afinzel -o ControlMaster=auto -o ControlPath=\\"/Users/afinzel/Library/Application Support/rancher-desktop/lima/0/ssh.sock\\" -o ControlPersist=5m -v -3 -- /var/folders/dm/m0xvqpl93s52df05t0cqwq2r0000gq/T/rd-ca-tVBtxn/certs.tar <scp://afinzel@127.0.0.1:51174//tmp/certs.tar>]"\n' +
    'Executing: program /usr/bin/ssh host 127.0.0.1, user afinzel, command sftp\n' +
    'OpenSSH_9.0p1, LibreSSL 3.3.6\r\n' +
    'debug1: Reading configuration data /dev/null\r\n' +
    'debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling\r\n' +
    'debug1: auto-mux: Trying existing master\r\n' +
    'debug1: mux_client_request_session: master session id: 13\r\n' +
    '/usr/bin/scp: write remote "/tmp/certs.tar": Failure\r\n' +
    '/usr/bin/scp: failed to upload file /var/folders/dm/m0xvqpl93s52df05t0cqwq2r0000gq/T/rd-ca-tVBtxn/certs.tar to /tmp/certs.tar\r\n',
that si what I see as the last thing in lima logs
it was working and then I had issues writing in a container. I restarted as disk space looked ok adn then things stopped working
w
yup i figured not, but first post didn’t have much to go on. generic 1 exit
maybe the vm disk is full?
w
any idea how to check?
but that sounds possible
w
can the VM come up at all so you can do an rdctl shell?
w
I am in
w
just take a ook at the devices for free space
w
THATS THE BADGER, ANY IDEA WHAT NOW?
Copy code
/dev/disk/by-label/data-volume
                         97.9G     93.1G         0 100% /tmp
sorry for caps
w
any chance a docker prune helps clean up some old images?
w
that won't work because the image manager is down
w
so docker system df and docker system prune are toast i guess.
w
Copy code
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
so I am in the container? with this shell
w
yeah i mean it makes sense. was just hoping 😉
no rdctl takes you into the VM that runs dockerd, k3s, etc.
i am sure a factory reset will clean things up, but be nice to not have to start from scratch
w
I tried that 😞
factory reset
w
well thats strange
w
thank you for your help btw rhis has got me a lot closer
I deleted a volume from /var/lib/docker/volumes and it boots now. Seems strange 97gig is the set size
✅ 1
thank you again!!
w
yup you can increase the vm size with a lima override, but by default its 100G
w
cool, thanks
w
you could try the manual fstrim an see if it helps
no that i think of it… your issues isn’t space on the Host… just space in the VM so don’t think that will matter
the fstrim i mean. the larger base disk can help if you are legit using up all 100 without a ton of orphaned images hanging out
w
I did docker prune after it came up so maybe I should be good now
👍 1
w
probably a low space warning would be a good one for Diagnostics if its not already there
490 Views
Open in Slack
PreviousNext
Powered by