Issues Uploading Container Images to Sonatype Nexus3 #9466
-
|
I run Nexus3 for an artifactory, and at some point (unsure of the trigger) I have started to see Concourse unable to properly push container images to my registry. I do not observe this behavior when using the My redactions are shown below as Here's my main NGINX reverse proxy config for Nexus (it's running in k8s, as is Concourse, but this reverse proxy is a separate device not on k8s): Here's an output from the I realize this issue may be on the Nexus side and not Concourse. I suspect a recent Nexus upgrade I ran is what caused this, but I cannot be sure as I cannot nail down the timeline. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
|
In the registry-image, the uploading of images is done by https://github.com/google/go-containerregistry Your hunch that it's an issue on the Nexus end seems likely. You could try checking their repo for similar issues as well. |
Beta Was this translation helpful? Give feedback.
-
|
@taylorsilva I finally found the line in the Nexus log which points me to my reverse-proxy configuration. For some reason when uploading via the |
Beta Was this translation helpful? Give feedback.
-
|
Further closing the loop here for @taylorsilva - Unsure exactly how this happened, but my Docker settings in Nexus had path-based routing enabled for the
Flipping it to blank solved my problem. To everybody who reads this discussion, let this be a lesson - check all of your possible logs before raising a GitHub discussion. I should have checked my Nexus logs earlier. |
Beta Was this translation helpful? Give feedback.
@taylorsilva I finally found the line in the Nexus log which points me to my reverse-proxy configuration. For some reason when uploading via the
dockerCLI I do not encounter this issue; I do in Concourse. I'll continue my investigation. Unless you have some insight, I consider this discussion closed.