Hello, with incus 6.1 addresses were shown. Not anymore with incus 6.2.
[alain@ALPHA:~]$ incus list
+------+---------+------+------+-----------+-----------+
| NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS |
+------+---------+------+------+-----------+-----------+
| nixo | RUNNING | | | CONTAINER | 0 |
+------+---------+------+------+-----------+-----------+
[alain@ADRIEN:~]$ incus list
+-------------+---------+------+------+-----------+-----------+
| NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS |
+-------------+---------+------+------+-----------+-----------+
| adguardhome | RUNNING | | | CONTAINER | 0 |
+-------------+---------+------+------+-----------+-----------+
| lxconsole | RUNNING | | | CONTAINER | 0 |
+-------------+---------+------+------+-----------+-----------+
| nixo-prem | RUNNING | | | CONTAINER | 0 |
+-------------+---------+------+------+-----------+-----------+
[alain@ALPHA:~]$ ip a
...
5: bridge0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 06:5b:64:ec:3d:1a brd ff:ff:ff:ff:ff:ff
inet 192.168.3.102/24 scope global bridge0
valid_lft forever preferred_lft forever
inet6 fe80::ca4d:44ff:fe24:a1c1/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
...
See, nixo is just a brand new container created via:
incus launch images:nixos/unstable nixo --profile default --profile bridgeprofile -c security.nesting=true -c boot.autostart=true
[alain@ALPHA:~]$ incus config show nixo -e
architecture: x86_64
config:
boot.autostart: "true"
image.architecture: amd64
image.description: Nixos unstable amd64 (20240608_01:00)
image.os: Nixos
image.release: unstable
image.requirements.secureboot: "false"
image.serial: "20240608_01:00"
image.type: squashfs
image.variant: default
security.nesting: "true"
volatile.base_image: 14316d6dbb041e24f0d8ec1f0ecb60289b50252e6fd8ab469b27e1933c914713
volatile.cloud-init.instance-id: b4515206-930d-435b-b297-999cdb29507f
volatile.eth0.host_name: vethfd3a5393
volatile.eth0.hwaddr: 00:16:3e:7b:62:9f
volatile.idmap.base: "0"
volatile.idmap.current: '[{"Isuid":true,"Isgid":false,"Hostid":1000000,"Nsid":0,"Maprange":1000000000},{"Isuid":false,"Isgid":true,"Hostid":1000000,"Nsid":0,"Maprange":1000000000}]'
volatile.idmap.next: '[{"Isuid":true,"Isgid":false,"Hostid":1000000,"Nsid":0,"Maprange":1000000000},{"Isuid":false,"Isgid":true,"Hostid":1000000,"Nsid":0,"Maprange":1000000000}]'
volatile.last_state.idmap: '[]'
volatile.last_state.power: RUNNING
volatile.last_state.ready: "false"
volatile.uuid: 24e51271-0dd8-4247-968d-38ddfeba3f24
volatile.uuid.generation: 24e51271-0dd8-4247-968d-38ddfeba3f24
devices:
eth0:
name: eth0
nictype: bridged
parent: bridge0
type: nic
root:
path: /
pool: default
type: disk
ephemeral: false
profiles:
- default
- bridgeprofile
stateful: false
description: ""
[alain@ALPHA:~]$ incus shell nixo
[root@nixos:~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host proto kernel_lo
valid_lft forever preferred_lft forever
8: eth0@if9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 00:16:3e:7b:62:9f brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 192.168.3.18/24 metric 1024 brd 192.168.3.255 scope global dynamic eth0
valid_lft 85356sec preferred_lft 85356sec
inet6 fe80::216:3eff:fe7b:629f/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
Why the “if9” in eth0@if9 ?
Thank you.
