sashokbg opened a new issue, #8616:
URL: https://github.com/apache/apisix/issues/8616

   ### Current Behavior
   
   Following the tutorial:
   
   https://apisix.apache.org/docs/apisix/stand-alone/ and using 
https://github.com/apache/apisix-docker
   
   I set mu apisix server in standalone mode
   
     apisix:
       image: apache/apisix:latest
       restart: always
       environment:
         APISIX_STAND_ALONE: true
       volumes:
         - error_vol:/usr/local/apisix/logs
         - ./apisix_conf/config.yaml:/usr/local/apisix/conf/config.yaml
       depends_on:
         - etcd
       ports:
         - "9180:9180/tcp"
         - "9080:9080/tcp"
         - "9091:9091/tcp"
         - "9443:9443/tcp"
         - "9092:9092/tcp"
       network_mode: host
   
   And when I start the server the config.yaml file gets overwritten and all my 
routes / upstreams disappear.
   
   
   
   ### Expected Behavior
   
   When Starting the docker compose with a volume   - 
./apisix_conf/config.yaml:/usr/local/apisix/conf/config.yaml then the 
config.yaml should be read into memory as described in the documentation
   
   ### Error Logs
   
   _No response_
   
   ### Steps to Reproduce
   
   1. Use the docker compose example - 
https://github.com/apache/apisix-docker/tree/master/example
   2. Set APISIX_STAND_ALONE: true
   3. Put some routes in apisix_conf/config.yaml
   4. Run docker-compose up
   5. Check the dashboard - no routes imported and file has been overwritten
   
   PS: if you don't remove the :ro flag from the volume mount the server does 
not start at all
   
   ### Environment
   
   - APISIX version: 3.1.0
   - Operating system: Linux alexander-p14s 6.1.1-arch1-1 #1 SMP 
PREEMPT_DYNAMIC Wed, 21 Dec 2022 22:27:55 +0000 x86_64 GNU/Linux
   


-- 
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]

Reply via email to