You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In short, incus is writing the project name into the domain field when creating the corresponding dnsmasq host file for each container at /var/lib/incus/networks/incusbr0/dnsmasq.hosts/<project>_<container>.<network interface>
Instead I would expect it to use the value of dns.domain for the bridge network whether configured explicitly or left to default setting (incus).
Per @candlerb, in practice this doesn't seem to affect actual operation, just generates the warning messages. However the behaviour does appear to be incorrect.
Steps to reproduce
Create a new project
Create a container in the project which uses the default network for ipv4 and ipv6
Read the contents of /var/lib/incus/networks/incusbr0/dnsmasq.hosts/<project>_<container>.<network interface> and note the domain written in the file
Information to attach
system journal snippet for incus:
Jan 11 10:24:53 revo dnsmasq-dhcp[188435]: read /var/lib/incus/networks/incusbr0/dnsmasq.hosts/ghost-sandbox_ghost-db-sandbox.eth0
Jan 11 10:24:53 revo dnsmasq-dhcp[188435]: read /var/lib/incus/networks/incusbr0/dnsmasq.hosts/ghost-sandbox_ghost-nodejs-sandbox.eth0
Jan 11 10:24:53 revo dnsmasq-dhcp[188435]: read /var/lib/incus/networks/incusbr0/dnsmasq.hosts/mailtrain-v1.eth0
Jan 11 10:24:53 revo dnsmasq-dhcp[188435]: read /var/lib/incus/networks/incusbr0/dnsmasq.hosts/n8n.eth0
Jan 11 10:24:53 revo dnsmasq-dhcp[188435]: read /var/lib/incus/networks/incusbr0/dnsmasq.hosts/vvveb-sandbox_vvveb-db-sandbox.eth0
Jan 11 10:24:53 revo dnsmasq-dhcp[188435]: read /var/lib/incus/networks/incusbr0/dnsmasq.hosts/vvveb-sandbox_vvveb-nodejs-tmp.eth0
Jan 11 10:24:53 revo dnsmasq-dhcp[188435]: read /var/lib/incus/networks/incusbr0/dnsmasq.hosts/vvveb-sandbox_vvveb-php-sandbox.eth0
Jan 11 10:24:53 revo dnsmasq-dhcp[188435]: read /var/lib/incus/networks/incusbr0/dnsmasq.hosts/wordpress-sandbox_wp-db-sandbox.eth0
Jan 11 10:24:53 revo dnsmasq-dhcp[188435]: read /var/lib/incus/networks/incusbr0/dnsmasq.hosts/wordpress-sandbox_wp-php-sandbox.eth0
Jan 11 10:25:48 revo dnsmasq-dhcp[188435]: Ignoring domain ghost-sandbox for DHCP host name ghost-db-sandbox
Jan 11 10:25:48 revo dnsmasq-dhcp[188435]: Ignoring domain ghost-sandbox for DHCP host name ghost-nodejs-sandbox
Jan 11 10:25:50 revo dnsmasq-dhcp[188435]: Ignoring domain wordpress-sandbox for DHCP host name wp-db-sandbox
Jan 11 10:25:50 revo dnsmasq-dhcp[188435]: Ignoring domain wordpress-sandbox for DHCP host name wp-php-sandbox
Jan 11 10:25:53 revo dnsmasq-dhcp[188435]: Ignoring domain vvveb-sandbox for DHCP host name vvveb-db-sandbox
Jan 11 10:25:54 revo dnsmasq-dhcp[188435]: Ignoring domain vvveb-sandbox for DHCP host name vvveb-php-sandbox
Jan 11 10:25:54 revo dnsmasq-dhcp[188435]: Ignoring domain vvveb-sandbox for DHCP host name vvveb-nodejs-tmp
The text was updated successfully, but these errors were encountered:
I believe when we first introduced projects our intent was to use NAME.PROJECT.DOMAIN when not in the project that owns the network. But this never really worked and we actually ended up introducing a check that when using a shared network between two projects, instance names must be unique, so it would make sense to always generate NAME.DOMAIN now and not try to include the project name in there.
Required information
Issue description
I'm seeing the same issue as discussed over on this forum post by @candlerb
In short, incus is writing the project name into the domain field when creating the corresponding dnsmasq host file for each container at
/var/lib/incus/networks/incusbr0/dnsmasq.hosts/<project>_<container>.<network interface>
Instead I would expect it to use the value of
dns.domain
for the bridge network whether configured explicitly or left to default setting (incus
).Per @candlerb, in practice this doesn't seem to affect actual operation, just generates the warning messages. However the behaviour does appear to be incorrect.
Steps to reproduce
/var/lib/incus/networks/incusbr0/dnsmasq.hosts/<project>_<container>.<network interface>
and note the domain written in the fileInformation to attach
system journal snippet for incus:
The text was updated successfully, but these errors were encountered: