-
Notifications
You must be signed in to change notification settings - Fork 37
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
Newer docker version #1419
Merged
Merged
Newer docker version #1419
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aequitas
force-pushed
the
newer-docker-versions
branch
5 times, most recently
from
May 30, 2024 09:08
8a8c548
to
27f1a24
Compare
aequitas
force-pushed
the
newer-docker-versions
branch
17 times, most recently
from
June 3, 2024 14:51
457f08a
to
df979ef
Compare
aequitas
force-pushed
the
newer-docker-versions
branch
2 times, most recently
from
June 3, 2024 15:47
b6fc41d
to
fd6dc84
Compare
aequitas
force-pushed
the
newer-docker-versions
branch
from
June 5, 2024 12:53
fd6dc84
to
d50e45a
Compare
… Docker/Compose Due to some changes in the handling of config files in Compose, some configurations might not work on older or newer versions of Docker/Compose. Use a matrix to test both.
…ronment. Due to a change in Docker's DNS resolver (moby/moby#47589) in version 25.0.5 (https://docs.docker.com/engine/release-notes/25.0/#2505), traffic to the mock resolver used in integration/batch tests is no longer forwarded. This is fixed in moby/moby#47822 in version 26.0.3 (https://docs.docker.com/engine/release-notes/26.0/#2603). - Temporary add upgrade commands to CI because 26.0.3 is not yet in the default CI image - Add checks to warn about incompatible versions - Add documentation to help developers get the right versions
Somehow Chromium disables IPv6 resolving when there is no IPv6 default route or when it cannot connect to a specific address: https://issues.chromium.org/issues/40435291 Switching to Firefox as browser until this can be solved.
- Docker Compose 2.24 broke behaviour we rely on for merging .env files. Versions since 2.27.1 restore this funcitonality: docker/compose#11824
mxsasha
force-pushed
the
newer-docker-versions
branch
from
June 13, 2024 20:40
d50e45a
to
3a99706
Compare
aequitas
force-pushed
the
newer-docker-versions
branch
from
June 14, 2024 09:18
cf94048
to
bf0e95f
Compare
aequitas
force-pushed
the
newer-docker-versions
branch
5 times, most recently
from
June 14, 2024 10:27
cb7f9fe
to
ba377b6
Compare
aequitas
force-pushed
the
newer-docker-versions
branch
from
June 17, 2024 13:00
ba377b6
to
4f33015
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes several issues with newer Docker/Compose versions:
!override
in the YAML file explicitly we get the expected behaviour on newer version which is backwards compatible with older versions as well.ipv6.internet.nl
domains and the connection test) to fail. Switching to Firefox as browser used for testing. There might be a way to override this behaviour in Chrome using theIPv6ReachabilityOverrideEnabled
policy, but so far I have not been able to make it work inside the playwright Docker image using available documentation. Firefox does seem a little bit slower on executing the tests so we might want to switch back to Chrome if we can.no configuration file provided: not found
). This has been fixed in 2.27.0 but seems to be broken again in 2.27.1 due to [BUG] Incompatible.env
file behavior docker/compose#11880. Currently Compose in CI will be pinned to 2.27.0.Besides the fixes the following changes are included: