-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kibana 7.14.0 bug Error response from daemon: OCI runtime create failed: #109064
Comments
Pinging @elastic/kibana-operations (Team:Operations) |
Can you share a little bit more info about your setup? Are you using the default docker image? |
Used image url is :https://hub.docker.com/layers/kibana/library/kibana/7.14.0/images/sha256-4826c5665c879272cb0fedb4e654d45dc16666b4f8df9c0850c511166acfb342?context=explore |
I tried to reproduce this and was able to start the service on arm64. My config looked like this:
When I changed the bind source to a path that didn't exist - I was able to reproduce the issue. Can you verify that the user running docker has read access to kibana.yml? |
@zhujunjieit, that image is not provided by us. Please use those provided at https://www.docker.elastic.co/. Since this appears to be a Docker CLI issue, and not caused by the Kibana Docker Image I am going to close this issue. If you have questions or need help, please post to https://discuss.elastic.co/c/kibana. |
system in centos7.9:
error:
docker: Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: rootfs_linux.go:76: mounting "/rkhome/soft/conf/kibana.yml" to rootfs at "/usr/share/kibana/config/kibana.yml" caused: mount through procfd: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type.
Provide logs (if relevant):
The text was updated successfully, but these errors were encountered: