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

[BUG] Powershell script for running the daemon does not exist #3837

Closed
schultzp2020 opened this issue Sep 13, 2023 · 7 comments
Closed

[BUG] Powershell script for running the daemon does not exist #3837

schultzp2020 opened this issue Sep 13, 2023 · 7 comments
Labels
kind/bug Something isn't working os/windows

Comments

@schultzp2020
Copy link

General information

  • OS: Windows
  • Hypervisor: Hyper-V
  • Did you run crc setup before starting it (Yes/No)? N/A, installed through Podman Desktop
  • Running CRC on: Laptop

CRC version

$ crc version
CRC version: 2.26.0+233df0
OpenShift version: 4.13.9
Podman version: 4.4.4

CRC status

$ crc status --log-level debug
DEBU CRC version: 2.26.0+233df0
DEBU OpenShift version: 4.13.9
DEBU Podman version: 4.4.4
DEBU Running 'crc status'
Machine does not exist. Use 'crc start' to create it

CRC config

$ crc config view
- consent-telemetry                     : no

Host Operating System

$ systeminfo

Host Name:                 PSCHULTZ-LAPTOP
OS Name:                   Microsoft Windows 10 Pro
OS Version:                10.0.19045 N/A Build 19045
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          [email protected]
Registered Organization:   N/A
Product ID:                00330-80846-80580-AA719
Original Install Date:     8/9/2021, 09:13:09
System Boot Time:          9/13/2023, 16:48:15
System Manufacturer:       Eluktronics Inc.
System Model:              MAX-17
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: AMD64 Family 25 Model 80 Stepping 0 AuthenticAMD ~3301 Mhz
BIOS Version:              American Megatrends International, LLC. N.1.18ELU05, 5/21/2021
Windows Directory:         C:\Windows
System Directory:          C:\Windows\system32
Boot Device:               \Device\HarddiskVolume5
System Locale:             en-us;English (United States)
Input Locale:              en-us;English (United States)
Time Zone:                 (UTC-06:00) Central Time (US & Canada)
Total Physical Memory:     32,158 MB
Available Physical Memory: 20,690 MB
Virtual Memory: Max Size:  39,582 MB
Virtual Memory: Available: 24,096 MB
Virtual Memory: In Use:    15,486 MB
Page File Location(s):     C:\pagefile.sys
Domain:                    WORKGROUP
Logon Server:              \\PSCHULTZ-LAPTOP
Hotfix(s):                 34 Hotfix(s) Installed.
                           [01]: KB5029919
                           [02]: KB5028951
                           [03]: KB4562830
                           [04]: KB4570334
                           [05]: KB4577586
                           [06]: KB4580325
                           [07]: KB4586864
                           [08]: KB4598481
                           [09]: KB5000736
                           [10]: KB5003791
                           [11]: KB5011048
                           [12]: KB5012170
                           [13]: KB5015684
                           [14]: KB5008575
                           [15]: KB5030211
                           [16]: KB5006753
                           [17]: KB5007273
                           [18]: KB5011352
                           [19]: KB5011651
                           [20]: KB5014032
                           [21]: KB5014035
                           [22]: KB5014671
                           [23]: KB5015895
                           [24]: KB5016705
                           [25]: KB5018506
                           [26]: KB5020372
                           [27]: KB5022924
                           [28]: KB5023794
                           [29]: KB5025315
                           [30]: KB5026879
                           [31]: KB5028318
                           [32]: KB5028380
                           [33]: KB5029709
                           [34]: KB5005699
Network Card(s):           8 NIC(s) Installed.
                           [01]: Realtek Gaming 2.5GbE Family Controller
                                 Connection Name: Ethernet
                                 Status:          Media disconnected
                           [02]: Intel(R) Wi-Fi 6 AX200 160MHz
                                 Connection Name: Wi-Fi
                                 DHCP Enabled:    Yes
                                 DHCP Server:     192.168.68.1
                                 IP address(es)
                                 [01]: 192.168.68.57
                                 [02]: fe80::3e0c:655d:5452:fc9b
                           [03]: Bluetooth Device (Personal Area Network)
                                 Connection Name: Bluetooth Network Connection
                                 Status:          Media disconnected
                           [04]: ZeroTier Virtual Port
                                 Connection Name: ZeroTier One [8056c2e21c329a03]
                                 DHCP Enabled:    No
                                 IP address(es)
                                 [01]: 172.25.237.196
                                 [02]: fe80::71b7:4665:84c1:2d2e
                           [05]: DisplayLink Network Adapter NCM
                                 Connection Name: Ethernet 2
                                 Status:          Media disconnected
                           [06]: TAP-Windows Adapter V9
                                 Connection Name: OpenVPN TAP-Windows6
                                 Status:          Media disconnected
                           [07]: TAP-NordVPN Windows Adapter V9
                                 Connection Name: Ethernet 3
                                 Status:          Media disconnected
                           [08]: Hyper-V Virtual Ethernet Adapter
                                 Connection Name: vEthernet (WSL)
                                 DHCP Enabled:    No
                                 IP address(es)
                                 [01]: 172.19.112.1
                                 [02]: fe80::3ef:68be:a714:3b5a
Hyper-V Requirements:      A hypervisor has been detected. Features required for Hyper-V will not be displayed.

Steps to reproduce

  1. Install Podman
  2. Install Podman Desktop
  3. Initialize Podman
  4. Install OpenShift Local Extension
  5. Click initialize and run (OpenShift Local Extension)

Expected

OpenShift Local starts

Actual

OpenShift Local errors out

Logs

image

OpenShift Local start error: Error: Powershell script for running the daemon does not exist
@schultzp2020 schultzp2020 added kind/bug Something isn't working status/need triage labels Sep 13, 2023
@cfergeau
Copy link
Contributor

Does this help if you run crc setup from the commandline? Is it a fresh install, or were you using crc/podman desktop/... before?

@schultzp2020
Copy link
Author

@cfergeau

Does this help if you run crc setup from the commandline?

No, I keep getting this error when using the CLI after I reboot my PC.

$ crc setup
INFO Using bundle path C:\Users\Tanks\.crc\cache\crc_hyperv_4.13.9_amd64.crcbundle
INFO Checking minimum RAM requirements
INFO Checking if current user is in crc-users and Hyper-V admins group
INFO Checking if CRC bundle is extracted in '$HOME/.crc'
INFO Checking if C:\Users\Tanks\.crc\cache\crc_hyperv_4.13.9_amd64.crcbundle exists
INFO Checking if the daemon task powershell script is present
INFO Creating the daemon task powershell script
INFO Checking if the daemon task is installed
INFO Checking if the daemon task is running
INFO Running the daemon task
INFO Checking admin helper service is running
Make sure you installed crc using the Windows installer and performed required reboot

Is it a fresh install, or were you using crc/podman desktop/... before?

I just updated Podman, Podman Desktop, and OpenShift Local before running into this issue. It's been a while since I have used Podman Desktop because in previous versions I kept getting an error saying Podman disconnected from the daemon.

@gbraad
Copy link
Contributor

gbraad commented Sep 21, 2023

@anjannath reproducible?

@anjannath
Copy link
Member

yes, i am able to reproduce this, #3839 should fix it

@anjannath
Copy link
Member

@schultzp2020 Hi, the original issue you were facing the error Powershell script for running the daemon..." has been fixed in the crc-extension` could give it another try and let us know if this is fixed now, thanks!

@schultzp2020
Copy link
Author

Thank you for letting me know! I will update crc and give it a try tomorrow.

@anjannath
Copy link
Member

the powershell script is now replaced with background-launcher

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working os/windows
Projects
None yet
Development

No branches or pull requests

4 participants