-
-
Notifications
You must be signed in to change notification settings - Fork 365
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
colima takes ~30s to boot #301
Comments
When I start the machine manually via the qemu command colima uses, the login prompt appears in <10s. |
If you're building from source, kindly use the makefile to have actual version attached to the binary. make # binary will be present in _output/binaries
make install # if you want it in PATH |
Are you referring to the initial boot or subsequent boots? |
Ah, sorry, this is packaged by Nix. Don't know why the version doesn't show up. Is there a flag we need to set in order for the release to know its version? Version is 0.3.4. I'm referring to subsequent boots. This time is reproducible. |
This is not an accurate comparison, getting the login prompt directly from Qemu does not imply that Lima is done starting. To monitor the boot, tail the serial log during startup. tail -f ~/.lima/colima/serial.log Considering that Colima startup is not something expected to be frequently repeated, this is not a pressing issue (if at all an issue). Nonetheless, will keep an eye on ways to improve the boot time. Thanks. |
Looks like the Nix package needs to be fixed. cc @aaschmid. |
If you can tell me how the colima build system decides which version to embed, I could fix that too. How long does it take to start on your machine? |
The ldflags need to be specified Line 15 in 784cec0
~ 30secs on an Intel MacBook. |
These are shown on `colima version` See also abiosoft/colima#301
@Atemu Thanks :) Kindly note that the package is also a bit outdated, the latest version is v0.4.2 as opposed to nixpkg's v0.3.4. |
Yeah, that'll need a separate PR. Are there any major changes to dependencies, build process etc. to watch out for? Perhaps it's related to some sort of timeout because we're trying to ssh before it's up or something? |
Not at all, no changes.
Yeah exactly. |
@Atemu: sorry for being late with update of colima for @abiosoft: Do you have an idea why it fails? Otherwise I would need to dive deeper w/o having time for it...
|
Not sure precisely why it is failing, currently trying to set up a nix based environment on Linux to see if I can reproduce it. |
I can also try to provide more information. Do you have some tips for me, how to easily to this? Maybe enabling some debugging infos while building. Another lightweight alternative could be using docker, see https://nixos.org/download.html#nix-install-docker. My problem however is based on MacOS using nix as package manager |
Apparently, some behaviours are different on macOS and Linux. Will you able to test the changes if it's on the main branch or will it require a new release? |
I can test every revision, so a feature branch would also work :-) |
@aaschmid can you try the |
Didn't come back after about 2 minutes. Need to leave and can check later again... |
Alright, thanks. I will dig a bit further. FYI it builds fine on macOS and Linux (with/without Nix) for me. |
Sounds like a problem on my side. I created a draft PR and will look on the result of the build: NixOS/nixpkgs#174013 |
Created #304 as this thread has deviated from its original issue. |
Describe the Bug
A clear and concise description of what the bug is.
Version
Colima Version:
What is the output of
colima version
Lima Version:
What is the output of
limactl --version
Qemu Version
What is the output of
qemu-img --version
Operating System
To Reproduce
Steps to reproduce the behavior:
time colima start
Expected behavior
A clear and concise description of what you expected to happen.
It should start in about a third of the time.
Additional context
Add any other context about the problem here.
Booting a minimal NixOS VM takes about 10 seconds in UTM and I can't imagine docker needing much time either. Something must be off about the Alpine configuration.
The text was updated successfully, but these errors were encountered: