[BUG] OpenShift Local require access to port 443 which is used by another process

[LionelVallet]

General information

• OS: Windows
• Running CRC on: Desktop with PodmanDesktop

CRC version

CRC version: 2.37.1+36d451
OpenShift version: 4.15.14

CRC status

DEBU CRC version: 2.37.1+36d451
DEBU OpenShift version: 4.15.14
DEBU Running 'crc status'
CRC VM:          Stopped
OpenShift:       Stopped (v4.15.14)
RAM Usage:       0B of 0B
Disk Usage:      0B of 0B (Inside the CRC VM)
Cache Usage:     36.45GB

CRC config

- consent-telemetry                     : no

Steps to reproduce

Start OpenShift Local from Podman Desktop

Expected

OpenShift Local start with on a new port or choose port in configuration

Actual

OpenShift Local start error: Error: failed to expose port :443 -> 192.168.127.2:443: listen tcp :443: bind: An attempt was made to access a socket in a way forbidden by its access permissions.

Logs

Before gather the logs try following if that fix your issue

INFO Starting CRC VM for openshift 4.15.14...
failed to expose port :443 -> 192.168.127.2:443: listen tcp :443: bind: An attempt was made to access a socket in a way forbidden by its access permissions.

[praveenkumar]

Some background is part of https://github.com/crc-org/crc/issues/4124 and it is fixed and will be available on upcoming release 2.38.x which going to happen this week. As of now there is no option in podman desktop, crc extension side to choose a different port so better to use the cli as mentioned in the the original issue.

[anjannath]

you can run the command mentioned in this comment: https://github.com/crc-org/crc/issues/4124#issuecomment-2072383036 to choose a different port

[LionelVallet]

Thank you for your help. I will wait for the 2.38 release.