Skip to content
This repository has been archived by the owner on Jan 22, 2024. It is now read-only.

Plugin.Activate, 400 Bad Request: malformed Host header #83

Closed
elezar opened this issue Apr 21, 2016 · 6 comments
Closed

Plugin.Activate, 400 Bad Request: malformed Host header #83

elezar opened this issue Apr 21, 2016 · 6 comments
Labels

Comments

@elezar
Copy link
Member

elezar commented Apr 21, 2016

When using the deb package to install nvidia-docker on a system running docker 1.9.1, the following message is presented when trying to start a container using nvidia-docker:

>nvidia-docker run nvida/cuda nvidia-smi
Error response from daemon: Error looking up volume plugin nvidia-docker: Plugin Error: Plugin.Activate, 400 Bad Request: malformed Host header

Upgrading to docker=1.10.3 solved this problem.

On production machines, we still have to use 1.9.1, so if 1.9 is really the minimum requirement it would be great if this would work. Alternatively, the wiki page should be updated.

@3XX0 3XX0 changed the title Docker>=1.9 requirement is incorrect for deb package Plugin.Activate, 400 Bad Request: malformed Host header Apr 21, 2016
@3XX0
Copy link
Member

3XX0 commented Apr 21, 2016

This incompatibility is due to a breaking change in the Go http package.
Docker 1.9 is probably compiled against Go 1.5 while nvidia-docker is compiled against 1.6
Try changing FROM golang to FROM golang:1.5 here and rebuild nvidia-docker from sources

@elezar
Copy link
Member Author

elezar commented Apr 21, 2016

Thanks for the tip!

@elezar elezar closed this as completed Apr 21, 2016
@elezar
Copy link
Member Author

elezar commented Apr 21, 2016

Sorry, did not want to close (it can be if you like).

@elezar elezar reopened this Apr 21, 2016
@3XX0
Copy link
Member

3XX0 commented Apr 21, 2016

Does it work? If it fixes the problem we might want to stick to Go 1.5

@3XX0 3XX0 added the bug label Apr 21, 2016
@elezar
Copy link
Member Author

elezar commented Apr 22, 2016

Hi, I have already solved the problem by upgrading docker. I will see if I can replicate and test the fix as soon as I have access to the system again.

@3XX0 3XX0 mentioned this issue Apr 25, 2016
@elezar
Copy link
Member Author

elezar commented Apr 26, 2016

I have just had a chance to test on another system that showed the same behaviour, and I can confirm that switching to the golang:1.5 base image no longer shows the message that I originally reported (and allows for docker 1.9.1 to be used).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants