-
Notifications
You must be signed in to change notification settings - Fork 603
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker repository - Unsupported protocol scheme "null" #565
Comments
same error msg 3.76.1-01 is good? |
Yes, it is. |
Hello, I'm seeing the same error with pulls on 3.77.1:
I wonder since it did not show up in release test runs maybe this is due to some legacy option carried from a previous version? Can one force schema so the value is not null but for example http in jetty? settings? |
I just checked the docker daemon on a linux machine and the logs suggest http/https mixup:
|
As a workaround, I modified the class org.sonatype.nexus.bootstrap.jetty.NexusRequestCustomizer as follows:
|
hello @giacgbj , would you mind attaching compiled class? or even the whole nexus-bootstrap-3.77.1-01.jar? |
It's the compiled class from 3.77.0-08, but it should work fine. |
Nice, thank you it worked 👍 |
same here with |
Same problem here. Can't apply workaround because we're running the container I tried downgrading to 3.76.1 but nexus won't start because of the data folder upgrade.
Is there a way to force a downgrade? |
I patched the compiled class into the |
Is that in the next release of nexus ? |
No, I just patched it into my local image as a workaround. |
I can confirm that this worked for me too, for my deployment of 3.77.1-01, using docker.
|
for anyone brand new to Nexus (like myself) if you don't actually need "Allow anonymous docker pull" you might try un-checking that box. when I un-check that box, the error went away for me, and I'm able to push/pull to the repo as desired. |
Same here. Can we expect the patch soon? |
@mpiggott Could you label this issue as a bug perhaps? |
With the class file above http works again, but then https doesn't work! We need both working!!! |
Hi guys, I am trying the trick with the class file but I am getting this error: nexus 2025-02-16 17:43:21,622+0000 WARN [FelixStartLevel] *SYSTEM javax.xml.bind - Using non-standard property: javax.xml.bind.JAXBContext. Property javax.xml.bind.JAXBContextFactory should be │ I havent touch manifest file... just copied the class file into jetty folder then put it into jar again with jar -cvf |
At the end I have create custom image based on 3.77.1 and apline java 17 and used that class for jetty. |
We are facing the same problem. After deactivating "Allow anonymous docker pull" our Jenkins was able to push to the registry again, but we are not able to pull from anywhere, even with login. We have checked that all needed privileges are set for the logged-in user, but it does not work anymore. Even activating "Allow anonymous docker pull" doesn't make it work again. Everything worked fine in 3.76.1. |
We are also affected by this issue. |
is 3.77.2 Released February 25, 2025 resolved tihs issue ? |
No, it did not. I just tested this. |
I just upgraded from nexus-3.76.1-01 to nexus-3.77.0-08 and I can't login to a hosted Docker repository anymore. The error is:
$ docker login 1.2.3.4:2375
Error response from daemon: Get "http://1.2.3.4:2375/v2/": Get "null://1.2.3.4:2375/v2/token?account=foo&client_id=docker&offline_token=true&service=null%3A%2F%2F1.2.3.4%3A2375%2Fv2%2Ftoken": unsupported protocol scheme "null"
The text was updated successfully, but these errors were encountered: