Container networks set via `set container network <name>` lose their VRF association when the last member container is restarted.
```
run add container image alpine:latest
set vrf name test table 999
set container network test prefix 192.168.0.0/24
set container network test vrf test
set container name test image alpine:latest
run restart container test
```
Workaround: retriggering something in the network config (e.g., add and remove `no-name-server`) brings it back.
Workaround 2: don't let the network go empty, e.g., by running a //sleep// container
Originally tried on `1.5-rolling-202411260813` but seems to still be an issue in current rolling `2025.04.01-0021-rolling`.