-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[openvpn] ERROR: could not find an available, non-overlapping IPv4 address pool among the defaults to assign to the network #418
Comments
From what I've read, and testing with vpn and docker, this seems to be the issue
|
Same experience with Debian Stretch |
This is has been a while around, even in ubuntu 16.04 I was experiencing it. |
Docker tried to automatically assign a /24 to a network and it could not find an available one. You need to manually select a subnet as part of your network options for the service. You can do this either as an option on network create or tell docker about the default addresss pools, which is a daemon level option. moby/moby#36396 This is not a bug. |
Let me close this per the discussion above, but feel free to comment after I closed |
My recommended work-around is to create a network utilizing an unused private address range on your machine:
Configure docker compose to use this as an external network. Either adding the following to the compose file or the override file as shown:
|
@myspotontheweb 's answer solved my problem, while I'm using ExpressVPN, a commercially hosted VPN vendor, seems that tunnel occupied the default 172 subnet of docker, thus any container got better to specify a dedicated subnet |
Docker unable to access from VPN
docker network prune Using Docker Compose + OpenVPNSet the content below inside your docker-compose file: networks:
default:
driver: bridge
ipam:
config:
- subnet: 10.10.1.0/24 |
@cpuguy83 This is a bug. If route I can not assign network manually because when I run same compose file with different project name |
In the latest docker version, I no longer get this error. Instead when i'm connected to VPN, The previous error |
@cipher-code: your local IP address 127.0.0.1 is overlapping with default route 0.0.0.0/0. Is is OK to prohibit assign 127.0.0.1 to your host? (eg. Docker should not restrict usage of 10.0.0.1/24 locally if your system has route to 10.0.0.0/8 network) |
Description of the issue
When running
docker-compose up
while connected to an OpenVPN proxy, I get the following error:Several other people have experienced this issue, and discussed it on StackOverflow
Context information (for bug reports)
Steps to reproduce the issue
docker-compose up
in a projectObserved result
Expected result
Docker compose should be able to find an IPv4 address pool
Additional information
OS: Kubuntu 18.04
The text was updated successfully, but these errors were encountered: