-
Notifications
You must be signed in to change notification settings - Fork 103
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 default config uses invalid network subnet #602
Comments
hi @roundowl, thanks for this warning, do you have time to open a PR with the fix? |
roundowl
pushed a commit
to roundowl/abstruse
that referenced
this issue
Jan 31, 2024
Docker compose plugin can't start using these configs because the network 10.20.20.0/16 is invalid and it expects either 10.20.0.0/16 or 10.20.20.0/24. Since we're using only three addresses and change only 4th octet, it's more viable to change the network to /24. Relevant issue: bleenco#602
Hi @jkuri, of course, here it is I've briefly checked that I can clone this repo and run all three configs, but didn't (couldn't) run the complete testing environment. |
jkuri
pushed a commit
that referenced
this issue
Jan 31, 2024
Docker compose plugin can't start using these configs because the network 10.20.20.0/16 is invalid and it expects either 10.20.0.0/16 or 10.20.20.0/24. Since we're using only three addresses and change only 4th octet, it's more viable to change the network to /24. Relevant issue: #602
thank you for the fix! I think testing env is deprecated and should be removed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Greetings!
From the readme:
However, running the above (with the exception of running through docker compose plugin) leads to:
I propose replacing the 10.20.20.0/16 subnet with 10.20.20.0/24, since the default config only uses addresses 10, 20 and 30 in that network. With only this change, the demo setup runs successfully.
The text was updated successfully, but these errors were encountered: