After deploying Dify, Dify's Docker and Harbor services generated three network segments: 172.17.0.0, 172.18.0.0, and 172.19.0.0, which conflict with the company's local network segment 172.

Help Me Build Seeking help
1

:bullseye: What I Need Help With

After deploying Dify on an Ubuntu 22.04.3 system with x86 architecture, the server uses the IP address 191.136.12.2. However, Dify’s Docker and Harbor services have created three subnets in the kernel IP routing table: 172.17.0.0, 172.18.0.0, and 172.19.0.0.

These subnets conflict with the company’s local network, which also uses the 172.x.x.x subnet. The company’s local LAN includes both 191.x.x.x and 172.x.x.x subnets.

As a result, computers on the 172.x.x.x subnet cannot access the server at 191.136.12.2, and it is unclear whether Dify has been successfully deployed.

Could you please advise how to modify the Docker and Harbor services in Dify to change the generated subnets (172.17.0.0, 172.18.0.0, 172.19.0.0)?

Thank you all!

WeChat Image_20251203191555

:clipboard: Project Details

  • Project Type: [Chatbot/RAG/Agent/Workflow/Other]
  • Timeline: [When do you need this done?]
  • Budget: [Your budget range or “flexible”]
  • Scope: [Small task / Full project / Ongoing support]

:wrench: Technical Requirements

  • Dify features needed: [List specific features]
  • Integration requirements: [APIs, databases, external services]
  • Scale expectations: [Number of users, requests, etc.]

:white_check_mark: Ideal Collaborator

[Skills or expertise you’re looking for]

:telephone_receiver: How to Reach Me

  • Preferred contact: [Email/Discord/Telegram]
  • Contact info: [Your contact details]
  • Timezone: [Your timezone]

:paperclip: Additional Context

[Any other relevant information]

2

Docker allows you to customize network segments.

/etc/docker/daemon.json — Create it if it does not exist:

{
“bip”: “172.31.0.1/16”,
“default-address-pools”: [
{
“base”: “172.32.0.0/16”,
“size”: 24
},
{
“base”: “172.33.0.0/16”,
“size”: 24
}
]
}

systemctl daemon-reload
systemctl restart docker

After restarting the Docker service, the addresses will be successfully modified.

3

Sure, thank you for the guidance.

Well, the current Docker network segment 172.17.0.0 has already been modified.

However, I haven’t found configuration files to modify the 172.18.0.0 and 172.19.0.0 segments yet.

Could you please advise how to modify these two?

Thank you.