How to give containers (app) an IP address?

Yes, but I'll note the /ip/reverse-proxy can hide the port for you, since you just use a different DNS name that has the references the internet port/container IP to forward. Food for thought. Now it's FQDN name is often less friendly, but a DNS suffix in DHCP might solve it so it's just hostname resolved)

That only work with HTTP/S... so does not work all the time, in all case. And do hear on you the "just know the IP" part here, as too do get confused on port stuff is on sometimes too - why I'm not say it's "bad" to bridge a VETH, but it is a choice that folks should consider since it's not some clear-cut "always bridge VETH". You have needs, understand what you're doing, etc. is a different story than what the "generic advice" should be :wink:

The way I do it, the container has the IP of the VETH and you connect to it directly via that IP. I guess I don't get what you are trying to do . . .

Add another container, add another VETH with it's own unique IP.

Unless you arentrying to grant external access (which I may have overlooked, missed, or outright forgotten . . .