I encountered a problem when trying to set up a docker environment using the full-openim-server-chat-web.yml file with Docker Compose. When I ran the command docker-compose -f example/full-openim-server-chat-web.yml up -d
What did you expect to happen?
I received the following error message:
Creating network "example_openim-server" with driver "bridge"
ERROR: Pool overlaps with other one on this address space
How can we reproduce it (as minimally and precisely as possible)?
This error usually occurs when there's a conflict in the network address space being used by Docker. It seems like the network example_openim-server is trying to use an address space that's already in use by another network.
I'm considering using the commands docker stop $(docker ps -qa) and docker rm $(docker ps -qa), or docker-compose down to possibly resolve this issue. However, I am not sure if these commands will help in clearing the existing network that's causing the overlap.
Could you please confirm if using the above commands will help in resolving the network conflict? Also, I found that the command docker network prune -f might be a solution to remove unused networks. Would this be an appropriate approach to resolve the network overlap issue?
Anything else we need to know?
This issue report provides a clear description of the problem, context on why it occurs, and asks for confirmation on potential solutions, making it a comprehensive and well-structured request for help.
version
```console
$ {name} version
# paste output here
```
Cloud provider
OS version
```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here
# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```
What happened?
I encountered a problem when trying to set up a docker environment using the
full-openim-server-chat-web.ymlfile with Docker Compose. When I ran the commanddocker-compose -f example/full-openim-server-chat-web.yml up -dWhat did you expect to happen?
I received the following error message:
How can we reproduce it (as minimally and precisely as possible)?
This error usually occurs when there's a conflict in the network address space being used by Docker. It seems like the network
example_openim-serveris trying to use an address space that's already in use by another network.I'm considering using the commands
docker stop $(docker ps -qa)anddocker rm $(docker ps -qa), ordocker-compose downto possibly resolve this issue. However, I am not sure if these commands will help in clearing the existing network that's causing the overlap.Could you please confirm if using the above commands will help in resolving the network conflict? Also, I found that the command
docker network prune -fmight be a solution to remove unused networks. Would this be an appropriate approach to resolve the network overlap issue?Anything else we need to know?
This issue report provides a clear description of the problem, context on why it occurs, and asks for confirmation on potential solutions, making it a comprehensive and well-structured request for help.
version
Cloud provider
OS version
Install tools