503 Response object too large when trying to pull #26568
-
Hi everyone, I used a Github action to build & push an image to github container registry. All the other layers are properly pulled. Here is the workflow I used to build & push the image : github.comHartorn/satisfactory-serverContribute to Hartorn/satisfactory-server development by creating an account on GitHub. I’m available to provide more details. Cheers, |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
Hi Hartorn,
Hartorn:
Due to the way our caching works, there is currently a limit of 4GB per layer. We’re hoping to fix this, but I don’t have an ETA for exactly when. The workaround would be to break your image into layers of 4GB or less. Might this be feasible? |
Beta Was this translation helpful? Give feedback.
-
Hi @jcansdale, No not really. The layer is about 16go (yeah, quite big ^^’) Nvm, not a big issue for me, I’m using a GCP container registry for that time, will do as a workaround. I feel like it would be better to break the push command still atm, to avoid people being able to push, but not pull. It feels quite weird, and I took some time to say : “oh must be github”. I have no strict timing on ETA, but I’m available to test if needed Cheers. |
Beta Was this translation helpful? Give feedback.
-
@Hartorn this should be fixed now. Please give it a try again and let me know if its still a problem for you. Thanks! |
Beta Was this translation helpful? Give feedback.
-
@markphelps Pulling it right now. Thanks ! |
Beta Was this translation helpful? Give feedback.
@Hartorn this should be fixed now. Please give it a try again and let me know if its still a problem for you.
Thanks!