path: root/doc/forum/Using_ip_address_in_a_container
AgeCommit message (Collapse)Author
2017-10-25Make addInfo accumulate Info in order properties appear, not reverse orderJoey Hess
This fixes a bug involving reverting Systemd.resolvConfed or Systemd.linkJournal. addInfo was prepending to the list for efficiency. But, that was in conflict with mappend of two Info, which appended the second to the first. In the case where Systemd.resolvConfed was added reverted, to override the one added by default, that led to a list of info that had first the reversion and then the default, so the default won. Which was wrong. So, make addInfo accumulate in the same order mappend combines things, even though it's a little less efficient. The efficiency probably does not matter; there is not typically a whole lot of info. There's some risk this change has unexpected consequences, if something relied on the old addInfo order without using fromInfo to access to info. But if so, that something would have been broken before when two Info properties were combined. With this change, it would just be broken the other way around. This commit was sponsored by Jochen Bartl on Patreon.
2017-10-05Added a comment: Problem with resolvConfedNicolas.Schodet
2017-10-05Added a comment: ipv4/ipv6Nicolas.Schodet
2017-10-05Added a comment: systemd-nspawn with its own network in the containerNicolas.Schodet
2017-10-04avoid propagating non-alias DNS info from container to hostJoey Hess
* When the ipv4 and ipv6 properties are used with a container, avoid propagating the address out to the host. * DnsInfo has been replaced with DnsInfoPropagated and DnsInfoUnpropagated. (API change) * Code that used fromDnsInfo . fromInfo changes to use getDnsInfo. * addDNS takes an additional Bool parameter to control whether the DNS info should propagate out of containers. (API change) This commit was sponsored by Trenton Cronholm on Patreon.