xzzh999 opened a new issue #113:
URL: https://github.com/apache/apisix-docker/issues/113


   Hi~ 
   Greate job!
   
   I use the docker hub official `apisix apline-2.1` image, and when init it 
run error: 
   ```
   /usr/local/openresty/luajit/bin/luajit: /usr/bin/apisix:218: bad argument #1 
to 'ipairs' (table expected, got nil)
   
   stack traceback:
        [C]: in function 'ipairs'
   
        /usr/bin/apisix:218: in function </usr/bin/apisix:150>
   
        /usr/bin/apisix:419: in main chunk
   
        [C]: at 0x55d22c265300
   ```
   i use potainer to create the container, with the follow mount vol:
   ```
   /root/apisix/cfg:/usr/local/apisix/conf
   ```
   and both ***config-default.yaml*** and ***config.yaml*** are the same as 
follow:
   (the etcd have been started ok, and etcd address is 172.17.0.5:2379)
   ```
   apisix:
     node_listen: 9080              # APISIX listening port
     enable_ipv6: false
   
     allow_admin:                  # 
http://nginx.org/en/docs/http/ngx_http_access_module.html#allow
       - 0.0.0.0/0              # We need to restrict ip access rules for 
security. 0.0.0.0/0 is for test.
   
     admin_key:
       - name: "admin"
         key: edd1c9f034335f136f87ad84b625c8f1
         role: admin                 # admin: manage all configuration data
                                     # viewer: only can view configuration data
       - name: "viewer"
         key: 4054f7cf07e344346cd3f287985e76a2
         role: viewer
   
   etcd:
     host:                           # it's possible to define multiple etcd 
hosts addresses of the same etcd cluster.
       - "http://172.17.0.5:2379";     # multiple etcd address
     prefix: "/apisix"               # apisix configurations prefix
     timeout: 30                     # 30 seconds
   
   ```
   
   need u help, thx~


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

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to