With Podman's former network backend, it was possible to configure a container network that mapped to my home network. Thus, containers were first-class and I could reach them from any LAN client. With the new one (netavark), it *seems* to be impossible. Does anyone know if it can be done?

@zhenech yeah the previous setup I used was a bridge. I followed this guide at the time (not the macvlan bit, the bit after). https://blog.carroarmato0.be/2020/05/08/exposing-podman-container-on-the-network/ with trixie’s podman (using netavark), it explicitly detects and rejects defining a bridge network that overlaps a CIDR the host already has. Perhaps there’s a flag to ignore that warning I haven’t found yet.

@zhenech my own write up is https://jmtd.net/log/podman_network/ , but it isn’t as useful as the other blog post by someone else

@zhenech the beige already exists, yes: i didn’t try that exact invocation (i think a superset). Going to fiddle a bit more this morning :)

@zhenech alas the second cmd there also throws the "already used on host or by another config" error. I'm wondering if the old CNI config lying around could be the problem…

@zhenech partial solution: I've defined the network with a wrong/temporary IP range, and then edited the JSON file afterwards.

@zhenech here's the code that actually throws the error. https://github.com/containers/container-libs/blob/a3b0f19c3ea12cb02f0b11788489c52d4fb02e96/common/libnetwork/internal/util/validate.go#L35 (sorry, I'm using you as a rubber duck here ;))