raldone01

I have two machines running docker. A (powerful) and B (tiny vps).

All my services are hosted at home on machine A. All dns records point to A. I want to point them to B and implement split horizon dns in my local network to still directly access A. Ideally A is no longer reachable from outside without going over B.

How can I forward requests on machine B to A over a tunnel like wireguard without loosing the source ip addresses?

I tried to get this working by creating two wireguard containers. I think I only need iptable rules on the WG container A but I am not sure. I am a bit confused about the iptable rules needed to get wireguard to properly forward the request through the tunnel.

What are your solutions for such a setup? Is there a better way to do this? I would also be glad for some keywords/existing solutions.

Additional info:

• Ideally I would like to not leave docker.
• Split horizon dns is no problem.
• I have a static ipv6 and ipv4 on both machines.
• I also have spare ipv6 subnets that I can use for intermediate routing.
• I would like to avoid cloudflare.

A Containerized Night Out: Docker, Podman, and LXC Walk into a Bar

🌆 Setting: The Busy Byte Bar, a local hangout spot for tech processes, daemons, and containerization tools.

🍺 Docker: walks in and takes a seat at the bar Bartender, give me something light and easy-to-use—just like my platform.

🍸 Bartender: Sure thing, Docker. One "Microservice Mojito" coming up.

🥃 Podman: strides in, surveying the scene Ah, Docker, there you are. I heard you've been spinning up a lot of containers today.

🍺 Docker: Ah, Podman, the one who claims to be just like me but rootless. What'll it be?

🥃 Podman: I'll have what he's having but make it daemonless.

🍹 LXC: joins the party, looking slightly overworked You two and your high-level functionalities! I've been busy setting up entire systems, right down to the init processes.

🍺 Docker: Oh, look who decided to join us. Mr. Low-Level himself!

🥃 Podman: You may call it low-level, but I call it flexibility, my friends.

🍸 Bartender: So, LXC, what can I get you?

🍹 LXC: Give me the strongest thing you've got. I need all the CPU shares I can get.

🍺 Docker: sips his mojito So, Podman, still trying to "replace" me?

🥃 Podman: Replace is such a strong word. I prefer to think of it as giving users more options, that's all. winks

🍹 LXC: laughs While you two bicker, I've got entire Linux distributions depending on me. No time for small talk.

🍺 Docker: Ah, but that's the beauty of abstraction, my dear LXC. We get to focus on the fun parts.

🥃 Podman: Plus, I can run Docker containers now, so really, we're like siblings. Siblings where one doesn't need superuser permissions all the time.

🍹 LXC: downs his strong drink Well, enjoy your easy lives. Some of us have more... weight to carry.

🍸 Bartender: Last call, folks! Anyone need a quick save and exit?

🍺 Docker: I'm good. Just gonna commit this state.

🥃 Podman: I'll podman checkpoint this moment; it's been fun.

🍹 LXC: Save and snapshot for me. Who knows what tomorrow's workloads will be?

And so, Docker, Podman, and LXC closed their tabs, leaving the Busy Byte Bar to its quiet hum of background processes. They may have different architectures, capabilities, and constraints, but at the end of the day, they all exist to make life easier in the ever-expanding universe of software development.

And they all knew they’d be back at it, spinning up containers, after a well-deserved system reboot.

🌙 The End.

I was bored a bit after working with podman, docker and lxc. So I asked chat gpt to generate a fun story about these technologies. I think its really funny and way better than these things usually turn out. I did a quick search to see if I can find something similar but I couldn't find anything. I really suspect it being repurposed from somewhere.

I hope you can enjoy it despite being ai generated.