-
Notifications
You must be signed in to change notification settings - Fork 131
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
docker-compose SUBSPACE_IPV4_POOL= ignored? #158
Comments
I can confirm that this doesn't seem to work. The gateway and DNS server target seems okay though (wireguard server as single dns server). |
I could confirm this in testing with and without docker-compose. The following docker-compose.yml worked fine for me:
|
Upon further investigation, this line in "entrypoint.sh" basically sets the correct "SUBSPACE_IPV4_PREF" whenever "SUBSPACE_IPV4_GW" is left empty. So providing "SUBSPACE_IPV4_GW" basically leads to "SUBSPACE_IPV4_POOL" getting ignored in the main program, because the "SUBSPACE_IPV4_PREF" variable it expects is never set. |
After providing SUBSPACE_IPV4_POOL as a docker-compose environment variable, I'm still ending up with peers defined in the default 10.99.98.3 space. Is this expected behavior?
The text was updated successfully, but these errors were encountered: