Hi, we are trying to start container in Qovery, but get mirroring error. Seems that might be timeout issue, because this part works fine when we try it with very small size image. Is there a way to change that timeout or do you have any other info about that?
Hello @km1414,
Can you share the qovery console link ?
@Melvin_Zottola Hi, any updates on this? Seems that any image with size >2GB takes too much time to mirror and process crashes because of timeout. Is there a way to fix it?
New link for the reference: https://console.qovery.com/organization/2119cfce-8e17-474a-9a13-d0e6f0c2794b/project/e5894769-84d5-46af-a9d0-1fd3727737c9/environment/2c240f82-81c4-47e2-8280-a2fb49cf4717/logs/f9ae1901-3c04-45e2-b053-ab6a7e074f0c/deployment-logs
Hello @km1414,
I’m checking but this seems related to an issue with scaleway registry during the mirroring, I’m digging
Doing manually the command with a docker image > 2Gb works fine locally on my side (it took ~ 200s to push the image from ECR to Scaleway container registry)
But, as our environment engines are located in us-east-2 region on AWS side, it seems to introduce some latency.
I’ll increase the timeout on our side and ping you once this is done
Dev is still in progress, an alternative in the meantime would be to push directly your image into your cluster registry to skip mirroring: Default container registry for Scaleway cluster - #9 by Melvin_Zottola
Hello @km1414,
After digging into this issue, the cause is actually that the mirroring takes too much time: AWS seems to throttle the bandwidth + our engines are located in us-east-2
The preferred solution would be that you push your images directly to your scaleway registry to skip the mirroring (link above)
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.