Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse

Cloudron Forum

Apps | Demo | Docs | Install

Docker IP range

Scheduled Pinned Locked Moved Solved Support
17 Posts 3 Posters 541 Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • subvenS Offline
    subvenS Offline
    subven
    replied to savity on last edited by
    #7

    @savity said in Docker IP range:

    @subven Trust me when i tell you..... i adressed this 1000 times 🙂

    Yeah gotya ^^ As system administrator I had to deal with users not beeing able to use VPN and stuff because of stupid networking design all the time. Companies grow and not all are able to fix their sins.

    1 Reply Last reply
    1
  • S Offline
    S Offline
    savity
    wrote on last edited by
    #8

    @girish Would need help here i solved this issues by making configs directly on another Linux Machine by

    /etc/docker/daemon.json
    {
    "default-address-pools":
    [
    {"base":"10.10.0.0/16","size":24}
    ]
    }

    subvenS 1 Reply Last reply
    0
  • subvenS Offline
    subvenS Offline
    subven
    replied to savity on last edited by
    #9

    @savity said in Docker IP range:

    @girish Would need help here i solved this issues by making configs directly on another Linux Machine by

    /etc/docker/daemon.json
    {
    "default-address-pools":
    [
    {"base":"10.10.0.0/16","size":24}
    ]
    }

    Don't think this will work because from what I understand is that you have to recreate the containers. Take a look at the post I linked above.

    S 1 Reply Last reply
    0
  • S Offline
    S Offline
    savity
    replied to subven on last edited by
    #10

    @subven I did and tried also with 10.10 network no chance still no route

    1 Reply Last reply
    0
  • girishG Offline
    girishG Offline
    girish Staff
    replied to savity on last edited by
    #11

    @savity said in Docker IP range:

    is there a supported way to reconfigure the Docker IP range? So i can use my smtprelay witch is in the network 172.17

    Cloudron uses the 172.18.x.x network for docker containers. So, I am guessing the problem is something else? The ping screenshot you posted in your initial post, is that from inside a container or is that from the host?

    S 2 Replies Last reply
    0
  • S Offline
    S Offline
    savity
    replied to girish on last edited by
    #12

    @girish It is from the Host yes
    I wanna Ping 172.17.x.x and this is the nic adapter IP
    172.16.x.x/16

    1 Reply Last reply
    0
  • S Offline
    S Offline
    savity
    replied to girish on last edited by savity
    #13

    @girish Then this must be the issue?
    3abc2172-77fd-4e25-9bfe-acfe7bb2a2bb-image.png I did not creat those bridges and it is a standard cloudron installation

    girishG 1 Reply Last reply
    0
  • girishG Offline
    girishG Offline
    girish Staff
    replied to savity on last edited by
    #14

    @savity Ah indeed, it seems that docker uses 172.17 by default. Let me check how to workaround this.

    1 Reply Last reply
    1
  • girishG Offline
    girishG Offline
    girish Staff
    wrote on last edited by
    #15

    @savity OK, I might have a solution for this. Still testing. Hopefully, should have a workaround tomorrow.

    S 1 Reply Last reply
    1
  • S Offline
    S Offline
    savity
    replied to girish on last edited by
    #16

    @girish Any news here girish.

    girishG 1 Reply Last reply
    0
  • girishG Offline
    girishG Offline
    girish Staff
    replied to savity on last edited by
    #17

    @savity So, create a file named /etc/systemd/system/docker.service.d/custom.conf:

    [Service]
    ExecStart=
    ExecStart=/usr/bin/dockerd -H fd:// --log-driver=journald --exec-opt native.cgroupdriver=cgroupfs --storage-driver=overlay2 --experimental --ip6tables --bip 192.168.1.1/24 
    

    Then,

    # systemctl daemon-reload
    # systemctl restart box
    

    If you do, docker network inspect bridge, you will see the IP has changed.

    1 Reply Last reply
    2
  • girishG girish marked this topic as a question on
  • girishG girish has marked this topic as solved on

  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Login

  • Don't have an account? Register

  • Login or register to search.