You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by "Baoyuantop (via GitHub)" <gi...@apache.org> on 2023/02/01 07:35:51 UTC

[GitHub] [apisix-ingress-controller] Baoyuantop opened a new issue, #1637: bug: exec failed, "curl" not found in $PATH

Baoyuantop opened a new issue, #1637:
URL: https://github.com/apache/apisix-ingress-controller/issues/1637

   ### Issue description
   
   I am using apisix ingress controller according to this document
   https://apisix.apache.org/docs/ingress-controller/tutorials/proxy-the-httpbin-service/
   
   When I got to this point in the execution I found the error
   ```
   kubectl exec -it -n ${namespace of Apache APISIX} ${Pod name of Apache APISIX} -- curl http://127.0.0.1:9180/apisix/admin/routes -H 'X-API-Key: edd1c9f034335f136f87ad84b625c8f1'
   ```
   
   The errors are as follows:
   ```
   Defaulted container "apisix" out of: apisix, wait-etcd (init)
   OCI runtime exec failed: exec failed: unable to start container process: exec: "curl": executable file not found in $PATH: unknown
   command terminated with exit code 126
   ```
   
   After troubleshooting, we found that apisix changed the image to `debian`, which caused the `curl` command to be unavailable, so we may need to update the documentation.
   
   ### Environment
   
   - your apisix-ingress-controller version (output of apisix-ingress-controller version --long):
   - your Kubernetes cluster version (output of kubectl version):
   - if you run apisix-ingress-controller in Bare-metal environment, also show your OS version (uname -a):
   
   
   ### Minimal test code / Steps to reproduce
   
   https://apisix.apache.org/docs/ingress-controller/tutorials/proxy-the-httpbin-service/
   
   ### Actual result
   
   Following the documentation can be successfully executed.
   
   ### Error log
   
   ```
   Defaulted container "apisix" out of: apisix, wait-etcd (init)
   OCI runtime exec failed: exec failed: unable to start container process: exec: "curl": executable file not found in $PATH: unknown
   command terminated with exit code 126
   ```
   
   ### Expected result
   
   _No response_


-- 
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: notifications-unsubscribe@apisix.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [apisix-ingress-controller] Baoyuantop commented on issue #1637: bug: exec failed, "curl" not found in $PATH

Posted by "Baoyuantop (via GitHub)" <gi...@apache.org>.
Baoyuantop commented on issue #1637:
URL: https://github.com/apache/apisix-ingress-controller/issues/1637#issuecomment-1421706047

   fixed by https://github.com/apache/apisix-docker/pull/419


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [apisix-ingress-controller] tao12345666333 commented on issue #1637: bug: exec failed, "curl" not found in $PATH

Posted by "tao12345666333 (via GitHub)" <gi...@apache.org>.
tao12345666333 commented on issue #1637:
URL: https://github.com/apache/apisix-ingress-controller/issues/1637#issuecomment-1411592215

   We can modify all the examples to enter the Pod of apisix-ingress-controller to operate


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [apisix-ingress-controller] fengshunli commented on issue #1637: bug: exec failed, "curl" not found in $PATH

Posted by "fengshunli (via GitHub)" <gi...@apache.org>.
fengshunli commented on issue #1637:
URL: https://github.com/apache/apisix-ingress-controller/issues/1637#issuecomment-1417172505

   Do you need to modify the dockerfile in debian and centos? @Baoyuantop 


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [apisix-ingress-controller] fengshunli commented on issue #1637: bug: exec failed, "curl" not found in $PATH

Posted by "fengshunli (via GitHub)" <gi...@apache.org>.
fengshunli commented on issue #1637:
URL: https://github.com/apache/apisix-ingress-controller/issues/1637#issuecomment-1417020089

   see https://github.com/apache/apisix-ingress-controller/pull/1648 @tao12345666333 


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [apisix-ingress-controller] Baoyuantop commented on issue #1637: bug: exec failed, "curl" not found in $PATH

Posted by "Baoyuantop (via GitHub)" <gi...@apache.org>.
Baoyuantop commented on issue #1637:
URL: https://github.com/apache/apisix-ingress-controller/issues/1637#issuecomment-1417216039

   Just modify the `debian`, cc @tao12345666333 


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [apisix-ingress-controller] fengshunli commented on issue #1637: bug: exec failed, "curl" not found in $PATH

Posted by "fengshunli (via GitHub)" <gi...@apache.org>.
fengshunli commented on issue #1637:
URL: https://github.com/apache/apisix-ingress-controller/issues/1637#issuecomment-1416925562

   Is the solution to this fix is to install curl command processing in the container? @tao12345666333 


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [apisix-ingress-controller] Baoyuantop commented on issue #1637: bug: exec failed, "curl" not found in $PATH

Posted by "Baoyuantop (via GitHub)" <gi...@apache.org>.
Baoyuantop commented on issue #1637:
URL: https://github.com/apache/apisix-ingress-controller/issues/1637#issuecomment-1417148134

   Hi @fengshunli, we need to add `curl` in the APISIX docker image, you can refer to https://github.com/apache/apisix-docker, apisix-ingress-controller no need to change. 


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [apisix-ingress-controller] Baoyuantop closed issue #1637: bug: exec failed, "curl" not found in $PATH

Posted by "Baoyuantop (via GitHub)" <gi...@apache.org>.
Baoyuantop closed issue #1637: bug: exec failed, "curl" not found in $PATH
URL: https://github.com/apache/apisix-ingress-controller/issues/1637


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org