Closed
Description
openedon Jan 5, 2021
General information
- OS: CentOS Linux release 8.3.2011
- Hypervisor: Hyper-V
- Did you run
crc setup
before starting it (Yes/No)? yes
CRC version
# Put the output of `crc version`
CodeReady Containers version: 1.20.0+ef3f80d
OpenShift version: 4.6.6 (embedded in executable)
CRC status
CRC VM: Running
OpenShift: Not Reachable (v4.6.6)
Disk Usage: 15.03GB of 32.72GB (Inside the CRC VM)
Cache Usage: 13.69GB
Cache Directory: /home/redscorpion/.crc/cache
CRC config
#empty
Host Operating System
NAME="CentOS Linux"
VERSION="8"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="8"
PLATFORM_ID="platform:el8"
PRETTY_NAME="CentOS Linux 8"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:8"
HOME_URL="https://centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"
CENTOS_MANTISBT_PROJECT="CentOS-8"
CENTOS_MANTISBT_PROJECT_VERSION="8"
Steps to reproduce
- crc setup
Expected
No error
Actual
End with error
...
INFO Checking if libvirt 'crc' network is active
INFO Starting libvirt 'crc' network
Failed to start libvirt 'crc' network
exit status 1: error: Failed to start network crc
error: COMMAND_FAILED: '/usr/sbin/iptables -w10 -w --table filter --insert LIBVIRT_INP --in-interface crc --protocol tcp --destination-port 67 --jump ACCEPT' failed: iptables: No chain/target/match by that name.
Fix
This fixed the issue for me
$ crc delete -f
$ crc cleanup
$ sudo iptables -t filter -F
$ sudo iptables -t filter -X
$ crc setup
#no error this time
Logs
You can start crc with crc start --log-level debug
to collect logs.
Please consider posting this on http://gist.github.com/ and post the link in the issue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment