Skip to content

Conversation

@Rajakavitha1
Copy link
Collaborator

Updated the configuration to help multipart uploads to ensure that there is no 500 error. Based on the discussion
https://www.linode.com/community/questions/24117/unknown-error-500-on-pushing-image-to-private-docker-registry#answer-84451

…rage

Updated the configuration to help multipart uploads to ensure that there is no 500 error.
@netlify
Copy link

netlify bot commented Nov 23, 2023

Deploy Preview for nostalgic-ptolemy-b01ab8 ready!

Name Link
🔨 Latest commit f3ae6d8
🔍 Latest deploy log https://app.netlify.com/sites/nostalgic-ptolemy-b01ab8/deploys/67226c1a0451aa00080e8284
😎 Deploy Preview https://deploy-preview-6744--nostalgic-ptolemy-b01ab8.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link
Collaborator

@wildmanonline wildmanonline left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have not tested this but based on that community site post, I assume that there should be an additional configData YAML parameter included with the following:

configData:
  storage:
    s3:
      multipartcopythresholdsize: 5368709120

Or maybe it's just:

storage:
  s3:
    multipartcopythresholdsize: 5368709120

I'm likely wrong though! All this to say, has it been validated through official docs or by testing?

@Rajakavitha1
Copy link
Collaborator Author

Hi @jddocs ! I was not able to reproduce the error. However, I made the updates as suggested here: https://www.linode.com/community/questions/24117/unknown-error-500-on-pushing-image-to-private-docker-registry

@jddocs jddocs added the Ready label Oct 30, 2024
@jddocs jddocs merged commit b4a2acb into develop Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants