Docker and MongoDB Version Updates #25
Open
Conversation
This file contains hidden or 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
…e with the current version of the docker compose plugin
…nd to skip tests which depend on miniswarm if that is not available
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 updates the mongo controller image and service and all related compose and test files to use supported versions of Docker and MongoDB.
For Docker: it has been tested with docker-ce v29+, which dropped support for older docker engine API versions.
For MongoDB: it has been tested with MongoDB v4.4 (the earliest version still supported) and all major versions up to 8.2 (the current supported minor version)..
The docker compose files used for development and test environments have been updated to current compose file syntax
The local tests are passing on a local swarm (miniswarm is old and no longer supported, so I have not tested that option)
The tests that would be run by travis-ci are also running and passing on a local swarm.