-
Notifications
You must be signed in to change notification settings - Fork 250
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
[BUG] Error getting MAC address from UUID on macOS with hyperkit #882
Comments
@arthurbarr Looks like you hit kubernetes/minikube#5594 one, can you try to do following and let us know if that works?
|
|
Is https://686-55985023-gh.circle-artifacts.com/0/hyperkit a custom build of hyperkit? Or a nightly build? My spidey-sense is tingling just thinking about about running a random binary on my machine. |
Anything new on this issue? I have exactly the same error. |
@arthurbarr This is the build artifact of moby/hyperkit#263 one if you check the details for circleCI it will take you to the circleCI UI, here you can check the artifact tab after login. |
@rlangbehn You can also follow the suggestion from #882 (comment) and tell us if it helps. |
I am hitting the same with Max OS Catalina version 10.15.3 and latest crc version downloaded from RedHat developer site:
|
Comment above mentions issue moby/hyperkit#263 but that has been merged 3 months ago and I am on latest patch level of Mac OS, but realised my version of hyperkit failry outdated:
Moved to latest available from
And cleaned up/tried again but yet failing with the same:
|
So guess need to rebuild hyperkit from latest master.. but now I am getting afraid of messing up my docker install since hyperkit is supposedly a core component for it |
Can you try the steps from #882 (comment) ? This will not impact your system-wide hyperkit install. |
Ok yes I did not realize that comment points to just replace the hyperkit within ~/.crc/bin, so tried and failed again:
Start command failed:
|
Do I need to download a different version of crc-driver-hyperkit too? |
crc-driver-hyperkit drivers are bound to the version of CRC. they act as an intermediate between the actual hyperkit binary and CRC. @cfergeau perhaps something caused by macOS Catalina updates that causes hyperkit to fail? |
This is what moby/hyperkit#263 says, assuming it's the same issue. |
that is something that came back from quite a while ago when @praveenkumar and I discussed this. perhaps we need to make crc-driver-hyperkit enforce a minimum version... much higher than 2018 as is now the case. |
Looking more closely at the logs/code, this macos issue may not be hyperkit-related after all (?) https://github.com/code-ready/machine-driver-hyperkit/blob/master/pkg/hyperkit/driver.go#L218 if you look at the logs, this fails between |
I've put a small binary which should exhibit the problem at https://teuf.fedorapeople.org/vmnet.tar.gz. Unpack, and run $ sudo vmnet/vmnet
Password:
mac: 0e:f0:e3:c7:4f:be |
So I tried and hit the issue indeed:
Then I restarted docker to get it to restart the docker bound hyperkit and also killed the hyperkit process spinned up from crc/bin and then vmnet gets the MAC address:
Is there any workaround to get crc to work or need to wait for Mac OS updates then? |
I'm a bit confused by these hyperkit processes which are running. Why was there a crc hyperkit process running? I thought |
So one of the hyperkit processes is owned by docker desktop, the other one was left over from the failed
|
Great to know! Could you do one last test, move away |
I tried but could not repro the error anymore, did the following:
And it worked both times. Now fairly puzzled.. |
Maybe the first time I updated hyperkit with brew the failure was caused by the leftover hyperkit process and subsequent errors have been due to that all along.. have not really restarted my Mac since |
leftover hyperkit process can probably happen and cause these issues... We probably should check more carefully for its presence. Thanks for the additional testing! |
@marchmallow If it possible can you run docker for Mac first and then run crc to see if it is reproducible? We just want to be sure is it because of any hyperkit process or just the one which leftover (zombie one)? |
I had the same issue today, I followed the steps in #882 (comment), but had the same error. after reading other comments here, I restarted my macOS, followed by
worked for me. I was also running into this same issues, which the |
I had the same issue - old hyperkit process was causing the problem as the comment mentioned. Killing that process, |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hello guys, I am trying to install CRC on MacOs Catalina (10.15.4). However, I have received the following error after doing
I run above commands after stopping docker desktop too but the issue is still the same. I run the steps mentioned at #882 (comment) Can anyone please help me to resolve it? :) |
Also getting the same issue as @mayankhacharya. Updated to Catalina 10.15.5 (19F96)
|
I solved the issue on my machine. I disabled "Internet Sharing" and the issue is no longer present. |
@Aenima4six2 "Internet Sharing" option has been disabled on my machine. I still have the issue. |
@mayankhacharya I highly doubt this issue because of Provide following output of the
|
@praveenkumar Now I am getting following error after implementing your suggestion from the comment.
|
Thanks for the disregard bro. The suggestion to disable internet sharing came from feedback on the minikube github issue you referenced, and it worked for me. |
Sorry it didn’t help you. Do you have docker for Mac installed ? |
fork/exec /Users/mayankhacharya/.crc/bin/hyperkit: exec format error
Did you update the environment or modify it? This error occurs when the
file does not have the correct permissions
```
$ crc cleanup
$ crc setup
$ crc start
```
Note: Docker for Mac should not have an effect as we do not share the
hyperkit executables.
…On Sat, May 30, 2020 at 9:27 AM John-Paul Dienst ***@***.***> wrote:
@Aenima4six2 <https://github.com/Aenima4six2> "Internet Sharing" option
has been disabled on my machine. I still have the issue.
Sorry it didn’t help you. Do you have docker for Mac installed ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#882 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAAOZSQSWNZ54R3EYVL5JTRUBOGXANCNFSM4JY66WTQ>
.
--
Gerard Braad | http://gbraad.nl
STEM is the source, but BUILD is how you develop!
[ Better Understanding Involves Learning and Doing ]
|
@Aenima4six2 Yes I do have docker on mac but before running this setup, I stopped it. @gbraad I executed those steps mentioned in comment and then I received the above error. |
|
@gbraad I fixed the above-mentioned error. This URL Now I am getting below error. Before running the execution, I have verified that there wasn't any process running with hyperkit. I have verified many times that my |
Where did you get the binary from? They are included in our release as they are specific to crc as we modified them. I am now confused about the steps you took to make it work. I asked for the ls to confirm the size and flags. A simple 'setup', 'start' is all that is needed to get the dependencies and environment working. Please perform a clean and delete or the crc/bin folder and run setup. After this report back what start does and if failing m share the info about the used binaries. |
@gbraad I followed the documentation when I was installing Based on your suggestion in the last comment, I followed the following steps. After doing all this, I received again the same error log mentioned in comment Before running above steps, I manually checked that there wasn't any process running with hyperkit and my |
@Aenima4six2 I said, I highly doubt not disregarded, Thanks for sharing the issue reference 👍 |
I got the issue again, but on a different version of
Of particular interest, I found that if I didn't kill any existing |
@Aenima4six2 I tried your mentioned steps. I downgraded crc version to I am still getting this error |
@mayankhacharya can you try kubernetes/minikube#4206 (comment) (also check other comments) and also kubernetes/minikube#6143 one, try to use the latest version of crc. |
Just to mention that somehow I got this issue in version 1.11.0 but got past it with Aenima4six2's comment |
I was running into the same issues. Turned out had nothing to do with either bootp or internet sharing, and was due to the fact the mac firewall was enabled. Once I disabled the FW the hyperkit issue was resolved on minikube: kubernetes/minikube#8287 To get it working in crc I had to do a few additional things:
Hopefully this helps anyone whom is still running into issues getting crc working. CRC 1.12 |
Just ran into this issue on a fresh install of crc |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
General information
crc setup
before starting it? YesCRC version
# Put `crc version` output here
CRC status
CRC config
Host Operating System
Steps to reproduce
crc start
Expected
CRC to start
Actual
CRC fails with following error:
Logs
The text was updated successfully, but these errors were encountered: