502 error on deploy

1

Hello,

I have been seeing this during the deploy state:

\u001b[31mError\u001b[0m received unexpected HTTP status: 502 Bad Gateway"}

I wonder whether it is the issue before with the remote build, since it is doing a remote docker build. Seems to be regular issues.

Could fly support using a private docker image, as presumably if the image was pushed to gcr or equivalent, it could pull from there and deploy it without issue? But it would need to authenticate itself to do so.

Since currently CI does not have docker available locally. So the build has to be done remotely, which randomly fails, as above.

2

This is almost certainly an issue with an api gateway that we’re working on. It’s on our end so you don’t need to change your build. Deploying from private repositories is on our roadmap but no timeframe yet.

2 Likes