crc: [BUG] failed to expose port :80 -> 192.168.127.2:80: listen tcp :80: bind: address already in use

General information

  • OS: macOS
  • Hypervisor: vfkit
  • Did you run crc setup before starting it (Yes)?
  • Running CRC on: Laptop

CRC version

# Put `crc version` output here

CRC version: 2.5.1+5b02b826
OpenShift version: 4.10.18
Podman version: 4.1.0

CRC status

DEBU CRC version: 2.5.1+5b02b826
DEBU OpenShift version: 4.10.18
DEBU Podman version: 4.1.0
DEBU Running 'crc status'
DEBU Checking file: /Users/carlosroberto/.crc/machines/crc/.crc-exist
DEBU Checking file: /Users/carlosroberto/.crc/machines/crc/.crc-exist
CRC VM:          Stopped
OpenShift:       Stopped (v4.10.18)
Podman:
Disk Usage:      0B of 0B (Inside the CRC VM)
Cache Usage:     36.98GB
Cache Directory: /Users/carlosroberto/.crc/cache
DEBU Running 'sw_vers -productVersion'

CRC config

- consent-telemetry                     : yes
- cpus                                  : 5
- enable-experimental-features          : true
- memory                                : 10000
- skip-check-m1-cpu                     : true

Host Operating System

ProductName:	macOS
ProductVersion:	12.5
BuildVersion:	21G5063a

Steps to reproduce

  1. install: $ open crc-macos-installer.pkg
  2. $ crc setup (ok !!!)
  3. $ crc start

Expected

start custer

Actual

INFO Checking if running as non-root
INFO Checking if crc-admin-helper executable is cached
INFO Checking for obsolete admin-helper executable
INFO Checking if running on a supported CPU architecture
INFO Checking minimum RAM requirements
INFO Checking if crc executable symlink exists
INFO Checking if running emulated on a M1 CPU
WARN Skipping above check...
INFO Checking if vfkit is installed
INFO Checking if old launchd config for tray and/or daemon exists
INFO Checking if crc daemon plist file is present and loaded
INFO Loading bundle: crc_vfkit_4.10.18_amd64...
INFO Starting CRC VM for OpenShift 4.10.18...
failed to expose port :80 -> 192.168.127.2:80: listen tcp :80: bind: address already in use

Logs

Before gather the logs try following if that fix your issue

$ crc delete -f
$ crc cleanup
$ crc setup
$ crc start --log-level debug
INFO Creating CRC VM for OpenShift 4.10.18...
DEBU Running pre-create checks...
DEBU Creating machine...
DEBU /Users/carlosroberto/.crc/machines/crc/crc.img is already 33285996544 bytes
INFO Generating new SSH key pair...
INFO Generating new password for the kubeadmin user
DEBU Created /Users/carlosroberto/.crc/machines/crc/.crc-exist
DEBU Machine successfully created
DEBU Checking file: /Users/carlosroberto/.crc/machines/crc/.crc-exist
INFO Starting CRC VM for OpenShift 4.10.18...
DEBU Running 'sw_vers -productVersion'
failed to expose port :80 -> 192.168.127.2:80: listen tcp :80: bind: address already in use

Please consider posting the output of crc start --log-level debug on http://gist.github.com/ and post the link in the issue.

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 15 (6 by maintainers)

Most upvoted comments

Hi, unfortunately I already tried using the command: sudo lsof -nP -i4TCP:80, however, the only ports 80 are web ports on IP6. I’ve already stopped the services and it’s still in the same situation. However, if I remove the CRC Red hat and install the CRC OKD, it works normally. However, CRC OK has version 4.8, and I need 4.10 from Red Hat, to access the operators and test.

carlosroberto in ~ took 3s sudo lsof -nP -i4TCP:80
Password:
COMMAND   PID USER   FD   TYPE             DEVICE SIZE/OFF NODE NAME
httpd     143 root    4u  IPv6 0x47cb843eb06ed32d      0t0  TCP *:80 (LISTEN)
com.avast 486 root   74u  IPv4 0x47cb8451ddc865e5      0t0  TCP 100.111.52.195:49648->77.234.42.40:80 (ESTABLISHED)
httpd     843 _www    4u  IPv6 0x47cb843eb06ed32d      0t0  TCP *:80 (LISTEN)

Do you have any other ideas that could solve this? Possibly the OKD CRC VM got port 80, and it doesn’t release even when to remove the OKD CRC, I use:

$ crc delete -f
$ crc cleanup

Thank you so much friend!!!