Warning: file_get_contents(/data/phpspider/zhask/data//catemap/7/kubernetes/5.json): failed to open stream: No such file or directory in /data/phpspider/zhask/libs/function.php on line 167

Warning: Invalid argument supplied for foreach() in /data/phpspider/zhask/libs/tag.function.php on line 1116

Notice: Undefined index: in /data/phpspider/zhask/libs/function.php on line 180

Warning: array_chunk() expects parameter 1 to be array, null given in /data/phpspider/zhask/libs/function.php on line 181
无法在kubernetes中运行OpenDistro for Elastic,因为出现了非root-supervisord错误_Kubernetes_Elasticsearch Opendistro - Fatal编程技术网

无法在kubernetes中运行OpenDistro for Elastic,因为出现了非root-supervisord错误

无法在kubernetes中运行OpenDistro for Elastic,因为出现了非root-supervisord错误,kubernetes,elasticsearch-opendistro,Kubernetes,Elasticsearch Opendistro,我正在Kubernetes为Elastic设置OpenDistro。集群具有pod安全性,不允许特权pod。启动集群时,日志显示/usr/share/supervisor/supervisor.log存在权限问题 我在部署中设置了securityContext securityContext: runAsUser: 1000 fsGroup: 1000 `` The error message from kubectl logs es-master-0 is ```/usr/share

我正在Kubernetes为Elastic设置OpenDistro。集群具有pod安全性,不允许特权pod。启动集群时,日志显示/usr/share/supervisor/supervisor.log存在权限问题

我在部署中设置了securityContext

securityContext:
  runAsUser: 1000
  fsGroup: 1000
``

The error message from kubectl logs es-master-0 is
```/usr/share/elasticsearch/config/elasticsearch.yml seems to be already configured for Security. Quit.
Traceback (most recent call last):
  File "/usr/bin/supervisord", line 9, in <module>
    load_entry_point('supervisor==4.0.2', 'console_scripts', 'supervisord')()
  File "/usr/lib/python2.7/site-packages/supervisor-4.0.2-py2.7.egg/supervisor/supervisord.py", line 358, in main
    go(options)
  File "/usr/lib/python2.7/site-packages/supervisor-4.0.2-py2.7.egg/supervisor/supervisord.py", line 368, in go
    d.main()
  File "/usr/lib/python2.7/site-packages/supervisor-4.0.2-py2.7.egg/supervisor/supervisord.py", line 70, in main
    self.options.make_logger()
  File "/usr/lib/python2.7/site-packages/supervisor-4.0.2-py2.7.egg/supervisor/options.py", line 1472, in make_logger
    backups=self.logfile_backups,
  File "/usr/lib/python2.7/site-packages/supervisor-4.0.2-py2.7.egg/supervisor/loggers.py", line 417, in handle_file
    handler = RotatingFileHandler(filename, 'a', maxbytes, backups)
  File "/usr/lib/python2.7/site-packages/supervisor-4.0.2-py2.7.egg/supervisor/loggers.py", line 212, in __init__
    FileHandler.__init__(self, filename, mode)
  File "/usr/lib/python2.7/site-packages/supervisor-4.0.2-py2.7.egg/supervisor/loggers.py", line 159, in __init__
    self.stream = open(filename, mode)
IOError: [Errno 13] Permission denied: '/usr/share/supervisor/supervisord.log'
securityContext:
runAsUser:1000
组别:1000
``
来自kubectl日志es-master-0的错误消息为
```/usr/share/elasticsearch/config/elasticsearch.yml似乎已经配置了安全性。退出
回溯(最近一次呼叫最后一次):
文件“/usr/bin/supervisord”,第9行,在
加载入口点('supervisor==4.0.2','console\u scripts','supervisords')()
文件“/usr/lib/python2.7/site packages/supervisor-4.0.2-py2.7.egg/supervisor/supervisord.py”,第358行,主文件
go(选项)
文件“/usr/lib/python2.7/site packages/supervisor-4.0.2-py2.7.egg/supervisor/supervisord.py”,第368行,在go中
d、 main()
文件“/usr/lib/python2.7/site packages/supervisor-4.0.2-py2.7.egg/supervisor/supervisord.py”,第70行,主文件
self.options.make_logger()
文件“/usr/lib/python2.7/site packages/supervisor-4.0.2-py2.7.egg/supervisor/options.py”,第1472行,make_记录器
备份=self.logfile\u备份,
handle_文件中的文件“/usr/lib/python2.7/site packages/supervisor-4.0.2-py2.7.egg/supervisor/loggers.py”,第417行
handler=RotatingFileHandler(文件名'a',最大字节数,备份)
文件“/usr/lib/python2.7/site packages/supervisor-4.0.2-py2.7.egg/supervisor/loggers.py”,第212行,在__
FileHandler.\uuuu init\uuuuuu(self、filename、mode)
文件“/usr/lib/python2.7/site packages/supervisor-4.0.2-py2.7.egg/supervisor/loggers.py”,第159行,在__
self.stream=打开(文件名,模式)
IOError:[Errno 13]权限被拒绝:'/usr/share/supervisor/supervisord.log'

你好,Isaanc,欢迎来到SO。如果看不到整个
部署
描述符和/或任何定制的
Dockerfile
,就不可能知道什么设置可能出错。请包括更多详细信息,而不仅仅是错误消息。您将希望对群集中具有“标识”的服务使用部署,而不是部署,例如Elasticsearch或Postgres等。谢谢。我已经找到了一个使用initcontainer的解决方案,并将为OpenDistro社区github repo创建一个PR。我认为这可以归结为kubernetes的安全实践,而不是任何好的或坏的配置。我在minikube上没有这个问题,只是在公司集群上。欢迎来到SO。如果看不到整个
部署
描述符和/或任何定制的
Dockerfile
,就不可能知道什么设置可能出错。请包括更多详细信息,而不仅仅是错误消息。您将希望对群集中具有“标识”的服务使用部署,而不是部署,例如Elasticsearch或Postgres等。谢谢。我已经找到了一个使用initcontainer的解决方案,并将为OpenDistro社区github repo创建一个PR。我认为这可以归结为kubernetes的安全实践,而不是任何好的或坏的配置。我在minikube上没有这个问题,只是在公司集群上。干杯