Bug 2115988
Summary: | Recent podman upgrade causes container to fail with error "invalid config provided: extra host entries must be specified on the pod: network cannot be configured when it is shared with a pod" | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Brian Masney <bmasney> |
Component: | podman | Assignee: | Tom Sweeney <tsweeney> |
Status: | CLOSED WORKSFORME | QA Contact: | atomic-bugs <atomic-bugs> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 8.6 | CC: | bbaude, dwalsh, jligon, jnovy, lsm5, mheon, pthomas, umohnani |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-08-08 20:48:02 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Brian Masney
2022-08-05 23:00:00 UTC
I fixed the issue by moving the --add-host argument from the 'pod run' command to the 'podman pod create --share net' command. This was a deliberate change in response to a bug opened upstream (breadcrumb: commit was https://github.com/containers/podman/commit/e4ab8a5bedb48615402231a5aa3a62ca4364c45f); I'm trying to locate the specific bug that this was in response to, but so far without success. The general idea is that the previous behavior did not work as expected (adding hosts to pre-existing containers that you joined the network namespace of had a number of bugs with it), so we have changed things to require hosts to be pre-specified in the pod's config when it is created. This can be closed as far as I am concerned since the various search engines will add this error message and BZ to their indexes. Closing per prior comments |