nspawn should support passing wifi adapters to containers, like other environments (LXC, …) apparently can do · Issue #7873 · systemd/systemd
but it is actually working if you do it manually.
removed the wireless network adapter from container:
cat /etc/systemd/nspawn/server037.nspawn
[Exec]
PrivateUsers=False
[Network]
Bridge=br0
starting the container without error:
machinectl start server037
container status is green:
machinectl status server037
server037(c9f48eb179fb4b1c9eb0a6abd0174047)
Since: Mon 2018-01-15 19:03:08 CET; 13s ago
Leader: 11352 (systemd)
Service: systemd-nspawn; class container
Root: /srv/machines/server037
Iface: br0
Address: 192.168.178.37
OS: Debian GNU/Linux buster/sid
Unit: systemd-nspawn@server037.service
├─payload
│ ├─init.scope
│ │ └─11352 /lib/systemd/systemd
add the wireless network adapter to the nspawn container:
iw phy phy0 set netns 11352
works well:
machinectl shell server037 /sbin/ip addr show wlx001c4afd2f29
Connected to machine server037. Press ^] three times within 1s to exit session.
4: wlx001c4afd2f29: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:1c:4a:fd:2f:29 brd ff:ff:ff:ff:ff:ff
Connection to machine server037 terminated.
can you please have a second look? it looks like systemd is not taking into consideration that for wireless adapters the whole interface needs to be moved to the namespace: