-
Notifications
You must be signed in to change notification settings - Fork 6
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
Failed to run example docker instance #22
Comments
@jjaychen1e Could you please also share if its intel or m1 mac |
@balajiv113 Thanks for replying, I'm using a M1 Mac. |
Thanks for the info. Will check and let you know |
I found a bug in code which looked for ssh private key before it is generated. I have just released a new version v0.0.4. To update, just running |
@balajiv113 I've tried v0.0.4, I got another error when run
log:
I also tried to remove |
Ah !! Thanks for checking it out. Let me take a look again. |
Also if possible could you please share the log under |
I'm sorry, it's empty. I upload all log files under |
@jjaychen1e The issue was, for m1 mac the kernel, disk images should be arm one. But it was picking amd images. |
It's almost the same(version 0.0.4-1):
|
Hope you have tried by removing the ~/.macvz folder. If not could you give a try once. |
I tried again, but I got the same log. Thanks for you patience!! |
Thanks a lot for testing 👍 Will do a full test with M1 and let you know ASAP. |
I'd like to get someone else to confirm this, but @jjaychen1e if, per chance, you're running the latest macOS 13 Beta, I believe this might be an issue with VZLinuxBootLoader itself in this release |
I'm using macOS 12.4 |
same error macOs 12.2.1 (M1) |
Thanks @daudcanugerah for double checking and verifying. |
@jjaychen1e Can you please try to do |
ok i try |
|
@daudcanugerah Thanks for trying it out :) |
after reinstall macvz, still get same error |
@daudcanugerah Same to me.
|
@jjaychen1e issues that may be related: |
@jjaychen1e & @daudcanugerah There is still 1 issue /dev/rtc file is not created for arm instance for some reason due to this, apt update is failing. You could start plain ubuntu (without install docker scripts) and install docker manually, this is working fine |
There's still some kind of issue.
images:
- kernel: "https://cloud-images.ubuntu.com/releases/focal/release/unpacked/ubuntu-20.04-server-cloudimg-amd64-vmlinuz-generic"
initram: "https://cloud-images.ubuntu.com/releases/focal/release/unpacked/ubuntu-20.04-server-cloudimg-amd64-initrd-generic"
base: "https://cloud-images.ubuntu.com/releases/focal/release/ubuntu-20.04-server-cloudimg-amd64.tar.gz"
arch: "x86_64"
- kernel: "https://cloud-images.ubuntu.com/releases/focal/release/unpacked/ubuntu-20.04-server-cloudimg-arm64-vmlinuz-generic"
initram: "https://cloud-images.ubuntu.com/releases/focal/release/unpacked/ubuntu-20.04-server-cloudimg-arm64-initrd-generic"
base: "https://cloud-images.ubuntu.com/releases/focal/release/ubuntu-20.04-server-cloudimg-arm64.tar.gz"
arch: "aarch64"
mounts:
- location: "~"
writable: true
disk: 20GB
portForwards:
- guestPortRange:
- 1
- 65535
hostIP: 0.0.0.0
hostResolver:
enabled: true
hosts:
host.ubuntu.internal: host.macvz.internal
|
Describe the bug
FATA[0015] hostagent ("/Users/jjaychen/.macvz/docker/vz.pid") did not start up in 15s (hint: see "/Users/jjaychen/.macvz/docker/ha.stderr.log")
To Reproduce
Run
macvz start https://raw.githubusercontent.com/mac-vz/macvz/main/examples/docker.yaml
, ormccvc start docker
Versions (please complete the following information):
Additional context
{"level":"fatal","msg":"stat /Users/jjaychen/.macvz/_config/user: no such file or directory","time":"2022-07-13T23:32:10+08:00"}
The text was updated successfully, but these errors were encountered: