Comments (11)
As a worst case, you should not need to do more than this.
limactl stop colima
limactl delete colima
colima start
from colima.
I think I know what the problem is.
Can you kindly run colima delete
before starting.
If it still does not work, can you kindly share the output of the following.
cat ~/.lima/colima/lima.yaml
Thanks
from colima.
I see this issue whenever I try to stop colima and start again with a different CPU and Memory limits.
Running
limactl stop colima ; limactl delete colima
gives meFATA[0000] failed to delete instance "colima": expected status "Stopped", got "Broken"
on first attempt, but works fine on second try.
@zvictor You should not need to use limactl
at all. It was only recommended above for troubleshooting purposes.
colima delete
should do what you need.
from colima.
Thanks for the commands.
I didn't use limactl
, so below are the way with colima
command, they are similar, but shorter.
colima stop
colima delete
colima start
Put here for reference only
(Notes: I got this error after upgraded my macbook to latest OS, Ventura, maybe related.)
from colima.
Thanks for trying this out so quickly. This is strange as I have not been able to reproduce this.
Do you have an existing version of colima running?
What lima version do you have?
Is the vm created on lima? check with limactl ls
from colima.
Contents of my cat ~/.lima/colima/lima.yaml
arch: "default"
images:
- location: "https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64.img"
arch: "x86_64"
- location: "https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-arm64.img"
arch: "aarch64"
cpus: 3
memory: "6GiB"
disk: "75GiB"
mounts:
- location: "~"
# CAUTION: writable SHOULD be false for the home directory.
# Setting writable to true is possible, but untested and dangerous.
writable: false
- location: "/tmp/colima"
writable: true
ssh:
localPort: 41122
loadDotSSHPubKeys: false
containerd:
system: false
user: false
firmware:
legacyBIOS: false
from colima.
After capturing the above, I deleted the following directories with this command: rm -rf ~/.lima ~/.colima ~/.docker
After this, I ran colima start
, which resulted in a different error, prompting me to look at the logs. The content of the ~/.lima/colima/ha.stderr.log
file is:
{"level":"info","msg":"Starting QEMU (hint: to watch the boot progress, see \"/Users/vijay/.lima/colima/serial.log\")","time":"2021-10-13T07:36:44+05:30"}
{"level":"debug","msg":"qCmd.Args: [/usr/local/bin/qemu-system-x86_64 -cpu host -machine q35,accel=hvf -smp 2,sockets=1,cores=2,threads=1 -m 2048 -drive if=pflash,format=raw,readonly=on,file=/usr/local/share/qemu/edk2-x86_64-code.fd -boot order=c,splash-time=0,menu=on -drive file=/Users/vijay/.lima/colima/diffdisk,if=virtio -cdrom /Users/vijay/.lima/colima/cidata.iso -netdev user,id=net0,net=192.168.5.0/24,dhcpstart=192.168.5.15,hostfwd=tcp:127.0.0.1:41122-:22 -device virtio-net-pci,netdev=net0,mac=52:55:55:7c:c7:d9 -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/vijay/.lima/colima/serial.sock,server=on,wait=off,logfile=/Users/vijay/.lima/colima/serial.log -serial chardev:char-serial -chardev socket,id=char-qmp,path=/Users/vijay/.lima/colima/qmp.sock,server=on,wait=off -qmp chardev:char-qmp -name lima-colima -pidfile /Users/vijay/.lima/colima/qemu.pid]","time":"2021-10-13T07:36:44+05:30"}
{"level":"info","msg":"Waiting for the essential requirement 1 of 4: \"ssh\"","time":"2021-10-13T07:36:44+05:30"}
{"level":"debug","msg":"executing script \"ssh\"","time":"2021-10-13T07:36:44+05:30"}
{"level":"debug","msg":"qemu[stderr]: qemu-system-x86_64: -netdev user,id=net0,net=192.168.5.0/24,dhcpstart=192.168.5.15,hostfwd=tcp:127.0.0.1:41122-:22: Could not set up host forwarding rule 'tcp:127.0.0.1:41122-:22'","time":"2021-10-13T07:36:44+05:30"}
{"error":"exit status 1","level":"info","msg":"QEMU has exited","time":"2021-10-13T07:36:44+05:30"}
{"level":"debug","msg":"stdout=\"\", stderr=\"[email protected]: Permission denied (publickey).\\r\\n\", err=failed to execute script \"ssh\": stdout=\"\", stderr=\"[email protected]: Permission denied (publickey).\\r\\n\": exit status 255","time":"2021-10-13T07:36:45+05:30"}
This is the version of qemu 6.1.0_1
(installed via homebrew
)
from colima.
No dice unfortunately!
from colima.
@vraravam I am willing to help you troubleshoot in a zoom session. Can you send me an email?
I suspect it is something to do with ssh for you. And I have not seen anyone else report this issue.
from colima.
@abiosoft - thanks - I just downloaded 0.2.1
- and that works without issues! We can close this ticket.
from colima.
I see this issue whenever I try to stop colima and start again with a different CPU and Memory limits.
Running limactl stop colima ; limactl delete colima
gives me FATA[0000] failed to delete instance "colima": expected status "Stopped", got "Broken"
on first attempt, but works fine on second try.
from colima.
Related Issues (20)
- error setting up reachable IP address
- macOS 14 VM Type VZ / Virtiofs - SSH agent forward fails after colima stop / start (if container with agent was still running)
- Can't mount volumes with 9p securityModel: mapped-xattr HOT 4
- Vanished DB while updating from 0.5.6 to 0.6 version. HOT 8
- Can't connect to host.docker.internal on first start when defined in extra_hosts HOT 3
- now that cgroup v2 is default (with Colima v0.6.0+), is there a CLI option to use cgroup v1 instead? HOT 2
- Network and kubernetes instability in extended use sessions HOT 1
- Allow configuration of Swap
- colima x86_64 daemon.json file has incorrect proxy HOT 6
- docker+k3s: no Node available, probably due to `--docker is no longer supported` from k3s HOT 1
- Colima with containerd runtime not exposing docker.sock HOT 2
- brew services start doesn't start colima
- colima start error HOT 2
- Containers in emulated x86_64 VM become unreachable after a while (connection refused) HOT 5
- Creating aarch64 instance on intel macOS hangs on starting ... context=docker HOT 4
- colima start --kubernetes: kubernetes cluster unreachable
- Can't start Elasticsearch image HOT 5
- Colima freezes and I have to restart it HOT 4
- Lima v0.20.0 breaks Colima HOT 4
- Colima is failing to do port forwarding after upgrading to Ventura 13.6.4 HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from colima.