43
Modernizing my cluster
(lemmy.ca)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 01 Dec 2024
43 points (100.0% liked)
Selfhosted
40719 readers
368 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 2 years ago
MODERATORS
I’ve always had issues with docker, especially when running it on a proxmox vm. I get weird network issues where when docker runs, the whole vm is cut off from network access (but my docker containers have internet). I also have problems with updates. Maybe it’s the whole virtual-ception of it all, a vm running docker running an application.
So far I’ve been getting by with running containers for every service (or VMs when I needed a gui since command line for certain things is tough.
That sounds like your local network IP’s are conflicting with the default docker IP addresses.
What is your routers subnet?
Should be 192.168.2.0/24
Check what your docker subnets are, but that shouldn’t conflict.