-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Improve error message about packaging problem of docker-machine-driver tarball #4486
Comments
I think this is due to a bad binary naming, I will regenerate all the binaries |
Can you try again with this link: https://github.com/scaleway/docker-machine-driver-scaleway/releases/download/v1.0.2/docker-machine-driver-scaleway_1.0.2_linux_amd64.tar.gz ? |
I have tried but I get the same error unfortunately. Also tried to rename with only middle dashes but it doesn't work either. |
Taring with only the go static binary at the root (no folder) did the trick! Keeping this issue opened and renaming to focus on catching the error and displaying it to the end user. |
@jmatsushita can you outline what you did to work around it exactly? Can you give the original file structure inside the tar that caused the problem? Definitely something we should handle more gracefully on our end. |
The original file structure is inside this tarball https://github.com/scaleway/docker-machine-driver-scaleway/releases/download/v1.0.2/docker-machine-driver-scaleway_1.0.2_linux_amd64.tar.gz which has a |
ok. thanks for reporting. we'll get it fixed. I think the intended behavior right now is to log/reply with a sensible error message saying that the tar should just contain the binary, but the logic is flawed and it is instead panicing. |
Verified with v1.1.0-dev2-rc4 that there is no longer a panic with invalid URL. Intstead there is an error |
Rancher Version:
1.0.1
Docker Version:
OS:
Steps to Reproduce:
Install docker machine driver:
Results:
The driver doesn't install and the UI keeps displaying "Request..."
Logs display:
Expected:
The text was updated successfully, but these errors were encountered: