crc setup fails in case of daemon settings are skipped

[praveenkumar]

Hi with latest CRC release crc not starting, is that expected?

$ cat /etc/redhat-release 
Red Hat Enterprise Linux release 9.4 (Plow)
$ crc version
CRC version: 2.47.0+457b65
OpenShift version: 4.17.14
MicroShift version: 4.17.14

Configuration

$ crc config view
- consent-telemetry                     : no
- cpus                                  : 24
- disk-size                             : 100
- kubeadmin-password                    : 12345678
- memory                                : 48000
- pull-secret-file                      : /home/ocp_dev/install_yamls/devsetup/pull-secret.txt
- skip-check-daemon-systemd-sockets     : true
- skip-check-daemon-systemd-unit        : true

$ crc setup
[...]
INFO Uncompressing /home/ocp_dev/.crc/cache/crc_libvirt_4.17.14_amd64.crcbundle 
crc.qcow2:  19.43 GiB / 19.43 GiB [------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------] 100.00%
oc:  158.81 MiB / 158.81 MiB [-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------] 100.00%
Your system is correctly setup for using CRC. Use 'crc start' to start the instance
+ /home/ocp_dev/bin/crc start                                     
Is 'crc daemon' running? Cannot reach daemon API: Get "http://unix/api/version": dial unix /home/ocp_dev/.crc/crc-http.sock: connect: no such file or directory
+ /home/ocp_dev/bin/crc console --credentials                     
Get "http://unix/api/webconsoleurl": dial unix /home/ocp_dev/.crc/crc-http.sock: connect: no such file or directory
++ /home/ocp_dev/bin/crc oc-env                   
Machine does not exist. Use 'crc start' to create it

With explicitly setting network mode i t works fine:-
$ crc config set network-mode system
$ crc setup
$ crc start

Originally posted by @karelyatin in #4514 (comment)

[praveenkumar]

Since the user had following setting as part of setup it is not able to create the daemon socket which is required for user mode networking.

- skip-check-daemon-systemd-sockets     : true
- skip-check-daemon-systemd-unit        : true

Unset those setting solve the issue for the user. We need to make sure that if user is using network mode as user those setting shouldn't skipped.

[cfergeau]

We need to make sure that if user is using network mode as user those setting shouldn't skipped.

It's ok to disable these as long as you know that you will need to start crc daemon by yourself before using crc with usermode networking. It's not much different from other presets (you can skip libvirt install/configuration, but crc won't work if you don't make sure by yourself that libvirt is correctly setup)

The problem here is that they were disabled and the (default) network mode changed.