Anyone seeing issues with containers in GitHub Actions (despite no code change)? 3 pointsvaillancourtmax3 years ago5 commentsSaveHideCopy link On HNComments−stimnw3yIt looks like the postgres docker containers were updated about 1pm pacific, which is around when we started to see issues.there's a new PR merged into the github repo to fix a bug caused by the above merge: https://github.com/docker-library/postgres/commit/41bd7bf3f4...I bet they'll be pushing out new containers shortly.−vaillancourtmaxOP3yGreat catch, thank you for pointing this out. Looks like it's resolved now.−cmorss3yYup, seeing it here too. postgres container in docker-compose is not started by the time it's needed anymore. What are you seeing?−holtbp3ySame−theCrowing3yGithub Actions is our new DNS no matter what you can always say "uh... I don't know actions was down again."
Comments
It looks like the postgres docker containers were updated about 1pm pacific, which is around when we started to see issues.
there's a new PR merged into the github repo to fix a bug caused by the above merge: https://github.com/docker-library/postgres/commit/41bd7bf3f4...
I bet they'll be pushing out new containers shortly.
Great catch, thank you for pointing this out. Looks like it's resolved now.
Yup, seeing it here too. postgres container in docker-compose is not started by the time it's needed anymore. What are you seeing?
Same
Github Actions is our new DNS no matter what you can always say "uh... I don't know actions was down again."