[docker] postgres healthcheck not operational

[jcpsantiago]

📓 Description

Summary of the change and link to any relevant tickets. New aliases should include details of why they are valuable

Fixed some typos and YAML white space problems preventing the config from being valid.

I couldn't docker-compose up with the name attribute present, so I removed it in this PR:

(root) Additional property name is not allowed

But reading the docs it sounds like it should be correct? No idea.

:octocat Type of change

Please tick x relevant options, delete those not relevant

• New feature
• Deprecate feature
• Development workflow
• Documentation
• Continuous integration workflow

:beetle How Has This Been Tested?

• unit test
• linter check
• GitHub Action checkers

:eyes Checklist

• Code follows the Practicalli cljstyle configuration
• Add / update alias docs and README where relevant
• Changelog entry describing notable changes
• Request practicalli-john review the PR

[jcpsantiago]

Postgres's healthcheck is failing with this error peter-evans/docker-compose-healthcheck#16
The proposed solution in peter-evans/docker-compose-healthcheck#17 is to change the command to

["CMD-SHELL", "pg_isready -d {db} -U {user}"]

but it didn't work for me

[practicalli-johnny]

I couldn't docker-compose up with the name attribute present, so I removed it in this PR:

(root) Additional property name is not allowed

But reading the docs it sounds like it should be correct? No idea.

I am unable to reproduce this issue, using Docker Desktop 4.18.0 (104112) on Linux

What version of Docker is being used, it may be using an older docker compose v1 spec

Also the command to run docker compose should be

docker compose up

rather than the older command form docker-compose up (I'll check if this is documented)

[practicalli-johnny]

Postgres's healthcheck is failing with this error peter-evans/docker-compose-healthcheck#16 The proposed solution in peter-evans/docker-compose-healthcheck#17 is to change the command to

["CMD-SHELL", "pg_isready -d {db} -U {user}"]

but it didn't work for me

There is a healthcheck both in compose.yaml and the Dockerfile, so some testing of both seems to be required.

Try comment the healthcheck configuration in the compose.yaml file, it can be dropped if its not working and simply use the Dockerfile healthcheck for deployed services (e.g. prod)

[jcpsantiago]

I couldn't docker-compose up with the name attribute present, so I removed it in this PR:

(root) Additional property name is not allowed

But reading the docs it sounds like it should be correct? No idea.

I am unable to reproduce this issue, using Docker Desktop 4.18.0 (104112) on Linux

What version of Docker is being used, it may be using an older docker compose v1 spec

Also the command to run docker compose should be

docker compose up

rather than the older command form docker-compose up (I'll check if this is documented)

my bad. I'm coding on my 2012 iMac with MacOS 10, so I had an ancient docker version. I'm running 4.15 (the most I can on this beast) and now name: works fine, and also the healthcheck (with my changes adding -d and -U).

I'm using docker compose up.