Chapter 5. Issues on Linux

This section describes CodeReady Containers issues that affect users on a Linux host.

5.1. CodeReady Containers 1.19 is not supported on Red Hat Enterprise Linux 7

The version of qemu-kvm provided in Red Hat Enterprise Linux 7 does not support the q35 machine type used for the CodeReady Containers virtual machine in CodeReady Containers 1.19. As a result, the CodeReady Containers virtual machine cannot be created on Red Hat Enterprise Linux 7.

This issue only exists in CodeReady Containers 1.19 and will be resolved in the next release of CodeReady Containers. Upgrade to the latest CodeReady Containers release once available to resolve this issue.

5.2. Fedora 33 uses systemd-resolved instead of dnsmasq

By default, Fedora 33 uses systemd-resolved for DNS resolution whereas the crc setup command configures DNS through dnsmasq. To configure Fedora 33 for split DNS resolution for the CodeReady Containers cluster, follow these steps:

  1. Clean up after any previous attempts to start CodeReady Containers: 

    $ crc delete
$ crc cleanup

  2. Disable the startup checks for dnsmasq: 

    $ crc config set skip-check-network-manager-config true
$ crc config set skip-check-crc-dnsmasq-file true

  3. Create a /etc/NetworkManager/dispatcher.d/99-crc file with the following contents: 

    #!/bin/sh
# This is a NetworkManager dispatcher script to configure split DNS for
# the 'crc' libvirt network.
# The corresponding bridge is recreated each time the system reboots, so
# it cannot be configured permanently through NetworkManager.
# Changing DNS settings through nmcli requires the connection to go down/up,
# so we directly do the change through resolvectl

export LC_ALL=C

if [ "$1" = crc ]; then
        resolvectl domain crc ~testing
        resolvectl dns crc 192.168.130.11
        resolvectl default-route crc false
fi

exit 0

  4. Make the file executable: 

    $ sudo chmod 755 /etc/NetworkManager/dispatcher.d/99-crc

  5. Start CodeReady Containers: 

    $ crc setup
$ crc start