-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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: mac os m1 External Plugin Local MODO #10865
Comments
Hi @zhangchaoyanggit , can you please communicate im English ? |
Sorry, my English proficiency is limited |
@zhangchaoyanggit , when you do this step APISIX_LISTEN_ADDRESS=unix:/usr/local/apisix/x.sock ./the_runner , |
As can be seen, it has been mapped to the interior of the container |
Can you please check the permission of the socket and send the output here, without proper permissions docker may mount it as a directory. Run : |
stat x.sock |
@zhangchaoyanggit , can you try |
Sorry, this command is not available in the container, but it works normally on the mounted host |
sorry, I can not reproduce. |
This is my configuration in docker-compose-arm64.yaml touch /usr/local/apisix/test Command executed normally |
@zhangchaoyanggit I found an issue which maybe useful. apache/apisix-java-plugin-runner#161 in the doc: https://apisix.apache.org/docs/java-plugin-runner/the-internal-of-apisix-java-plugin-runner/
|
It should be able to support Mac, otherwise how could there be documentation on the official website? Without a Mac, debugging costs would greatly increase. It's best for the community to provide support thanks |
@zhangchaoyanggit , You should try to check unix domain socket is work normal in you macos docker env first , And the apisix will not be supported MacOS |
@shreemaan-abhishek So now I think this issue is resolved. If we need to add support for mac. we can create a new issue. |
Very disappointed, it's hard to understand |
yes APISIX is not support for mac now, we can close this issue @shreemaan-abhishek |
Current Behavior
docker desktop 通过 docker-compose 启动apisix 并配置config.yaml
ext-plugin:
path_for_test: "/usr/local/apisix/x.sock" # without 'unix:' prefix
在docker-compose中挂在宿主机下的x.sock 本地idea启动加入环境变量APISIX_LISTEN_ADDRESS 赋予宿主机地址,插件正常启动.但是apisix无法找到这个文件,导致apisix执行路由的时候无法到我本地的插件代码.
Expected Behavior
通过访问apisix路由地址,能走到我本地的插件代码中
Error Logs
phase_func(): failed to connect to the unix socket unix:/usr/local/apisix/x.sock: connection refused, client: 172.20.0.1, server: _, request: "GET /order2/test HTTP/1.1", host: "localhost:9080"
Steps to Reproduce
创建一个路由,并配置插件,然后访问这个路由,正常应该走入我本地的插件代码,但是现在连接失败,以上配置参考apisix官网的文档,在windows环境下按照windows的配置方式可以正常到我本地. 参考https://apache-apisix.netlify.app/zh/docs/apisix/next/external-plugin/
Environment
openresty -V
ornginx -V
):curl http://127.0.0.1:9090/v1/server_info
):The text was updated successfully, but these errors were encountered: