boh001 opened a new issue, #163:
URL: https://github.com/apache/apisix-go-plugin-runner/issues/163
### Issue description
I launched it from an apisix image in docker, but the error is still there.
Dockerfile
```Dockerfile
FROM golang:1.22.5 AS plugin-builder
WORKDIR /builder
COPY go-runner .
RUN CGO_ENABLED=0 go build .
FROM apache/apisix:3.9.1-debian
ENV APISIX_STAND_ALONE=true
EXPOSE 9080 9180 9091 9443 9092
COPY apisix.yaml /usr/local/apisix/conf/apisix.yaml
COPY --from=plugin-builder /builder/go-runner
/usr/local/apisix-go-plugin-runner/go-runner
```
apisix.yaml
```yaml
routes:
- uri: /
plugin_config_id: 1
upstream:
nodes:
"upstream-nlb-9780037035286027.elb.ap-northeast-2.amazonaws.com": 1
type: roundrobin
plugin_configs: # 여기서 plugins_configs가 아니라 plugin_configs입니다.
- id: 1
plugins:
ext-plugin-pre-req:
name: ext-plugin-pre-req
config:
name: "say"
value:
body: "Hello, APISIX!"
ext-plugin:
cmd: ["/usr/local/apisix-go-plugin-runner/go-runner", "run"]
#END
```
Furthermore, when I checked /usr/local/apisix/config in Docker, there is no
sock file and no environment variable named APISIX_LISTEN_ADDRESS.
```bash
apisix@fe350b633c44:/usr/local/apisix/conf$ ls
apisix.uid apisix.yaml cert config-default.yaml config.yaml debug.yaml
mime.types nginx.conf
```
```bash
apisix@fe350b633c44:/usr/local/apisix/conf$ printenv
APISIX_STAND_ALONE=true
HOSTNAME=fe350b633c44
PWD=/usr/local/apisix/conf
HOME=/home/apisix
TERM=xterm
SHLVL=1
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/openresty/luajit/bin:/usr/local/openresty/nginx/sbin:/usr/local/openresty/bin
_=/usr/bin/printenv
OLDPWD=/usr/local/apisix
```
### Environment
* APISIX Go Plugin Runner's version:
* APISIX version: apache/apisix:3.9.1-debian
* Go version: 1.22.5
* OS (cmd: `uname -a`): arm64
--
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]
