Consistenlty failing to push on GitHub container registry withought knowing what needs to be fixed #120865
-
Select Topic AreaBug BodyWe use GitHub to host our code. Our code is not in a single repository. We have more than one repositories.
Whenever we want to release a service, system, etc. we just specify the tag of the image we want to release, and the release is performed. Hence it's mandatory we have published our latest version in the corresponding GitHub container registry, in order we be able to release it. If we fail for any reason for that then we can't release the latest introduced changes. For only one of our repos, we have started to notice great fluctuation in the time needed to push the generate image to the corresponding GitHub container registry. Sometimes the whole workflow takes 20 mins, other 1 hour, without any change in the generated image. The problem we have spotted is associated with the push of generated image to the the corresponding GitHub container registry. From today we are blocked, we can push, simply because this step takes forever: We have already raised our concern to GitHub, but we haven't received any help so far. Does anyone has something to suggest, on how we can deal with this problem ? Thanks PS. One of our last efforts was to start deleting old images from that container registry assuming that their size could somehow indirectly affects us. However this didn't help at all. Also our last effort was to reduce significantly the size of the image we push. Also this didn't work. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
After one month, and having GitHub to take a second look, they informed as that something has change in the size of the container. So we fixed it. |
Beta Was this translation helpful? Give feedback.
After one month, and having GitHub to take a second look, they informed as that something has change in the size of the container. So we fixed it.