You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using go-containerregistry to upload helm charts to an OCI registry (distribution/registry), using the vSphere networking, I receive a 400 Bad Request response.
Workarounds that mitigate the problem are:
Replacing the compressed layer streaming logic with ioutil.ReadAll into a []byte and performing the HTTP Patch request using that as the body instead
Using a local port-forward logic such as sudo ncat --sh-exec "ncat 10.220.54.215 30000" -l 30000 --keep-open
To Reproduce
Using a vSphere network connected to a Kubernetes NodePort exposed service for a pod running distribution/registry running in Kubernetes, and using the library to push a helm chart to the registry.
Expected behavior
The helm chart is uploaded.
Additional context
Add any other context about the problem here.
I am using v0.20.1 of the go-containerregistry library
Describe the bug
When using go-containerregistry to upload helm charts to an OCI registry (distribution/registry), using the vSphere networking, I receive a 400 Bad Request response.
Workarounds that mitigate the problem are:
sudo ncat --sh-exec "ncat 10.220.54.215 30000" -l 30000 --keep-open
To Reproduce
Using a vSphere network connected to a Kubernetes NodePort exposed service for a pod running distribution/registry running in Kubernetes, and using the library to push a helm chart to the registry.
Expected behavior
The helm chart is uploaded.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: