Skip to content
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

Compatibility between cli and sregistry versions? #213

Closed
Trophime opened this issue Jun 3, 2019 · 11 comments
Closed

Compatibility between cli and sregistry versions? #213

Trophime opened this issue Jun 3, 2019 · 11 comments

Comments

@Trophime
Copy link

Trophime commented Jun 3, 2019

Hi,
I wonder if there is some compatibility issue with sregistry-cli version and sregistry version.
I've tried to push an image with 0.1.39 cli version to a 0.0.94 sregistry and I got:

sregistry search
[client|registry] [database|sqlite:////home/LNCMI-G/trophime/.singularity/sregistry.db]
ERROR The server returned a malformed response.

Best
C

@vsoch
Copy link
Member

vsoch commented Jun 3, 2019

What do the server logs say? (docker-compose logs)

@vsoch
Copy link
Member

vsoch commented Jun 3, 2019

There was an update of sregistry server (a while back) to use the Nginx upload module, so if you didn’t update your server you will need to use an earlier version of the client.

@Trophime
Copy link
Author

Trophime commented Jun 3, 2019

Unfortunately I don't have access to the server log :(

@vsoch
Copy link
Member

vsoch commented Jun 3, 2019

Did you just update the client? If so, go back to the previous version.

@Trophime
Copy link
Author

Trophime commented Jun 3, 2019

The previous version is indeed working!

@vsoch
Copy link
Member

vsoch commented Jun 3, 2019

Also, are you not able to communicate with whomever runs your server? They can give you a more direct response about if there’s a change.

@Trophime
Copy link
Author

Trophime commented Jun 3, 2019

The server used to be was administred by @victorsndvg ...
But I don't know who is in charge of it right now.
I'm checking that

@vsoch
Copy link
Member

vsoch commented Jun 3, 2019

Great! What happened to @victorsndvg? He used to post on here a lot and it's been a while.

To give you some docs about the changes you are seeing, a little less than a year ago the server was upload to use the nginx upload module which allows for much faster uploads.

And of course on the same date the client was also updated. You are getting that message because you have a client sending a ping to an endpoint that doesn't exist, and the fix is to keep your version of sregistry cli less than 0.0.88.

@victorsndvg
Copy link

Dear @vsoch and @Trophime ,

I'm no longer working for the project/institution which I've to use/deploy sregistry. This means that I don't have access/rights to administer services ...

Anyway, @Trophime I remember that I containerize sregistry to freeze the working version at that moment. If you take a look to the registry, you are going to see several sregistry versions. 0.0.94 and 0.0.98 versions are available, and probably latest is the recomended version to interact with the registry

Hope to helpful.

Best regards!

@Trophime
Copy link
Author

Trophime commented Jun 3, 2019

Thanks @victorsndvg
indeed it works fine with your sregistry image ;)

Best

@vsoch
Copy link
Member

vsoch commented Jun 3, 2019

Safe and fun journeys ahead @victorsndvg ! It's been a pleasure working with you these last few years.

@vsoch vsoch closed this as completed Jun 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants