-
```
# bats test/100-bridge-iptables.bats
✗ iptables - internal network
(in test file test/100-bridge-iptables.bats, line 22)
`assert "$output" == "$before" "make sure tables have not chang…
-
Hi, I have a few standalone containers running under podman, using a `macvlan` network to make them available to an internal LAN network. I'm observing the following:
1: Every time the external rou…
-
Netavark assumes it can `systemd-run --user` aardvark after only checking for system-wide systemd (/var/run/systemd). This may not always be the case (e.g. disabled pam_systemd for some reason).
I …
-
### Issue Description
Creating podman network using driver macvlan with ipv6 enabled and ipam-driver dhcp passes through an ipv4 address, but not an ipv6 address.
### Steps to reproduce the issu…
-
Steps to reproduce:
- Install Alpine Linux 3.20.2
```sh
$ podman run --rm curlimages/curl podman.io # working
$ podman network create test
$ podman run --rm --network test curlimages/curl pod…
-
It seems on default setups with firewalld `DNS` is not functional at all, would it make sense to add `--zone=netavark_zone --add-port=53/udp` ?
Reproducer
* Start with default `firewalld`
```
…
-
## Observed behavior
When setting `dns_bind_port` in `/etc/containers/containers.conf` to anything other than 53, containers in internal networks have no container-to-container name resolution (e.g…
-
## Describe the Bug
We have a RHEL 9.4 server with podman installed as replacement for Docker. Podman installs a docker command to emulate docker using podman. Running puppet give us error for the fa…
-
Right now our dns startup is super flaky causing many flakes in CI that are only solved by using retries. This is bad and often not what users are doing. Sending signals is just not reliable. Netavark…
-
### Issue Description
Podman does not generate events about network.
### Steps to reproduce the issue
1) In one console run : podman events
2) In a another console create a new network : podma…