Hey everyone! I'm curious if there's a way to assign an external IP address to a network in Docker that differs from the host IP. For example, I have two containers named 'foo' and 'bar' running in a network (let's call it Network A) with ports 80 and 443. I'd like to assign a specific IP address so I can access them like this: :80 for foo and :443 for bar. I know it's possible to just give the IPs directly to the containers, but I prefer managing them as logical units on the network. Any suggestions? Thanks!
5 Answers
Just to give you some other options: you could create a MacVLAN network which allows your containers to be part of the same IP subnet as your host. Then you could access them directly through that IP. Or, use streaming to tunnel the requests if it fits your needs!
It's important to clarify what you're really after. Rather than trying to find a workaround for assigning IPs directly, maybe it’s better to express the requirements clearly, and then we can figure out the best solution together!
It sounds like you're trying to achieve a clean way to access your services. Technically, you can't assign a single external IP to a Docker network directly. However, you can group your services using a reverse proxy. That way, you could access them through a common domain name, making it much easier to route traffic without worrying about individual IPs. It also keeps things manageable without multiple VMs or complex setups.
If you want to go beyond basic port mapping, using a reverse proxy would be the way to go. You can run something like NGINX as a third container that has its own IP. It can handle routing requests to your other containers based on the domain or path, making everything much cleaner.
You might want to consider the default behavior of Docker networks. By default, when you run containers, they get IPs on Docker's bridge network. To expose them externally, you’d typically set up port forwarding from the Docker host to the respective containers. So, you would access them via the same IP but different ports like 8080 for foo and 8081 for bar. Is that similar to what you were looking for?
Absolutely! A reverse proxy can simplify everything. Just set the registrations for each service under subdomains, and you’ll have the benefits without the hassle of visualizing multiple IPs. Your explanation is spot on!