-
-
Notifications
You must be signed in to change notification settings - Fork 420
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 start fails most of the time: error validating SHA sum #1163
Comments
Confirm this. colima 0.7.5 |
same problem too. colima 0.7.5, apple m1, Sequoia 15.0.1. as saw the 0.7.1 in download link " https://github.com/abiosoft/colima-core/releases/download/v0.7.1/ubuntu-24.04-minimal-cloudimg-arm64-docker.qcow2", use asdf to install v0.7.0. ( tried to install 0.7.4, saw the same v0.7.1 in download link)
|
The disk image versioning is not directly tied to Colima versions, that is not an issue. |
yes, you are right. what i mean is i saw disk image versioning changed from version 0.7.1 so i gave a try version 0.7.0 and it works. once installed, i can upgrade to 0.7.5, still works, it looks like not download the new version qcow2 image. however, cleaned up the cache, install 0.7.5 freshly, can re-produce the issue. i checked the checksum, both version images checksum in the github assets are correct, also manually downloaded images, still correct checksum. the code change to curl is just added flag "I". struggle to find which code change in version 0.7.1 caused the issue . |
hit the same error for the latest version 0.7.6, output with --very-verbose as below
the file /Users/xxx/Library/Caches/colima/caches/c3056771d27045a9b7b665f5ddbbac4e311078337847c505226bd184c8191d0c.downloading.invalid is 0 size
Installed colima 0.7.0 and run colima start --very-verbose, output as below
the file /Users/xxx/Library/Caches/colima/caches/4e1d6f9076c36aa5dc942101c931e0230f3c2c4eafae3c050ebc072dda0ad76b looks good
|
@KevinHuang40856 can you share the output of the command And does it fail all the time or intermittently? |
@abiosoft sure, the outpuf of command which shasum as below with my testing, any fresh installation of versions higher than v0.7.0 will fail all the time. |
@KevinHuang40856 can you manually download the file with curl and compute the shasum afterwards and see if it matches? Disk image: https://github.com/abiosoft/colima-core/releases/download/v0.7.6-1/ubuntu-24.04-minimal-cloudimg-amd64-docker.qcow2 |
@abiosoft sure. it matches. `❯ curl -L -o ubuntu-24.04-minimal-cloudimg-amd64-docker.qcow2 https://github.com/abiosoft/colima-core/releases/download/v0.7.6-1/ubuntu-24.04-minimal-cloudimg-amd64-docker.qcow2 % Total % Received % Xferd Average Speed Time Time Time Current
|
The problem keeps happening in v0.8.0 with |
yes, tested v0.8.0, same error. and tested v0.7.6, v0.7.1, got new errors "panic: runtime error: invalid memory address or nil pointer dereference", until finally got colima start run successfully after switched back to v0.7.0. full output goroutine 1 [running]: |
once got colima v0.7.0 started successfully, install newer version including v0.8.0 and have no problem to run colima start `❯ asdf install colima 0.8.0
runtime: docker |
|
run " colima start --runtime containerd" which will download different image for colima v0.8.0, same error validating SHA sum error
|
I just hit this issue again and I don't think it's related to the version of colima itself. When I try to start colima I get:
What I imediatelly noticed is that according to my internet connection at the moment, downloading this 300MB file should take noticeably longer. So I checked what it actually downloaded:
I was able to download the file by just opening it via the browser, but I could not download it using However after a few tries - eventually it allowed me to download the file using I have not tested it, but it seems that by inspecting where |
Hi, any way to run colima? This is a real issue here. Cannot get my system running again after a reinstall of my mac. Is there a way to download the image and place it in the right spot? |
does not work for me in 0.8. same error as seen by Kevin. direct download via curl passes. here is my very verbose output:
|
any ideas on how to work around. I copied the downloaded qcow2 file to /Library/Caches/colima/caches folder, but it did not work |
Here's my workaround
Then manually download from github releases colima v6.9.10. Anything >=0.70 runs into this SHA mismatch error. Copy the downloaded 0.6.9 version to /usr/local/bin. Allow macOS security to execute this binary then re-run colima start - works!
|
Must have something to do with how curl is handling the downloads. |
yup. looks like github mirrors block the curl request with pre-set headers - perhaps the installation itself could download the qcow2 file and copy to the cache folder? What is the correct way to populate the local cache? does the qcow2 file need to be named with a hash? |
That would really help, please provide a short description how to set up manually (or point us to the script etc. that does the downloading). I really like this project, but right now I just cannot work .... |
This can be introduced as a cli flag. |
Ability to specify a previously downloaded disk image is being added in #1216, and |
Thanks for that !!! (though the issue still persists.) Tied to install but somehow it shows still the old version: brew install colima To start colima now and restart at login: ❯ colima --version colima start --disk-image ~/Downloads/ubuntu-24.04-minimal-cloudimg-amd64-docker.qcow2 |
@mstoffel-sag you're still running the older version. Can you run |
@abiosoft - did not work with 0.8.1
|
@rsriniva thanks for reporting, that is likely a bug. I will try to reproduce it. Can you try with specifying the absolute path? i.e. |
yes. i tried everything - absolute path, using ./ , using ~ etc etc. same result. looking at the output it seems the flag is skipped and it defaults to trying the download |
@rsriniva what mac are you using? |
@rsriniva can you share the output of the command |
|
I think I cracked it. I had a newer version of GNU shasum in the path. Using the default shasum that comes with macOS did the trick. colima 0.8.1 is now working! Thank you @abiosoft ! Here was the old shasum in path:
Here is the default macOS shasum which is older:
With the older shasum binary in PATH, here is what colima start looks like:
@abiosoft - I wonder what the correct fix for this is? Maybe add a flag to disable shasum checks? or find a native golang checksum library instead of relying on OS native tooling? What could possibly happen is that when people do brew install it could pull in lots of GNU coreutils and other C libs which are not compatible with BSD coreutils in macOS? |
The fix would be specifying the full path to the native |
This could also be tricky - people doing brew install will pull in shasum newer versions, now you have to search multiple paths. But why call out to external binaries. Is there not a native go lib to do checksums - yes, it will be slower, but not that much slower ;-) |
Do I understand that right: This is a checksum issue (somehow wrong output of the checksum binary). When this is fixed the download will also work. What I really dont get how a shasum can be different.... it would create a lot of trouble everywhere... |
I think what happens is not that the shasum is different, rather the behaviour of the |
Can someone try the latest development version with |
looks the same ❯ brew install --head colima To start colima now and restart at login: To start colima now and restart at login: ❯ colima start
|
@mstoffel-sag are you sure the right version is the one running? It should be downloading a newer disk image. Can you share the output of |
colima --version
colima version v0.8.0
which colima
/Users/mstoffel/.asdf/shims/colima
|
@mstoffel-sag that is wrong. Can you |
This is what I have on my macOS. The binary was downloaded directly from github releases. With this version, I don't need to pass the --disk-image flag either. I guess it caches the disk image and does not re-download? colima --version
colima version v0.8.1 |
did brew install colima --head but ❯ colima version ❯ colima start
|
@mstoffel-sag can you start with |
sure colima start --very-verbose
|
@mstoffel-sag I don't understand what's going on. The Colima version is wrong. What does running |
which colima colima --version |
@mstoffel-sag can you join the slack channel and let us try to troubleshoot this. The version is still wrong as it shouldn't be a stable version. So the newer (development) version is yet to be installed. |
@mstoffel-sag this is what I expect for the version.
|
Sorry not today. Will have time next week Tuesday |
Description
I had to run
colima start
more than 5 times for it to start correctly. I am running from AWS-hosted M1 and M2 machines. Output follows:Version
Operating System
Output of
colima status
(I don't know if it matters, but I run this after a successful download)
Reproduction Steps
colima --verbose start -p default --cpu 8 --memory 12 --disk 256 --vm-type=vz --vz-rosetta
Expected behaviour
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: