Postgresql would not start from a Windows WSL2 host - could not change permissions about aws-mwaa-local-runner HOT 2 CLOSED

Well forget all of that I guess. My main misstep was crossing file systems - which is not recommended (1).

When opening the WSL2 Ubuntu terminal it defaults to a Windows filesystem folder. By simply typing cd ~ I am in my home directory under the linux filesystem(1). From there, I can follow the aws-mwaa-local-runner "Get Started" instructions as written and they work great. No docker volume create needed. No modification to docker-compose-local.yml needed.

(1) https://docs.microsoft.com/en-us/windows/wsl/compare-versions#performance-across-os-file-systems

from aws-mwaa-local-runner.

@bradthurber - Huge credit to you for these instructions, which were linked from SO (link: https://stackoverflow.com/questions/71096132/aws-mwaa-postgres-not-reachable-error-when-trying-to-run-a-local-apache-airfl/72416210#72416210).

Yes, you're correct that the line endings had to be changed -- which I did. However, I still had to use your proposed solution above to get past the postgres issue. So thank you for your earlier write-up.

I hope that the main project's github readme someday includes a note on the line endings issue and also somehow fixes the docker-compose-local.yml file to work in Windows, without breaking other OSes.

from aws-mwaa-local-runner.