https://cal.com logo
Join Slack
Powered by
<@U034HPK8KCG>
# docker
z
@alannnc
c
if the container is failing to start or isn't responding to health checks
is that the github action?
z
yup
from E2E tests
c
oops, meant for thread
i'm not certain why two different versions of postgres are being used there
one is postgres:13, then the other is postgres which is = postgres:latest
i haven't seen that double container style before
honestly, I wonder if it's short on resources
z
Weird. but why now tho?
c
I've already had to kill the emulated ARM build on the docker project, because the runners are too small for the build and running out of memory
have you tried running the tests locally to see if it passes?
z
locally runs fine for me
c
that's usually an indicator of runner resources for me
the build is pretty hefty bc of all the components
(that'll get better when you start referencing npm packages instead of the local package references)
for experimentation you could try enabling the new Large Runners
or setting up your local machine as a self-hosted runner
here's info on the large runners, there's a beta signup https://docs.github.com/en/actions/using-github-hosted-runners/using-larger-runners
(but obviuosly use the cal.com repo instead. I just don't have access to the settings on that one, so the screenshot is from the docker repo)
z
I see
c
doesn't like my windows/WSL for the ARM emulator :grimage
z
Would it help to match postgress versions?
c
worth a try
that last one is when :web is building
(my local machine as a runner)
jumped up to 9gb at one point
Open in Slack
PreviousNext
Powered by