12:05 p.m.
On 01/03/2021 14:19, Brent Baude wrote:
Should there be substantial differences between versions?
The problem which original message describes I see with
podman-2.2.1-7.module_el8.3.0+699+d61d9c41.x86_64
-> $ podman run -it --rm --pod=cloud-${HOSTNAME%%.*} --name
alpine docker.io/library/alpine
/ # ip addr ls dev eth0
2: eth0@if3: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu
1450 qdisc noqueue state UP
link/ether e2:64:21:37:bb:e5 brd ff:ff:ff:ff:ff:ff
inet 10.0.1.116/24 brd 10.0.1.255 scope global eth0
/ # ping 10.0.1.8
PING 10.0.1.8 (10.0.1.8): 56 data bytes
which hangs with no reply, whereas
podman-3.0.0-0.33rc2.module_el8.4.0+673+eabfc99d.x86_64
(surely other components as underlying OS too):
-> $ podman run -it --rm --pod=cloud-${HOSTNAME%%.*} --name
alpine docker.io/library/alpine
2: eth0@if3: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu
1500 qdisc noqueue state UP
link/ether 3e:d8:0c:9d:ee:f1 brd ff:ff:ff:ff:ff:ff
inet 10.1.1.243/24 brd 10.1.1.255 scope global eth0
/ # ping 10.1.1.224
PING 10.1.1.224 (10.1.1.224): 56 data bytes
64 bytes from 10.1.1.224: seq=0 ttl=64 time=0.239 ms
In both cases targets to ping are some devices on local
subnet which targets are available, reachable by both
hosts(different boxes and OSes to clarify)
Maybe there is something to it.
regards, L.