R
RunPod4d ago
EMPZ

GitHub integration: "exporting to oci image format" takes forever.

It's been running for over 30 minutes on this step. Same image builds in less than 5 minutes in GitHub Actions. Why does it take so long? This is the first build. Would it be better for subsequent builds (assuming there's some caching involved?)? To me this is unusable and I much rather just do the build and push myself and just change the endpoint image version.
4 Replies
EMPZ
EMPZOP4d ago
Well, after a while it failed with the following error:
2024-12-16 17:30:54 [ERROR] Error: failed to receive status: rpc error: code = Unavailable desc = closing transport due to: connection error: desc = "error reading from server: EOF", received prior goaway: code: ENHANCE_YOUR_CALM, debug data: "too_many_pings"
2024-12-16 17:30:54 [ERROR] Build failed in the first attempt. Will retry one more time before exiting.
2024-12-16 17:30:54 [ERROR] Error: failed to receive status: rpc error: code = Unavailable desc = closing transport due to: connection error: desc = "error reading from server: EOF", received prior goaway: code: ENHANCE_YOUR_CALM, debug data: "too_many_pings"
2024-12-16 17:30:54 [ERROR] Build failed in the first attempt. Will retry one more time before exiting.
PRB
PRB4d ago
Expect a fix in the next few weeks. We are aware of it
EMPZ
EMPZOP4d ago
So it finally finished (just took a long time). I can see that subsequent builds are using Docker layer caching (good), so the actual build is pretty fast. But still, the "exporting to oci image format" takes forever.
PRB
PRB4d ago
Yeah we have caching for build and push. This is just a temporary thing thats there but will be gone soon
Want results from more Discord servers?
Add your server