25min Delay in starting Nixpack Build
I just noticed our latest deployment was taking 27mins to finish, so I checked it out and noticed our docker image push (or so I think that is it) was 800MB. I checked, and apparently we've been doing this for like 2 weeks, 800MB docker images each time. This sounds pretty unusual, as we don't use anything that heavy. Additionally, our builds usually finish in 3 minutes, so by this logic, nothing is out of the ordinary.
10 Replies
Project ID:
3c0425aa-9fe4-449a-a161-8a1efb3b53ee3c0425aa-9fe4-449a-a161-8a1efb3b53ee
Our stack is NextJS, Prisma, PostgreSQL with Nixpacks.
A build a day ago took from 11:04:12:287 to 11:04:12:293 to upload the docker image. That is 6 milleseconds for 830MB. WTF.
Okay, checking our latest build, it responds with very similar timings. So I have no clue why it took 27 mins.
14 mins later it restarted?
And it only started the server at 3PM, around 30mins after the merge & push occurred (2:35PM)
I just realized the restart was me. Times match up.
But here's the weird thing in the deployment
25min difference from the top to the bottom
nixpacks hasn't even started
Hey, flagging @AhmedMozaly who might be able to give you some color here
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
We resolved it, I don't know what my partner did but deployments are building normally again
Yea, its an issue on our end, hence we wanna know which deployment had the delay