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

Kamel binary install on Windows 10 with Minikube #619

Closed
pchakina opened this issue Apr 17, 2019 · 3 comments
Closed

Kamel binary install on Windows 10 with Minikube #619

pchakina opened this issue Apr 17, 2019 · 3 comments

Comments

@pchakina
Copy link

Hi,
I am working with Windows 10 Enterprise edition with Minikube. I installed Minikube on windows 10 .

Step1 : minikube start : it looks good
Stpe 2: minikube addons enable registry :
- registry was successfully enabled ....message displayed on screen
Step 3: I have downloaded camel-k-client-0.3.2-windows-64bit for Kamel binary
Step 4: Updated windows system path variable to points to Kamel binary directory
Step 5: kamel install Here i found issue....unable to install kamel binary.....system is showing pop-up window with notepad ....etc ...options to open... Please find attached image for details.

Can you help me out on this to install kamel binary.

Thanks,
Pchakina


Kamel Install error using Minikube on windows 10 Enterprise edition

@zregvart
Copy link
Member

@pchakina what does where kamel and echo %PATH% output? You might need to logout and login again to get the PATH environment variable to update.

@pchakina
Copy link
Author

Hi ,
Thanks for the reply. i have verified path variable and logged out and login again ...i am not seeing any difference. What is the extension of Kamel binary ...? Please find attached image.
i am seeing this error ....even setting Kamel binary file path in windows environment variable also ... Its windows 10 Professional environment

'kamel' is not recognized as an internal or external command,
operable program or batch file.

KAMEL on windows 10 screen
path screen settings
Kamel binary path location

Thanks,
pchakina

@jamesnetherton
Copy link
Contributor

jamesnetherton commented Apr 25, 2019

I think this happens because there is no file extension on the kamel binary. So Windows is not sure of how to handle it. If you rename the file to kamel.exe, you should find that it starts working.

To fix this in future releases, I could tweak the cross_compile.sh script to add a .exe extension to the Windows kamel binary.

jamesnetherton added a commit to jamesnetherton/camel-k that referenced this issue Apr 25, 2019
valdar pushed a commit to jboss-fuse/camel-k that referenced this issue May 21, 2019
ipolyzos pushed a commit to ipolyzos/camel-k that referenced this issue Jul 31, 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