Skip to content
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

nixos/lxc/container: allow useDhcp with LXC containers #358519

Closed
wants to merge 0 commits into from

Conversation

adamcstephens
Copy link
Contributor

#347283 changed the default to exclude non-physical network Kind, but that unfortunately also includes veth which LXC uses for its network interfaces. Re-enable that functionality so users can use networkd with useDHCP.

Things done

  • Built on platform(s)
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
    • sandbox = relaxed
    • sandbox = true
  • Tested, as applicable:
  • Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
  • Tested basic functionality of all binary files (usually in ./result/bin/)
  • 25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)
    • (Package updates) Added a release notes entry if the change is major or breaking
    • (Module updates) Added a release notes entry if the change is significant
    • (Module addition) Added a release notes entry if adding a new NixOS module
  • Fits CONTRIBUTING.md.

Add a 👍 reaction to pull requests you find important.

@github-actions github-actions bot added 6.topic: nixos Issues or PRs affecting NixOS modules, or package usability issues specific to NixOS 8.has: module (update) This PR changes an existing module in `nixos/` labels Nov 23, 2024
@player131007
Copy link
Contributor

Wouldn't it be better to add a separate 99-veth-default-dhcp that matches veth interfaces instead?

@ofborg ofborg bot added 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin 10.rebuild-linux: 1-10 labels Nov 24, 2024
@adamcstephens
Copy link
Contributor Author

Wouldn't it be better to add a separate 99-veth-default-dhcp that matches veth interfaces instead?

What makes that better?

@player131007
Copy link
Contributor

Previously the default behavior was to match both physical and virtual ethernet interfaces. I think we should keep it instead of only enabling for veth.

@adamcstephens
Copy link
Contributor Author

adamcstephens commented Nov 24, 2024

In what scenario would the physical unit match any devices in an LXC container?

@player131007
Copy link
Contributor

Maybe when an interface is passed through (using lxc.net.*.type = phys)?

@adamcstephens
Copy link
Contributor Author

Sigh. This is now here. #358806

I suspect phys users of raw lxc are quite rare, but easy enough to support. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
6.topic: nixos Issues or PRs affecting NixOS modules, or package usability issues specific to NixOS 8.has: module (update) This PR changes an existing module in `nixos/` 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin 10.rebuild-linux: 1-10
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants