@jmtd you mean like having a bridge and having containers as "hosts"?
I run some stuff as "network=host", which works fine but is not the same as a bridge.

@zhenech @jmtd it does sound like network=host is the answer here

@creepy_owlet @zhenech @jmtd Wouldn't that make them all use the host's ip rather than having their own?

@jmtd Did you try creating the bridge manually and then doing something like
podman network create --opt mode=unmanaged --interface-name=br0 --subnet=192.168.124.0/24 podbr0

@jmtd mode=unmanaged was the kicker here:

[root@centos9-stream ~]# podman network create --interface-name=br0 --subnet=192.168.124.0/24 podbr0
Error: subnet 192.168.124.0/24 is already used on the host or by another config
[root@centos9-stream ~]# podman network create --opt mode=unmanaged --interface-name=br0 --subnet=192.168.124.0/24 podbr0
podbr0

But that bridge has nothing attached to it, so I can't test right now.

@mattb @zhenech @jmtd it would, yes. I didn't realize it was a requirement.