containers: enable netavark port publishing
Enable netavark bridge networking in the trimmed Podman recipe so container images support publish-port arguments such as -p 80:8080 and restore iptables dependency. It's needed to install iptables-modules because it is not populated due to NO_RECOMMENDATIONS. Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
This commit is contained in:
parent
a5f42a53af
commit
2d261dd473
|
|
@ -6,18 +6,16 @@ require recipes-containers/podman/podman_git.bb
|
|||
|
||||
DESCRIPTION = "Trimmed Podman runtime for dey-image-container-manager"
|
||||
|
||||
# No CNI implies no isolated or custom network support, no NAT and no forwarding.
|
||||
# Host networking still works, and Podman uses netavark/aardvark-dns in this setup.
|
||||
VIRTUAL-RUNTIME_container_networking = ""
|
||||
PODMAN_NETWORK_BACKEND = "netavark"
|
||||
# Enable Podman bridge networking with netavark
|
||||
VIRTUAL-RUNTIME_container_networking = "netavark"
|
||||
|
||||
RDEPENDS:${PN}:append = " \
|
||||
netavark \
|
||||
aardvark-dns \
|
||||
iptables-modules \
|
||||
"
|
||||
|
||||
RDEPENDS:${PN}:remove = " \
|
||||
iptables \
|
||||
libdevmapper \
|
||||
"
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue