kworkbee opened a new issue, #12471:
URL: https://github.com/apache/apisix/issues/12471
### Description
### Issue description
The custom plug-in implementation is integrated with APISIX images to
operate Gateway in a production environment.
```Dockerfile
FROM ${APISIX_IMAGE}
USER root
WORKDIR /app
COPY ./apisix-runner-bin/apisix-java-plugin-runner.jar
/app/apisix-external-plugin.jar
RUN apt-get update && \
apt-get install -y --no-install-recommends openjdk-11-jdk && \
rm -rf /var/lib/apt/lists/*
RUN chown -R apisix:apisix /app
USER apisix
```
I am using the image built by configuring Dockerfile as above. If an API
request to use the plug-in occurs as shown in the log below, an error that
there is no socket file occurs.
```
2025/07/29 17:25:08 [error] 50#50: *45468 [lua] init.lua:889: phase_func():
failed to connect to the unix socket unix:/app/conf/apisix-1.sock: no such file
or directory, client: X.X.X.X, server: _, request: "GET /api/v1/something
HTTP/1.1", host: "api.corp.com"
```
Previously, Plugin Runner Version is `0.4.0`, and Base Image is
`3.9.1-debian`, which was not much of an issue at this time.
The error continues to occur after upgrading to Plugin Runner version
`0.6.0`. It is operating in a Kubernetes environment, and even if you change
the securityContext setting, the error continues to occur without much change.
### Environment
- APISIX version (run `apisix version`): `3.9.1`
- Operating system (run `uname -a`): `AWS AL2023`
- OpenResty / Nginx version (run `openresty -V` or `nginx -V`):
- etcd version, if relevant (run `curl
http://127.0.0.1:9090/v1/server_info`):
- APISIX Dashboard version, if relevant:
- Plugin runner version, for issues related to plugin runners: `0.4.0`
- LuaRocks version, for installation issues (run `luarocks --version`):
--
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-unsubscr...@apisix.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
