Hmm interesting ...
/usr/sbin/ebtables is managed by update alternatives.
But iptables continues to surprise.
In an sbuild build env of Eoan I get:
# which ebtables iptables ip6tables
/usr/sbin/ebtables
/sbin/iptables
/sbin/ip6tables
While in an Eoan container I have:
# which ebtables iptables ip6tables
/usr/sbin/ebtables
/usr/sbin/iptables
/usr/sbin/ip6tables
Let me recycle the container as it might have some old crap.
No it stays the same...
Both are on 2.0.10.4+snapshot20181205-1ubuntu1 / 1.6.1-2ubuntu3.
To make that three a Eoan VM as of today has the same as the container.
All of them (sbuild+lxd+vm) have the non usr path in the package itself.
dpkg -L iptables | grep 'bin\/iptables$'
/sbin/iptables
And the /usr/sbin path that exists in the container
Hmm, something in the container and the VM brings that /usr/sbin mapping to
work which fails in the build environment, maybe because it is "just" a chroot?
/var/lib/dpkg/info/iptables.* has no further magic maintscripts that
would explain.
For now in libvirt lets set the real paths as carried by iptables packages.
This will keep us on the safe side.
But that also means we are back at my initial assumption that on an
iptables 1.8.1 merge one might want to remove that (unless
/sbin/iptables is kept as compat, then I can clear it next cycle).
** Changed in: libvirt (Ubuntu)
Status: Invalid => Triaged
** Changed in: iptables (Ubuntu)
Status: Fix Released => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832297
Title:
usrmerge changes path of iptables - please update libvirt on a merge
of 1.8.1-x
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1832297/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
