Selfhosted

40173 readers

652 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

[email protected]

Maximum number of docker networks (lemm.ee)

submitted 7 months ago by [email protected] to c/[email protected]

14 comments fedilink hide all child comments

Hey guys, I was happily running 44 docker containers for a while on Debian host. Today I tried to add a new service (uptime-kuma) using portainer stacks, but I got this error:

Error response from daemon: could not find an available, non-overlapping IPv4 address pool among the defaults to assign to the network

Quick google led me to this link where I found possible problem with max number of docker networks. I did docker network prune, it removed 5 networks that were not in use and viola, uptime-kuma is working now!

Am I reaching the limit? What to do if I need 10 more services on the same host? I bet I saw some people in this community running many more services

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

[–] [email protected] 4 points 7 months ago* (last edited 7 months ago)

Only if there was IPv6: https://docs.docker.com/config/daemon/ipv6/

Just run all your containers with IPv6 randomly generated prefixes and this won't ever be a problem, you'll also get more IP spacing than you'll ever require. Then use your reverse proxy to convert between the "public" IPv4 space and the internal docker IPv6 networks.

Another option is to reduce the size of your IPv4 pools like this guy described.