Skip to content

e2e: fix invalid ip range #846

Merged
Choraden merged 2 commits intomainfrom
hg/fix_dns_e2e
Jun 18, 2024
Merged

e2e: fix invalid ip range #846
Choraden merged 2 commits intomainfrom
hg/fix_dns_e2e

Conversation

@Choraden
Copy link
Contributor

No description provided.

Choraden added 2 commits June 18, 2024 10:50
In Docker Compose network settings, the ip_range field within the ipam.config section specifies a range of IP addresses
from the defined subnet that can be allocated to containers.
If it is left empty it means no specific range is set, and Docker can allocate any address from the entire subnet.

We don't need ip range for the sake of e2e tests. That would keep the compose as simple as possible.
We don't need to be that specific in e2e tests. Moreover, it easy to make a mistake in calculating the range.
@Choraden Choraden merged commit 196054e into main Jun 18, 2024
@Choraden Choraden deleted the hg/fix_dns_e2e branch June 18, 2024 09:01
@mmatczuk
Copy link
Contributor

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants