apache / apache/apisix-go-plugin-runner

request help: connect() to unix:/usr/local/apisix/conf/apisix-1.sock failed (2: No such file or directory), client:

Open
#160 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
198
Forks
68
PR merge metrics
No merged PRs in 30d

Description

### Issue description
apisix deploy by docker
start :
docker run -d --name apisix --cpus 8 --memory 16G --network host -v /home/work/apisix/gateway-plugin:/usr/local/apisix/apisix-plugin-runner -v /home/work/apisix/config.yaml:/usr/local/apisix/conf/config.yaml -v /home/work/apisix/logs:/usr/local/apisix/logs -v /etc/localtime:/etc/localtime apache/apisix:latest

Execute make build to generate a new go runner executable program,than replace the old go-runner ,restart apisix
finally err !

![image](https://github.com/apache/apisix-go-plugin-runner/assets/37365340/0a1b7a96-a2fe-4322-8439-52552c62210c)

### Environment

* APISIX Go Plugin Runner's version:
* APISIX version:
* Go version:
* OS (cmd: `uname -a`):

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the Docker command, the output of `make build`, and the APISIX startup logs around `/usr/local/apisix/conf/apisix-1.sock`. Check how the newly built Go runner is replaced and how `/usr/local/apisix/conf/config.yaml` configures the runner. Done means APISIX starts and connects to the runner without the reported socket error.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, go
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.