Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
Woahai321 authored Jan 4, 2025
1 parent 303e44a commit c6a9170
Showing 1 changed file with 43 additions and 0 deletions.
43 changes: 43 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -245,6 +245,49 @@ This will determine your Overseerr Webhook URL i.e. HTTP://DOCKER-CONTAINER-IP:8

---



## Docker Network Configuration

### Steps to Align Containers on the Same Network

1. **Check Container Networks:**
Run the following command to list the containers and their associated networks:
```bash
docker ps --format '{{ .ID }} {{ .Names }} {{ json .Networks }}'
```
This will display the container IDs, names, and the networks they are connected to.

2. **Disconnect the Container from Its Current Network:**
Use the following command to disconnect a container from its current network:
```bash
docker network disconnect NETWORK_NAME CONTAINER_ID
```
Replace `NETWORK_NAME` with the name of the network the container is currently on, and `CONTAINER_ID` with the ID of the container.

3. **Connect the Container to the Desired Network:**
Use the following command to connect the container to the target network:
```bash
docker network connect TARGET_NETWORK_NAME CONTAINER_ID
```
Replace `TARGET_NETWORK_NAME` with the name of the network you want the container to join (e.g., `overseerr`), and `CONTAINER_ID` with the ID of the container.

4. **Verify the Changes:**
Run the `docker ps --format '{{ .ID }} {{ .Names }} {{ json .Networks }}'` command again to confirm that both containers are now on the same network.

### Example
To move a container with ID `abc123` from its current network to the `overseerr` network:
```bash
docker network disconnect current_network abc123
docker network connect overseerr abc123
```

### Notes
- Ensure both containers are connected to the same network after completing the steps.
- If the containers are still not communicating, double-check the network configuration and ensure no firewall rules are blocking the connection.

---

That's it! Your **SeerrBridge** container should now be up and running. 🚀
---
Expand Down

0 comments on commit c6a9170

Please sign in to comment.