This message was deleted.
# harvester
a
This message was deleted.
a
I've never used WSL, but just curious - how much CPU and RAM have you given to Harvester? I tried ages ago in a KVM VM with only 2CPUs and 8GiB RAM and it just never worked. I found I needed at least 4 CPUs...
(I'm pretty sure that "dial 10.x.x.x ... connection refused" thing happens periodically for a while until everything is up and running, so it should stop doing that eventually...)
n
Hi @ambitious-daybreak-95996 I have used 16G mem, 12 CPU cores and 300GB disk. The setup is in the same status after several hours. I did not have the same issue when going with the same setup as a VM with same specs that was hosted a normal Linux host and not on WSL2 🤔 I can run normally other Linux VMs on WSL2.
a
That certainly sounds like sufficient CPU, memory and disk to have it behave sensibly (it doesn't meet the production requirements, but it should at least actually run!), and several hours is way too long for setup to complete 😕 I'm not sure where to suggest looking next for diagnostic information under WSL2 though. Maybe someone else has an idea?