How Can I Assign IP Addresses to Docker Containers Using an External DHCP Server?

If you're trying to expose multiple services, using a reverse proxy is the way to go. You can manage all your services through one public IP by directing traffic based on URLs. It's actually more secure this way, preventing your backend applications from being directly exposed.

You really don't need to assign IP addresses manually to your containers. By default, Docker manages IPs dynamically within its own network. You can access services running in containers through the host IP address. If you have a special case where a container needs its own public IP (like a DNS server), then MACVLAN can work for that, but be cautious about the overall necessity.

It's surprising to see people forcing IP assignments when Docker provides automatic management. Instead of complicating things, consider using a reverse proxy alongside your own DNS to handle multiple services efficiently without needing separate IPs for each.

You might want to reconsider this approach. It's common for beginners to think of containers like virtual machines, but they're not quite the same. Typically, individual containers don't need their own public IP addresses. You can expose necessary ports from the Docker host instead. Alternatively, look into setting up a reverse proxy for better management. Using MACVLAN to assign individual IPs can complicate things unnecessarily, so it's generally not recommended.