-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable veth and bridges on diskless boots. #120
Enable veth and bridges on diskless boots. #120
Conversation
Relevant mention of the possibility of this future work here |
Thoughts @dongsupark ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey, sorry this has slipped. I am not following the change here, what was your issue? Because veth
is ignored here. Sorry again about the delay.
Hi, by default it doesn't seem to me that yy-pxe.network ignores veth devices. I have booted a machine via ipxe (in this case, no root= parameter on the kernel command line). When I try to start a docker container, I get the following set of log messages, and no container is created:
As you can see, docker attempts to configure the network, then NetworkManager also attempts to configure the network, and the container fails to start. I think yy-ipxe is intended to cast a broad net to configure network devices via DHCP, but the bycatch is wireguard, veth, and bridge interfaces which are extremely unlikely to be the things we want to get dhcp from. |
If you want me to make a qemu invocation without |
Bump @tormath1 |
Kicked off the CI with the changes: http://jenkins.infra.kinvolk.io:8080/job/container/job/packages_all_arches/4520/cldsv/ |
Enable veth and bridges on diskless boots.
Previously a rootless boot would allow systemd-networkd to manage unexpected interfaces, and might interfere with the expected operation of bridges, flannel, and veth interfaces.
How to use
Boot flatcar via ipxe or via qemu directly with kernel + initrd, but no root kcmdline
Testing done
Install k3s and observe services to start successfully.