Suggest an edit

Improve this article

Refine the answer for “What types of networks exist in Docker by default?”. Your changes go to moderation before they’re published.

Approval required

Content

What you’re changing

Title (EN)

Short answer (EN)

Shown above the full answer for quick recall.

Answer (EN)

By default, Docker creates three types of networks that are available right after installation:

---

### **1.** `bridge` **(the default for containers)**

- This is the standard internal network on a single host.
- Containers inside `bridge` can communicate with each other.
- From outside, the container is accessible only through published ports.
- Used by default when a container is started without specifying a network.

Example:

```bash
docker run -d nginx
```

The container ends up in `bridge`.

---

### **2.** `host`

- The container uses the host's network stack directly.
- The container **has no IP of its own**; it essentially "lives" on the host's network.
- Useful for tasks that need maximum network speed or direct access to the interface.

Example:

```bash
docker run --network host nginx
```

---

### **3.** `none`

- The container **has no network at all**.
- No internet access, no communication with other containers.
- Suitable for fully isolated tasks.

Example:

```bash
docker run --network none nginx
```

---

### **Summary table**

| Network type | Visibility between containers | Internet access | Feature |
|---|---|---|---|
| `bridge` | Yes, within the network | Yes | Used by default |
| `host` | No isolation from the host | Yes | Maximum speed, no separate IP |
| `none` | No | No | Full isolation |

---

**Summary:** by default, Docker provides three networks: `bridge`, `host`, `none`, and each of them is responsible for its own level of isolation and interaction.

Markdown · drag & drop images · ⌘B / ⌘I shortcuts250 words

For the reviewer

Note to the moderator (optional)

Visible only to the moderator. Helps review go faster.