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

docker-compose start kibana failed!--No such file or directory/usr/bin/env: bash #36

Closed
jacktang168 opened this Issue Jan 24, 2016 · 12 comments

Comments

Projects
None yet
6 participants
@jacktang168

jacktang168 commented Jan 24, 2016

I am use docker-machine on windows7 ,all of ELK can be up,but kibana,some error logs show for me:

$ docker-compose.exe up
dockerelk_elasticsearch_1 is up-to-date
Starting dockerelk_logstash_1
Creating dockerelk_kibana_1
Attaching to dockerelk_elasticsearch_1, dockerelk_logstash_1, dockerelk_kibana_1
: No such file or directory/usr/bin/env: bash

use docker logs , some errors show for me:

$ docker logs 0f4a58ad6b89
: No such file or directory
@shailesha

This comment has been minimized.

shailesha commented Feb 8, 2016

Hi,

I am also facing exactly the same issue. did you find the solution to this problem?

@rzijp

This comment has been minimized.

rzijp commented Feb 18, 2016

Ran into the same problem, and found a solution.
The issue is related to windows vs. UNIX line endings. According to this post it is best to change a git setting to not convert line endings (git config core.autocrlf false) before cloning onto a Windows environment. For me this trick didn't fix it though, but loading the kibana/entrypoint.sh file into an editor (notepad++) and converting to UNIX format worked.

@deviantony

This comment has been minimized.

Owner

deviantony commented Mar 15, 2016

I can't find what is the problem here, will leave the issue open as it seems that it affects multiple users. Could everyone precise its configuration (OS, docker version, compose version) ?

@rzijp

This comment has been minimized.

rzijp commented Mar 21, 2016

My impression is that the issue is not related to Docker at all, but has to do with git on windows only.

Here is my configuration:
Windows 7 Enterprise SP1

$ docker-machine.exe version
docker-machine.exe version 0.6.0, build e27fb87

$ docker version
Client:
 Version:      1.10.1
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   9e83765
 Built:        Thu Feb 11 19:14:21 2016
 OS/Arch:      windows/amd64

Server:
 Version:      1.10.1
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   9e83765
 Built:        Thu Feb 11 20:39:58 2016
 OS/Arch:      linux/amd64

@deviantony deviantony added the windows label Mar 21, 2016

@deviantony

This comment has been minimized.

Owner

deviantony commented Mar 21, 2016

So this issue seems related to Windows, thanks for pointing a solution @rzijp, I'll let this issue open for the other users who may have the same problem.

@jmkgreen

This comment has been minimized.

jmkgreen commented May 19, 2016

This should be documented in absence of a fix - I've just hit this on Windows 10.

@deviantony

This comment has been minimized.

Owner

deviantony commented May 19, 2016

@jmkgreen Did you tried the solution proposed by rzijp?

@jmkgreen

This comment has been minimized.

jmkgreen commented May 19, 2016

@deviantony yes, worked. I also had to docker-compose build before "upping" for the change to be recognised.

@swerfel

This comment has been minimized.

swerfel commented Aug 26, 2016

It was a good idea to let this issue open, it helped me a lot.
Here is the summary, because most people start reading from the last post:
This problem occurs because of line endings on windows. After a clone I

  • replaced all \r\n line endings with \n in ./kibana/entrypoint.sh with notepad++ (extended search and replace)
  • started docker-compose build to rebuild the kibana image again, before starting it with docker-compose up(-d)

(btw: thanks for this project)

@deviantony

This comment has been minimized.

Owner

deviantony commented Sep 25, 2016

Thanks to @matulko we may have a fix for this issue ! Could anybody here retry on Windows now to check if the problem still exists?

@swerfel

This comment has been minimized.

swerfel commented Oct 5, 2016

after clean clone and running docker-compose up no errors occure. Kibana site can be loaded. It looks like the issue is fixed! Thank you!

@deviantony

This comment has been minimized.

Owner

deviantony commented Oct 5, 2016

Perfect ! Thanks again to @matulko 🏆

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment