Skip to content

Kibana-5 fails to launch with custom-config - permission denied #63

@jmkgreen

Description

@jmkgreen

In order to switch-off x-pack components (https://www.elastic.co/guide/en/x-pack/current/installing-xpack.html) I have supplied my own kibana.yaml file and provided the following 'CMD' instruction via a docker-compose.yaml file:

kibana -c /usr/share/kibana/kibana-5.yaml

On launch, I now get the following:

"type":"log","@timestamp":"2016-11-14T14:58:13Z","tags":["fatal"],"pid":13,"level":"fatal","message":"EACCES: permission denied, open '/usr/share/kibana/optimize/bundles/monitoring.entry.js'","error":{"message":"EACCES: permission denied, open '/usr/share/kibana/optimize/bundles/monitoring.entry.js'","name":"Error","stack":"Error: EACCES: permission denied, open '/usr/share/kibana/optimize/bundles/monitoring.entry.js'\n    at Error (native)","code":"EACCES"}}

Presumably something to do with the permissions run when the start-up script does not get run with kibana as the only argument?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions