In case this has not already been noted (a quick search seems to indicate not) there is an issue when using the installer on hosts that contain non-routing network interfaces (for instance, docker bridges, VM networks etc) - this applied to at least Windows and Linux hosts.
It would appear that the installer selects one of the above interfaces, and, when run, will collect the required information, ask for permission to proceed and then stop for a while before reporting Read timed out
The workaround is to (temporarily) remove these interfaces (shut down docker etc) and attempt an installation before reinstating them.
It would appear that the installer selects one of the above interfaces, and, when run, will collect the required information, ask for permission to proceed and then stop for a while before reporting Read timed out
The workaround is to (temporarily) remove these interfaces (shut down docker etc) and attempt an installation before reinstating them.