Changing netdev settings in an unpriviliged container requires a reboot in order to take effect

Maybe it is obvious to the initated but it was not to me and thus like to share the knowledge that changing the settings of a netdev, particularly tun/tap though, in an unpriviliged container requires a reboot of the container in order to take effect.

systemctl restart systemd-networkd will not do the trick since producing

systemd[1]: systemd-networkd.service: Failed to reset devices.list: Operation not permitted