Selfhosted

40183 readers

634 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

My Docker containers can no longer communicate with the host's local network (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by UberMentch@lemmy.world to c/selfhosted@lemmy.world

7 comments fedilink hide all child comments

I feel like I'm losing my mind. A few days ago, all of my containers running on Docker Desktop on my Windows Server host were working nicely. I had NFS volumes set up on a few of them to reach my synology NAS on my local network, and things were working fine. I've done so much digging and tweaking over the last few days, so I can't be certain where all I've broken this connection further, but I woke up one morning and the containers that all had connections to my NAS via NFS volumes were no longer working. I hadn't restarted my host, I don't know what changed. Containers like NPM that I had set up for my internal DNS would no longer redirect to any IP that wasn't within my docker network (for example, I run Plex NOT in a container on my host PC). I had all of my containers on the default bridge network, and now nothing on this docker network can connect to anything on my local network.

I've tried setting static routes in my router, changed a lot of configurations, dug through tutorials, guides, and posts all weekend, but I couldn't make any progress in figuring things out. I'd really appreciate some help on this one, and can provide more details, logs, compose files, when needed. Just don't want to dump everything at once

you are viewing a single comment's thread
view the rest of the comments

[–] rikudou@lemmings.world 10 points 1 year ago (1 children)

You probably won't like this advice, but switch to Linux. Docker on Windows and MacOS is kind of a hack.

[–] UberMentch@lemmy.world 2 points 1 year ago (3 children)

That's what I've been seeing, but I run enough stuff on Windows that has poor support for Linux that makes it a toss-up. Do you think it's feasible to run Docker on Linux in a Hyper-V container on Windows? I'm really trying to evaluate my options, I've considered Proxmox to separate my Windows and Linux stuff; currently I am running an instance of Ubuntu in Hyper-V for my Linux stuff. Do you think Proxmox is more viable?

[–] thomasloven@lemmy.world 4 points 1 year ago (1 children)

I go the other way. I have linux installed pretty much just to run docker and qemu running windows with iommu passthrough. The performance hit is negligible, and with docker context you can run docker-cli and devcontainers and stuff in the windows vm like native.

[–] UberMentch@lemmy.world 1 points 1 year ago

Hmm, I've never looked into qemu. Do you use a GPU in your environment? It passes through to your Windows VM fine?

[–] chaospatterns@lemmy.world 3 points 1 year ago* (last edited 1 year ago)

If you're running Docker for servers not development, then you can make Hyper-V work. I used to do that before I got a separate Linux server and it worked out.

Just setup a network adapter that gets bridged to your Ethernet adapter, then create a VM that uses that bridged adapter. The Linux VM will appear like its another computer on your LAN and you can use Docker with host Network.

[–] walden@sub.wetshaving.social 3 points 1 year ago (1 children)

If using it solely for Docker, I wouldn't go the Proxmox route. Just install Debian and go from there.

[–] UberMentch@lemmy.world 1 points 1 year ago

On my host PC (Windows Server), I'm already running a VM in Hyper-V that operates behind a VPN for my *arr environment. I'm worried about resources and resource allocation if I add another VM just for docker. Basically I'm looking at 3 environments - Windows Server for my windows stuff, Debian server for my *arr stuff (this all has to be behind a VPN), and a Linux docker environment. It makes sense to me to go the Proxmox route now that I've considered it, don't you think? Not asking because I'm trying to convince you, just interested in others perspectives.