this post was submitted on 26 Mar 2024
22 points (92.3% liked)

Selfhosted

40313 readers
185 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
22
Maximum number of docker networks (lemm.ee)
submitted 8 months ago by rambos@lemm.ee to c/selfhosted@lemmy.world
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
[–] TheButtonJustSpins@infosec.pub 18 points 8 months ago* (last edited 8 months ago) (5 children)

Docker network pools are huge by default. I had to change this as well.

This article covers the issue and the solution in detail:
https://straz.to/2021-09-08-docker-address-pools/

If you just want the solution, skip to the section titled How to configure docker to allow >500 bridge networks. I think you'll need to remake all your networks after making the change, if I remember correctly.

Here's my config now:

$ sudo cat /etc/docker/daemon.json
{
  "default-address-pools": [
    { "base":"172.16.0.0/12", "size":24 },
    { "base":"172.17.0.0/12", "size":24 },
    { "base":"172.18.0.0/12", "size":24 },
    { "base":"172.19.0.0/12", "size":24 },
    { "base":"172.20.0.0/12", "size":24 },
    { "base":"172.21.0.0/12", "size":24 },
    { "base":"172.22.0.0/12", "size":24 },
    { "base":"172.23.0.0/12", "size":24 },
    { "base":"172.24.0.0/12", "size":24 },
    { "base":"172.25.0.0/12", "size":24 },
    { "base":"172.26.0.0/12", "size":24 },
    { "base":"172.27.0.0/12", "size":24 },
    { "base":"172.28.0.0/12", "size":24 },
    { "base":"172.29.0.0/12", "size":24 },
    { "base":"172.30.0.0/12", "size":24 },
    { "base":"172.31.0.0/12", "size":24 }
  ],
  "log-opts": {
    "max-size": "1g"
  }
}
[–] Markaos@lemmy.one 4 points 8 months ago (3 children)

I'm pretty sure all of those entries are in the same /12 network - 172.16.0.0/12. Apparently there's nothing wrong with it, but I think you can significantly simplify that config by just removing all the extra ones

load more comments (2 replies)
load more comments (3 replies)