You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your enhancement related to a problem? Please describe
I tried setting up CRC on Windows (11 64-Bit) and am using wsl-vpnkit for my company's VPN which by default uses Port 2222 for gvproxy.
When setting up CRC, I only figured out that crc wasn't set up properly when trying to start it (with crc start), however I poked around, thinking this was an error with previous installations of crc, podman desktop or similiar.
The crc setup command only shows the following, kind of nondescript message:
INFO Checking SSH port availability
crc uses port 2222 to run SSH
before returning control to my shell.
Describe the solution you'd like
The message displayed could be of type "ERROR" and be more verbose about the port being already in use (which is already obvious in debug log level but should be obvious in an actual error).
Describe alternatives you've considered
I also tried searching in documentation for "2222" and didn't find anything, so this could also be documented more thoroughly
Additional context
No response
The text was updated successfully, but these errors were encountered:
PirMei
changed the title
crc setup - Make error message for Port 2222 already in use more explicit
crc setup - Make error message for port 2222 already in use more explicit
Mar 5, 2025
Component
CLI
Is your enhancement related to a problem? Please describe
I tried setting up CRC on Windows (11 64-Bit) and am using wsl-vpnkit for my company's VPN which by default uses Port 2222 for gvproxy.
When setting up CRC, I only figured out that crc wasn't set up properly when trying to start it (with
crc start
), however I poked around, thinking this was an error with previous installations of crc, podman desktop or similiar.The
crc setup
command only shows the following, kind of nondescript message:before returning control to my shell.
Describe the solution you'd like
The message displayed could be of type "ERROR" and be more verbose about the port being already in use (which is already obvious in debug log level but should be obvious in an actual error).
Describe alternatives you've considered
I also tried searching in documentation for "2222" and didn't find anything, so this could also be documented more thoroughly
Additional context
No response
The text was updated successfully, but these errors were encountered: