Open cmoulliard opened 5 years ago
Cannot reproduce this, unfortunately. Maybe it is Mac-specific ?
You could try comparing with whatever info VBoxManage
returns
@cmoulliard I faced the same issue. I replaced the tinycore-based box
with fedora-based VM. I continue to name it box
for convenience.
podman-machine create --virtualbox-boot2podman-url \
https://github.com/snowjet/boot2podman-fedora-iso/releases/download/d1bb19f/boot2podman-fedora.iso \
--virtualbox-memory="4096" \
--virtualbox-share-folder ~/Code:code \
box
It has a downside of booting twice as slow, but it consistently works for me:
$ podman-machine start
Starting "box"...
(box) Check network to re-create if needed...
(box) Waiting for an IP...
Machine "box" was started.
Waiting for SSH to be available...
Detecting the provisioner...
Started machines may have new IP addresses. You may need to re-run the `podman-machine env` command.
I don't think this is relevant but I also tried removing all host-only networks under File > Host Network Manager.
Issue
On macos, we can't get the IP address of the VM running on Virtualbox