Issue confirmed this happens on Windows - ops uses rg instad of grep so any reference to grep shoud be re places with rg. Any PR fix ing this in tasks is appreciated it is an easy fix
-- Michele Sciabarra [email protected] ----- Original message ----- From: "Ersabba (via GitHub)" <[email protected]> To: [email protected] Subject: [I] Error during OpenServerLess Installation (Local Docker) [openserverless] Date: Saturday, March 08, 2025 2:35 PM Ersabba opened a new issue, #101: URL: https://github.com/apache/openserverless/issues/101 - [x] I have searched the [issues](https://github.com/apache/openserverless/issues) of this repository and believe that this is not a duplicate. ### Ⅰ. Issue Description Installation completes with errors. ### Ⅱ. Describe what happened Errors shown at the end of installation are the following: OpenServerless host and auth set successfully. You are now ready to use ops! ok: updated package hello ok: updated action hello/hello **_"grep": executable file not found in $PATH_** ops: Failed to run task "login": exit status 127 task execution error: ops: Failed to run task "login": exit status 127 ops: Failed to run task "devcluster": exit status 1 task execution error: ops: Failed to run task "devcluster": exit status 1 ### Ⅲ. Describe what you expected to happen The installation should end with no errors: OpenServerless host and auth set successfully. You are now ready to use ops! ok: updated package hello ok: updated action hello/hello "body": "hello, Nuvolaris" ### Ⅳ. How to reproduce it (as minimally and precisely as possible) 1. Install ops 2. ops config minimal 3. ops setup devcluster ### Ⅴ. Anything else we need to know? solvable with a workaround, before installing OpenServerLess: 1. Install GREP 2. install RIPGREP and in file opsfile.yml replace grep with rg command. ### Ⅵ. Environment: - K8S Runtime and version: - OPS CLI version: 0.1.0-2409121919.dev - OS: Windows Server 2022 Version 21H2 (OS Build 20348.3207) - Docker Version: Docker Desktop 4.38.0 (181591) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
