[general_failure]

Is your intention to expose the ports of a docker container? If you want to do this search for "expose" ports. The docker run option is -p and -P for this.

Or to create a subnet with custom IP for the docker daemon's bridge network? Use -b option to docker daemon.

https://docs.docker.com/engine/userguide/networking/ is a good place to start. If you have a specific question, feel free to ask and I can try to answer.

[dijit]

no, that's not my intention, my intention is to not have to deal with iptables mangling packets and adding netfilter tags to everything.

not to mention port collisions with things that must run on predefined ports (think SMTP or pesky applications that keep redirecting you back to port 80)

I'm looking to expose 'an IP' similar to a bridged/open network in KVM.

[jdoliner]

Would doing --network=host do this? It makes the container use the hosts networking stack so there's no funny business.

[takee]

Yes it would help here but would also expose new security loopholes.