diskimage-builder/releasenotes/notes/containerfile-host-networking-0691f3be5c6b11b6.yaml

---
upgrade:
  - |
    The default networking in the ``containerfile`` element is
    switched to ``host`` as we have found that more reliable in
    generating the initial chroot images.
tox jobs: pin to correct nodesets; use host networking for containerfile These must have broken when we switched the base nodes to Jammy. Update to use compatible versions of distros. We need to squish another gate-breaking change in here to update the containerfile "podman build" calls to use "--network host". We added this with Ia885237406bf4c7b9d49b349f374558ae746401f and the only external user I can find is kayobe, which is setting this anyway. I honestly haven't 100% root-caused what changed to require this; the last time our containerfile jobs ran and worked has unfortunately been purged so I can't compare versions to try and pinpoint something; i.e. this may be a podman bug or feature. At first I thought it related to the networking plugin package from the Depends-On (which is still useful for the right packages) but that didn't help get the bridge networking working. Depends-On: https://review.opendev.org/c/zuul/nodepool/+/867590 Change-Id: I23f091654cb212e8bdd908664b262de9bfe98cef 2022-12-13 23:57:18 +00:00			`---`
			`upgrade:`
			`- \|`
			The default networking in the ``containerfile`` element is
			switched to ``host`` as we have found that more reliable in
			`generating the initial chroot images.`