> Source: [sk168365](https://support.checkpoint.com/results/sk/sk168365)

# sk168365 - Configure Docker Engine to a different subnet

| Property | Value |
|----------|-------|
| Solution ID | sk168365 |
| Date Created | 2020-08-03 |
| Last Modified | 2021-03-01 |
| Technical Level | Advanced |
| Products | Security Management Server |
| Versions | R81 (EOS) |
| OS | Gaia |

## Symptoms

- * The Docker Engine default bridge network is conflicting with the internal network hosts access.
* Resources in the IP subnet 172.17.0.1/16 are not responding

## Cause

R81:  
On Management/Standalone system, *docker0* interface is automatically enabled after the First Time Wizard.  

The enabled docker interface sets itself to a reserved IP subnet `172.17.0.1/16`  
If it happens to be the same IP range as the internal network's resources then the respective requests are sent to the docker interface with no responses returned to the actual client.

<br />

<br />

\*\* in R80.40 docker is not enabled by default , if enabled manually you can follow this sk to resolve network issue

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content