Repository navigation
Closed
Labels
kind/documentationDocumentation issues.Documentation issues.kind/questionStart a discussionStart a discussionos/linuxos/macosos/windowspoints/3priority/trivialstatus/need more informationIssue needs more information before it will be looked atIssue needs more information before it will be looked atstatus/peer review requiredPeer review by assignee is required before being merged;Peer review by assignee is required before being merged;status/staleIssue went stale; did not receive attention or no reply from the OPIssue went stale; did not receive attention or no reply from the OP
Description
The getting started guide does not mention anywhere e.g. "/etc/hosts" or "resolv.conf". I'd like, as a user, if I consider using CRC, to know beforehand, what it's going to touch on my laptop - both as root/sudo (/etc/*) and in my home directory.
Perhaps better not have this hard-coded in docs/getting-started but have a 'crc' sub-command to show it.
What I found out so far (by having /etc/ maintained in git and looking at my home directory, didn't check elsewhere nor the code):
crc setup:
- Creates /etc/NetworkManager/conf.d/crc-nm-dnsmasq.conf
- Creates /etc/NetworkManager/dnsmasq.d/crc.conf
- Adds my account to the group 'libvirt'
- Creates /etc/libvirt/qemu/networks/autostart/crc.xml
- Creates /etc/libvirt/qemu/networks/crc.xml
- Changes /etc/resolv.conf (and see also After crc setup dnsmasq break configuration for public dns as port is already bound to another process (conflict) #1663 which I ran into)
crc start:
- Changes /etc/hosts
- Creates /etc/libvirt/qemu/crc.xml
- Creates /etc/libvirt/storage/crc.xml
Both of them (didn't check which - likely setup):
- Create $HOME/.config/systemd/user/crc* - user systemd units
- Create $HOME/.crc - crc itself - perhaps should be made configurable somehow
Reacted by Coleman McFarland
Metadata
Metadata
Assignees
Labels
kind/documentationDocumentation issues.Documentation issues.kind/questionStart a discussionStart a discussionos/linuxos/macosos/windowspoints/3priority/trivialstatus/need more informationIssue needs more information before it will be looked atIssue needs more information before it will be looked atstatus/peer review requiredPeer review by assignee is required before being merged;Peer review by assignee is required before being merged;status/staleIssue went stale; did not receive attention or no reply from the OPIssue went stale; did not receive attention or no reply from the OP
Activity
[-][DOCS] Missing documentation about what CRC changes in the maching[/-][+][DOCS] Missing documentation about what CRC changes in the machine[/+][-][DOCS] Missing documentation about what CRC changes in the machine[/-][+]Missing information about what CRC changes in the machine[/+]gbraad commentedon Feb 10, 2022
Added the trivial priority as our focus is on merging our development branch to master. this means some of this might change. Will be reprioritized after the release.
gbraad commentedon Feb 10, 2022
The
sudousage is only on the setup phase. We explicitly disallow the use of therootoradministratorto execute CRC. If administrative actions are needed, this might be performed by the admin-helper. However, this is only the case on Windows.One of my colleagues will fill you in on more details.
We do not consider these changes performed by CRC. We ask qemu+kvm to create a VM and the daemon of the virtualization stack creates these files. It depends on the target distribution where these files are created or perhaps even additional changes are made.
With this we create our own bridge to prevent overlap or conflicts with the user specified network setup. This is only the case when 'system mode networking' is used.
It might help to also have a look at the preflight checks we perform. These checks determine if the system is ready for use of CRC, and when not, the preflight has fixes that make these changes as aforementioned.
gbraad commentedon Feb 11, 2022
This should have been resolved as we support setups with
systemd-resolved. If not, this needs further investigation and more information to explain what the situation is and what you did to resolve this.cfergeau commentedon Mar 15, 2022
Networking setup is indeed more complex than that:
If using system networking
If systemd-resolved is used on the system
/etc/NetworkManager/dispatcher.d/99-crc.shis createdIf systemd-resolved is not used
/etc/NetworkManager/conf.d/crc-nm-dnsmasq.conf/etc/NetworkManager/dnsmasq.d/crc.conf/etc/resolv.confis not modified by crc, this is a consequence of the configuration changes above, and an implementation detail of NetworkManager dnsmasq support.If using usermode networking
/etc/hostswill be modified by a suid helperIf I remember correctly
/etc/hostsis also modified in system networking even if it's not required there.cfergeau commentedon Mar 15, 2022
crcon linux uses libvirt to manage its VM, and it creates acrcstorage pool, acrcnetwork, and acrcdomain inqemu:///system. I agree how libvirtd stores this on the filesystem is an internal libvirtd implementation detail.stale commentedon Jun 4, 2022
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.