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

Error: invalid json response body #3185

Closed
yaroslavsadin opened this issue Sep 3, 2021 · 2 comments · Fixed by #3195
Closed

Error: invalid json response body #3185

yaroslavsadin opened this issue Sep 3, 2021 · 2 comments · Fixed by #3195

Comments

@yaroslavsadin
Copy link

Hi,

I can't connect to our company's private registry on Nexus. I still can connect using 1.10.0 version but not with the later. I checked that /v2/ returns 200 but Docker says:

Error: invalid json response body at https://.../v2/ reason: Unexpected end of JSON input

Could you give me a clue on what had changed?

@bwateratmsft
Copy link
Contributor

It looks like in the changeover from request to node-fetch, the behavior for empty bodies is different. The /v2/ body is empty in some cases and should parse into an undefined JSON object.

@bwateratmsft
Copy link
Contributor

The fix for this has been released in Docker extension 1.17.0.

@vscodebot vscodebot bot locked and limited conversation to collaborators Oct 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants