Incus 6.15: Launching new instance, it gets around 20 IP addresses that clear up in a few seconds #2350
Description
Is there an existing issue for this?
- There is no existing issue for this bug
Is this happening on an up to date version of Incus?
- This is happening on a supported version of Incus
Incus system details
$ incus version
Client version: 6.15
Server version: 6.15
$Instance details
When launching an instance (container or VM), you can immediately run incus list mynewcontainer to see what's going on. The output of the command shows that the instance has multiple IP addresses (plus 2 multicast), both IPv4 and IPv6. After a few seconds, the list clears up and the instance looks and works properly.
Example output for container (also happens with VM)
$ incus list mynewcontainer
...
| clust3 | RUNNING | 224.0.0.252 (incusbr0) | ff02::1:ffe4:82a7 (incusbr0) | VIRTUAL-MACHINE | 0 |
| | | 224.0.0.251 (incusbr0) | ff02::1:ffc4:c4b2 (incusbr0) | | |
| | | 224.0.0.22 (incusbr0) | ff02::1:ffa9:2601 (incusbr0) | | |
| | | 10.133.19.91 (incusbr0) | ff02::1:ffa4:fefe (incusbr0) | | |
| | | 10.133.19.68 (incusbr0) | ff02::1:ff9f:b103 (incusbr0) | | |
| | | 10.133.19.57 (incusbr0) | ff02::1:ff97:cec8 (incusbr0) | | |
| | | 10.133.19.50 (incusbr0) | ff02::1:ff96:7a3c (incusbr0) | | |
| | | 10.133.19.34 (incusbr0) | ff02::1:ff95:6c2d (incusbr0) | | |
| | | 10.133.19.28 (incusbr0) | ff02::1:ff92:59e6 (incusbr0) | | |
| | | 10.133.19.26 (incusbr0) | ff02::1:ff72:d3ab (incusbr0) | | |
| | | 10.133.19.24 (incusbr0) | ff02::1:ff65:c7e1 (incusbr0) | | |
| | | 10.133.19.233 (incusbr0) | ff02::1:ff60:aa56 (incusbr0) | | |
| | | 10.133.19.23 (incusbr0) | ff02::1:ff50:fc90 (incusbr0) | | |
| | | 10.133.19.227 (incusbr0) | ff02::1:ff4d:cd4e (incusbr0) | | |
| | | 10.133.19.224 (incusbr0) | ff02::1:ff4c:c925 (incusbr0) | | |
| | | 10.133.19.214 (incusbr0) | ff02::1:ff4c:2408 (incusbr0) | | |
| | | 10.133.19.193 (incusbr0) | ff02::1:ff38:e035 (incusbr0) | | |
| | | 10.133.19.187 (incusbr0) | ff02::1:ff31:9448 (incusbr0) | | |
| | | 10.133.19.181 (incusbr0) | ff02::1:3 (incusbr0) | | |
| | | 10.133.19.176 (incusbr0) | ff02::1 (incusbr0) | | |
| | | 10.133.19.159 (incusbr0) | fd42:f50e:821:39d5:1266:6aff:fee4:82a7 (incusbr0) | | |
| | | 10.133.19.14 (incusbr0) | fd42:f50e:821:39d5:1266:6aff:fec4:c4b2 (incusbr0) | | |
| | | 10.133.19.122 (incusbr0) | fd42:f50e:821:39d5:1266:6aff:fea9:2601 (incusbr0) | | |
| | | 10.133.19.121 (incusbr0) | fd42:f50e:821:39d5:1266:6aff:fea4:fefe (incusbr0) | | |
| | | 10.133.19.10 (incusbr0) | fd42:f50e:821:39d5:1266:6aff:fe9f:b103 (incusbr0) | | |
| | | | fd42:f50e:821:39d5:1266:6aff:fe97:cec8 (incusbr0) | | |
| | | | fd42:f50e:821:39d5:1266:6aff:fe96:7a3c (incusbr0) | | |
| | | | fd42:f50e:821:39d5:1266:6aff:fe95:6c2d (incusbr0) | | |
| | | | fd42:f50e:821:39d5:1266:6aff:fe92:59e6 (incusbr0) | | |
| | | | fd42:f50e:821:39d5:1266:6aff:fe79:505a (incusbr0) | | |
| | | | fd42:f50e:821:39d5:1266:6aff:fe72:d3ab (incusbr0) | | |
| | | | fd42:f50e:821:39d5:1266:6aff:fe65:c7e1 (incusbr0) | | |
| | | | fd42:f50e:821:39d5:1266:6aff:fe60:aa56 (incusbr0) | | |
| | | | fd42:f50e:821:39d5:1266:6aff:fe50:fc90 (incusbr0) | | |
| | | | fd42:f50e:821:39d5:1266:6aff:fe4d:cd4e (incusbr0) | | |
| | | | fd42:f50e:821:39d5:1266:6aff:fe4c:c925 (incusbr0) | | |
| | | | fd42:f50e:821:39d5:1266:6aff:fe4c:2408 (incusbr0) | | |
| | | | fd42:f50e:821:39d5:1266:6aff:fe38:e035 (incusbr0) | | |
| | | | fd42:f50e:821:39d5:1266:6aff:fe2c:e919 (incusbr0) | | |
...
Instance log
No response
Current behavior
No response
Expected behavior
The incus list command should only show the appropriate IP addresses that the instance is supposed to use.
Steps to reproduce
- Launch an instance,
incus launch images:debian/13/cloud mynewcontainer - Run somewhat quickly, within a second,
incus list mynewcontainer - The output of the
incus listcommand should show a bit list of IP addresses as shown above.
Metadata
Metadata
Assignees
Labels
No labels