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

.exe file is missing from the versions after v1.31.2 #2717

Closed
divyansh42 opened this issue Sep 11, 2021 · 5 comments
Closed

.exe file is missing from the versions after v1.31.2 #2717

divyansh42 opened this issue Sep 11, 2021 · 5 comments
Labels
os/windows status/stale Issue went stale; did not receive attention or no reply from the OP

Comments

@divyansh42
Copy link

divyansh42 commented Sep 11, 2021

In the OpenShift tools Installer action we support the installation of CRC on the Windows platform.
For Windows OS this works using .exe file but it seems after version 1.31.2 .exe is replaced with MSI files.
To be able to support installation in Windows we definitely need exe files as we need to run this action without admin permissions and the MSI file needs admin permissions.
By any chance, can we get exe file back?

Ref: redhat-actions/openshift-tools-installer#50

cc @jduimovich @tetchel

@praveenkumar
Copy link
Member

@divyansh42 How did you perform the crc setup then before running crc start for those action because even in case of exe file we do need to run the setup for administrator privilege to perform like enabling hyperV or usermode networking side.

@gbraad
Copy link
Contributor

gbraad commented Sep 13, 2021

Unfortunately we will not be offering phat-binaries anymore. The install process as mentioned before crc setup was too involved and made the binary bloated. While it allows to easily move files around, it leaves a multitude of large files on the disk (eg. 2+ GB binary, 2+ GB bundle, 3+ GB disk image, etc).

The MSI is a single time affair. Or use the msi from the command line with msiexec ?

@stale
Copy link

stale bot commented Nov 16, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the status/stale Issue went stale; did not receive attention or no reply from the OP label Nov 16, 2021
@stale stale bot closed this as completed Dec 8, 2021
@cfergeau
Copy link
Contributor

cfergeau commented Dec 9, 2021

Did you manage to integrate the new installation process in your tools? Or do you need more help from our side for this?
@divyansh42 @tetchel @jduimovich ?

@divyansh42
Copy link
Author

Due to some other priorities, we were not able to devote much time to this.
I'll update this issue in case some help is needed from your side.
Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
os/windows status/stale Issue went stale; did not receive attention or no reply from the OP
Projects
None yet
Development

No branches or pull requests

4 participants