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.

Sign up for GitHub

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

Jump to bottom

Windows installer defaults installing 64-bit binaries into 32-bit directory (x86) #2670

Closed
rakslice opened this issue Apr 2, 2018 · 7 comments
Closed

Windows installer defaults installing 64-bit binaries into 32-bit directory (x86) #2670

rakslice opened this issue Apr 2, 2018 · 7 comments
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. packaging/windows Windows packaging issues priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@rakslice
Copy link

rakslice commented Apr 2, 2018

Please provide the following details:

Environment:

Windows 10 Pro 1709 (build 16299.309) 64-bit US English

Minikube version (use minikube version):

v0.25.2

What happened:

Installer proposed default install directory C:\Program Files (x86)\Kubernetes\Minikube

What you expected to happen:

Installer should propose C:\Program Files\Kubernetes\Minikube (or the corresponding system directory as appropriate on other regional Windows variants)
@rakslice rakslice changed the title Windows minikube-installer installs 64-bit software in 32-bit software location Windows minikube-installer defaults to putting 64-bit software in 32-bit software location Apr 2, 2018
@rakslice rakslice closed this as completed Apr 2, 2018
@rakslice rakslice reopened this Apr 2, 2018
@rakslice
Copy link
Author

rakslice commented Apr 2, 2018

See http://nsis.sourceforge.net/Reference/$PROGRAMFILES

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 1, 2018
@rakslice
Copy link
Author

rakslice commented Jul 1, 2018

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 1, 2018
@rakslice
Copy link
Author

rakslice commented Jul 1, 2018

Issue is still present in v0.28.0

@tstromberg tstromberg added kind/bug Categorizes issue or PR as related to a bug. packaging/windows Windows packaging issues os/windows labels Sep 19, 2018
@tstromberg tstromberg changed the title Windows minikube-installer defaults to putting 64-bit software in 32-bit software location Windows installer defaults installing 64-bit binaries into 32-bit directory (x86) Sep 19, 2018
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 18, 2018
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 17, 2019
@tstromberg tstromberg added help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Jan 24, 2019
@tstromberg
Copy link
Contributor

This is still an issue AFAIK, and I would more than happy to review any PR's which fix the issue. Help wanted!

@tstromberg tstromberg added priority/backlog Higher priority than priority/awaiting-more-evidence. and removed os/windows labels Jan 24, 2019
@igorakkerman igorakkerman mentioned this issue Mar 18, 2019
Merged
@tstromberg tstromberg reopened this Mar 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. packaging/windows Windows packaging issues priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@tstromberg @rakslice @k8s-ci-robot @fejta-bot