motongxue commented on issue #10997:
URL: https://github.com/apache/apisix/issues/10997#issuecomment-1981079922
### Problem Diagnosis:
- When configuring APISIX via Docker and setting the environment variable
`-e APISIX_STAND_ALONE=true`, you specified APISIX to run in standalone mode.
- However, it was discovered that APISIX's default configuration file
`conf/config.yaml` does not have specific settings for standalone mode, leading
APISIX to attempt to connect to etcd.
- This issue was initially unnoticed because my computer environment was
previously set up with APISIX according to the official tutorial, and the etcd
service was continuously running.
### Problem Manifestation:
- After I stopped the APISIX and etcd Docker containers that were installed
based on the official tutorial, without proper configuration of
`conf/config.yaml`, the `docker logs -f apache-apisix` command revealed that
APISIX continuously attempts to connect to etcd.
### Solution:
- To resolve this issue, it is necessary to configure `conf/config.yaml` to
ensure the file is correctly set to support standalone mode.
- After making appropriate modifications to `conf/config.yaml`, APISIX will
no longer attempt to connect to etcd but instead load configurations directly
from the local file.
conf/config.yaml
```yaml
deployment:
role: data_plane
role_data_plane:
config_provider: yaml
#END
```
### References:
- For more details on the standalone mode, you can refer to the deployment
modes section in the APISIX official documentation: [Standalone
Mode](https://apisix.apache.org/docs/apisix/deployment-modes/#standalone).
- For the initial installation and configuration of APISIX, you can refer to
the official tutorial: [APISIX Quick
Start](https://apisix.apache.org/docs/apisix/getting-started/README/).
--
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]
