Fixes 23925: docs - Update docker-compose-postgres.yml #23926
+3
−2
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
changed the port and uses consistent volume mechanism I am using rancher-desktop on MacOSX, because my colleagues use it and we need some containers with AVX support, which rosetta does not support. We also cannot use docker-desktop license. The error I get relates to chown not being able to change ownership of the folder mount. Likely some fun between OSX using qemu and the rancher desktop docker coordinator
LewisCowlesMotive
requested review from
akash-jain-10,
harshach and
tutte
as code owners
Contributor
|
Hi there 👋 Thanks for your contribution! The OpenMetadata team will review the PR shortly! Once it has been labeled as Let us know if you need any help! |
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.
Describe your changes:
Fixes #23925
I worked on changing the default port, and volume mechanism for postgres because the container would not start on my machine.
By using a non-standard postgres port, this is more likely to run on others machines.
By following the covention used elsewhere within the compose file, the volume permissions are no longer an issue.
Type of change:
Checklist:
Fixes <issue-number>: <short explanation>Documentation:
I have considered use-cases outside of my own and remain open to feedback and contributing wider changes around this proposed fix