HDDS-12931. [Ozone 2.0] Update ozone.scm.datanode.id.dir in the docker-compose.yaml of ozone-docker repo. #45
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
…r-compose.yaml of ozone-docker repo.
adoroszlai
approved these changes
Apr 29, 2025
Contributor
adoroszlai
left a comment
adoroszlai
left a comment
There was a problem hiding this comment.
Thanks @jojochuang for finding this problem and for the patch.
We should update ozone-latest, ozone-2.0.0, ozone-2.0.0-rocky branches/images as well.
We don't need to update those, because docker-compose.yaml is not part of the image.
Contributor
Author
|
Yes if we follow the v2 quick start instruction to download docker-compose.yaml from github: https://ozone-site-v2.staged.apache.org/docs/quick-start/installation/docker |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Apache JIRA: https://issues.apache.org/jira/browse/HDDS-12931
Make the docker-compose.yaml configuration consistent with the ones in the main ozone repo. See #7402 (arguably a breaking change)
We should update ozone-latest, ozone-2.0.0, ozone-2.0.0-rocky branches/images as well.