This filebeat.yml file comes with the container and be modified it but then I run into another problem, which is that when i try to execute filebeat I get the responseĮxiting: data path already locked by another beat. rw-r- 1 root filebeat 315 Feb 5 23:09 filebeat.yml,
#Elastic filebeats container full
filebeat.yml:/usr/share/filebeat/filebeat.yml" from the docker-compose file then go into the docker container for filebeat, at this point I have full access to the base filebeat.yml, which when using the ls -l filebeat.yml command give me this response I have managed to found a work around to this problem by removing the command rwxrwxrwx 1 filebeat filebeat 464 Feb 24 13:17 filebeat.ymlĪnd before it is suggested I have tried to use chmod, and chown commands to try and change the permission of the file within the filebeat.yml container but I am denied the ability to do it.
Even when I go into the container it says that everyone should have access to it When checking the permission through the command ls -l filebeat.yml on the host computer I get: -rwxrwxrwx 1 zebul zebul 464 Feb 24 13:29 filebeat.yml so everyone should be allowed access to it. The file in question is assigned some weird permission and locks me out from accessing it even though I have set the user in the container to root. filebeat.yml:/usr/share/filebeat/filebeat.yml" The problem seem to be that when using the volume command My probelm is that when I try to run it filebeat will imidietly exit and give me this error response:Įxiting: error loading config file: config file ("filebeat.yml") must be owned by the user identifier (uid=0) or root Hello I am currently unable of properly starting my filebeat process from its container.
0 kommentar(er)
