Multipass Dashboard Launch issues

Multipass
,
1

I have four Mac servers running Multipass. The issue below is on the M1 Mac Studio Ultra. I had a similar issue (below) on my 2013 Mac Pro at the same time. Which seems strange. Two different servers. And I didn’t update MacOS or Multipass. Below I address the issue I just solved on there Ultra.

Yesterday I started using the latest dashboard for launching new Ubuntu instances, which worked for a while, but then the dashboard hung [waiting for daemon]. I tried rebooting. Nothing worked. Finally, after several hours, I figured it out. One of the instances I launched was trying to get an IP from DHCP. The only way to resolve was to delete it. But I spent a day trying to figure out how to recover my dev environment. Now I no longer use Dashboard Launch - too early to trust. So far it seems good from the command line. And I use the dashboard for all other features.

The dashboard is highly convenient, productive and scalable. Gives it more of a private cloud feel. I’m loving Multipass speed of building, tearing down, monitoring and managing VMs (instances). I have 50 instances on the Ultra, and about 20 on each of the other servers. And I am running process heavy AI (CPU and GPU). Example: llama3.1 400B Agent RAG. inferencing (llama 3.1 400B embeddings to Chromadb VectorIndex solution space optimization and explanatory reasoning). Doesn’t take long for the hardware to pay for itself. Thanks to Multipass. In the past I did this with VMWare Fusion. it’s too heavy. Multipass instances are light, quick, fast and ideal.

2

UPDATE: More detail. if I add an apache server as the first component to my new Instance, it builds it, but eventually goes into the same issuer [waiting for daemon].

Turns out, even if I don’t install Apache, as soon as I add supporting apache libraries, it hangs on DHCP IP lease. So if I create the instance, and add other components. Then come back to Apache, after passing of a few minutes, it works. I think it might something to do with trying to get a DHCP lease before it’s listening. And maybe that gets into a deadly embrace. Maybe if I create the Instance, and just leave it for a few minutes, and then add Apache, that might work too.