Change linux default network-mode to user

[lilyLuLiu]

Currently, the Linux default network mode is system. But many issues happen due to different system situations.
For most user, user network mode already satisfied their demands. And user network mode no need to deal with complex system situations.
So after discuss, it's better to set user as default network-mode, making sure CRC works well in default.
If the user requires more functions, they can switch to system network mode.

@gbraad @praveenkumar @anjannath have agreed on this being needed.
It needs to start testing early during December.
In the worst case, we can revert before the new release in January.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign gbraad for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[rohanKanojia]

@lilyLuLiu : Hello, Could you please provide some context on why this change is needed?

[praveenkumar]

/retest

[praveenkumar]

@lilyLuLiu About integration failure I think https://github.com/crc-org/crc/blob/main/pkg/crc/network/types.go#L65 is culprit because settings only apply if we build binary for non installer, we need to change the default here also

[anjannath]

/retest

[openshift-ci]

@lilyLuLiu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-crc	6b1ce3f	link	true	/test e2e-crc

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[karelyatin]

Hi with latest CRC release including this commit 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

$ 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

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

[praveenkumar]

@karelyatin did you use crc cleanup before using this latest version of CRC? can you try following and see if that works?

$ crc delete
$ crc cleanup
$ crc setup

Also you need to unset following settings

crc config unset skip-check-daemon-systemd-sockets
crc config unset skip-check-daemon-systemd-unit

[karlyan]

This break your own document: https://crc.dev/docs/networking/#setting-up-on-a-remote-server
It looks like in linux you change ip from 192.168.130.1 to 127.0.0.1. The haproxy can no longer bind with bind 0.0.0.0:6443

[gbraad]

You can still use system mode. This documented scenario using haproxy is a semi-supported use case. If you have a fix, please let us know or otherwise switch network mode For the document I suggest a note about switching network mode. We do not have an automated test in place at the moment. I see this being for advanced use, especially as network setups can greatly differ and complicated this.

…

On Fri, Feb 21, 2025, 01:37 Shuhuan Yan ***@***.***> wrote: This break your own document: https://crc.dev/docs/networking/#setting-up-on-a-remote-server It looks like in linux you change ip from 192.168.130.1 to 127.0.0.1. The haproxy can no longer bind with bind 0.0.0.0:6443 — Reply to this email directly, view it on GitHub <#4514 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAAOZVVKF3P2GQGK2RTEEL2QYHD3AVCNFSM6AAAAABTVRXMO6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZSGIYTENJQGI> . You are receiving this because you were mentioned.Message ID: ***@***.***> [image: karlyan]*karlyan* left a comment (crc-org/crc#4514) <#4514 (comment)> This break your own document: https://crc.dev/docs/networking/#setting-up-on-a-remote-server It looks like in linux you change ip from 192.168.130.1 to 127.0.0.1. The haproxy can no longer bind with bind 0.0.0.0:6443 — Reply to this email directly, view it on GitHub <#4514 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAAOZVVKF3P2GQGK2RTEEL2QYHD3AVCNFSM6AAAAABTVRXMO6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZSGIYTENJQGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[gbraad]

I filed: crc-org/docs#26 and made a quick-fix in crc-org/docs#25

---

$ crc config set network-mode system

[karlyan]

Thanks for the response.
I like the current user mode. With this new fix I don't need to install haproxy and setup all these proxy config. In our case; we have a pipelline to create crc instance on gcp vm. Later we use ssh tunnel to forward the traffic to local mac machine. With the new user network; I can remove the haproxy code. Just the doc needs to change a little bit.

[gbraad]

We will update the document, but have no indication when this would happen.
So, good to hear using ssh forwards works for you.