It could be that the timeout occurs very quickly and does not give time to download the resources.
In another project I used the command several times with --force and finally I can get it running, but not in this one.
If I try to access the resources from the browser, they download with no problem.
➜ Trellis trellis new nomanisanisland.com
Creating new Trellis project in /Users/aitor/Documents/Trellis/nomanisanisland.com
Site domain [nomanisanisland.com]:
Aborting: error while downloading Trellis
Error fetching release information from the GitHub API: Get "https://api.github.com/repos/roots/trellis/releases/latest": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
This could be a temporary network error. Please delete this project folder and try again.
It seems that suddenly it works. The problem may be that when deleting virtual machines with trellis vm delete, the process did not finish correctly and some kind of configuration is left somewhere. I have looked in etc/hosts and the entries are removed fine. Is there somewhere else I should look into?
trellis vm stop
Running command => limactl stop nomanisanisland.com
INFO Sending SIGINT to hostagent process 10248
INFO Waiting for the host agent and the driver processes to shut down
INFO [hostagent] 2023/05/09 19:08:35 tcpproxy: for incoming conn 127.0.0.1:51156, error dialing "192.168.5.15:22": connect tcp 192.168.5.15:22: no route to host
INFO [hostagent] Received SIGINT, shutting down the host agent
INFO [hostagent] Shutting down the host agent
INFO [hostagent] Stopping forwarding "/run/lima-guestagent.sock" (guest) to "/Users/aitor/.lima/nomanisanisland.com/ga.sock" (host)
INFO [hostagent] Shutting down VZ
ERRO [hostagent] dhcp: unhandled message type: RELEASE
INFO [hostagent] panic: runtime/cgo: misuse of an invalid Handle
INFO [hostagent] goroutine 17 [running, locked to thread]:
INFO [hostagent] runtime/cgo.Handle.Value(...)
INFO [hostagent] /usr/local/Cellar/go/1.20.3/libexec/src/runtime/cgo/handle.go:124
INFO [hostagent] github.com/Code-Hex/vz/v3.changeStateOnObserver(0x0, 0xc000006601?)
INFO [hostagent] /Users/brew/Library/Caches/Homebrewfirstname.lastname@example.org/virtualization.go:160 +0xb4
FATA did not receive an event with the "exiting" status
Error stopping VM
exit status 1
In the last tests I’ve done starting virtual machines from scratch everything has worked fine (except the mentioned panic runtime when stopping the machine, which is a known problem in Lima). The original problem seems to have disappeared. If it comes back, I’ll open the thread again.
I don’t understand what was the cause because the problem persisted a while even after the Github incident was fixed.