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

   ### Description
   
   Trying to run apisix, I have all the required resources, however I get the 
following log from the apisix pod:
   ```
   /usr/local/openresty//luajit/bin/luajit ./apisix/cli/apisix.lua init
   WARNING: using fixed Admin API token has security risk.
   Please modify "admin_key" in conf/config.yaml .
   failed to update nginx.conf: failed to open file: 
/usr/local/apisix/conf/nginx.conf, error 
info:/usr/local/apisix/conf/nginx.conf: Permission denied
   ```
   However, I can't seem to find why the file is created with only root 
permissions, and not sufficient permission for apisix service account? (which 
exists in my cluster).
   I'm using openshift containers platform 4.12.
   I've seen the issue refered 
[here](https://github.com/apache/apisix-ingress-controller/issues/305), 
However, I don't understand why adding `anyuid` is a necessity here.
   I can't really understand lua (hence the help request) but It does not seem 
like something that must be, since the nginx does not listen in port 80.
   
   
   
   ### Environment
   
   - APISIX version (run `apisix version`): 3.6.0
   - Operating system (run `uname -a`): Linux 
apisix-client-1-68ddb78b56-jl788-debug-6stlf 4.18.0-372.73.1.el8_6.x86_64 #1 
SMP Fri Sep 8 13:16:27 EDT 2023 x86_64 GNU/Linux
   - OpenResty / Nginx version (run `openresty -V` or `nginx -V`): nginx 
version: openresty/1.21.4.2
   
   Irrelevant:
   - etcd version, if relevant (run `curl 
http://127.0.0.1:9090/v1/server_info`): 
   - APISIX Dashboard version, if relevant:
   - Plugin runner version, for issues related to plugin runners:
   - LuaRocks version, for installation issues (run `luarocks --version`):
   


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