Pin influxdb image to v1.8.4 in docker-compose.yml #198
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
v1.6.4 Merge
v1.6.5 Merge
v1.6.6 Merge
v1.6.7 Merge
v1.6.8 Merge
v1.7.0 Merge
v1.7.1 Merge
v1.7.2 Merge
v1.7.3 Merge
v1.7.4 Merge
My Varken recently blew up because Influxdb was mistakenly upgraded to v2.0. The only errors in the logs were authentication failures. After some debugging and documentation reading, I discovered the incompatible version of Influxdb. I know v2.0 support is around the corner (#195), but this could save other people the same problems in the future. I'd start pinning specific supported image versions for all required containers.
|
Please merge into develop instead. |
|
I created a bug (#199) before seeing this pull request as I faced exactly the same issue |
|
Going to close this as the rebase messed up the changes. I have updated develop with |
What could I have done more appropriately? Asking for feedback/instruction. |
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.
My Varken recently blew up because Influxdb was mistakenly upgraded to v2.0. The only errors in the logs were authentication failures. After some debugging and documentation reading, I discovered the incompatible version of Influxdb.
I know v2.0 support is around the corner (#195), but this could save other people the same problems in the future. I'd start pinning specific supported image versions for all required containers.