Recent searches
Search options
I need to take a step back and reassess my network setup. Here’s what I have:
• Proxmox VE running on a mini PC, directly connected to my router (no VLANs).
• The Proxmox host has a single virtual adapter with a static private IP, which is also reserved on the router.
• A Cloudflared LXC (running in Proxmox) with its own reserved private IP on the same subnet as the Proxmox host.
• A VM on the same subnet running Docker, where the containers are on a user-defined bridge network, but this bridge network is on a different subnet than the host.
My goal:
I want the Cloudflared LXC to properly route public hostname(s) to the appropriate Docker containers (which provide public services) on the VM.
The challenge:
Since the Docker containers are on a different subnet than the VM itself, how should I structure my networking so that:
1. Cloudflared can route requests correctly to the Docker services.
2. The setup remains clean and maintainable.
What’s the best approach to configure this? Should I adjust Proxmox networking, use additional routes, or take a different approach?
@suzannealdrich Can you pass a full network adapter to a Docker container? I use systemd containers and this is how I have containers in VMs sitting on a VPN routed subnet.
So from PVE I have two network adapters assigned to the VM - one configured to connect to the routed network and one on a management network. Inside the VM, the management network adapter is used as default ethernet, while the other is passed to the container.
@suzannealdrich My goal with that setup is to minimise the amount of network details configured in the container setup & VM. All the VM knows is that one atapter is for itself and the other for the container.
The implementation details are handled on PVE and the router.