invalid mount config for type "bind": bind source path does not exist #65
Comments
|
@perfecto25 I'm not sure what leads to this condition (I suspect it has something to do with the way docker-compose issues the mount command behind the scenes), but I was able to get this going by simply creating the directories, and then running |
|
@perfecto25 I'm curious if there's some permission errors going on and the process isn't able to create those keystores at the defined locations. |
|
I just got bit by the same issue. creating the auditbeat.keystore solved my problem. Thanks for posting that solution. |
|
I'm curious if the auditbeat service failing to start cause auditd isn't enabled for the kernel is breaking something in the whole process... |
|
I had the same issue and @fxdgear your solutions worked |
|
Same problem here, can't start the auditbeat container.
For the test, if I All other containers are up, no permission issue in the config folder.. |
|
Can you run auditbeat outside a container? |
|
I guess so... I've quickly did a test - installed auditbeat deb, and started the service. it's running. but haven't really tested thoroughly, @fxdgear please point me at specifics. |
|
@oori soo I've found that auditbeat can be kinda troublesome on linux. I personally run arch and I don't have auditd enabled and as a result auditbeat fails to start. Since this project is designed to be for "demo purposes" I consider not seeing audit beat data on my linux laptop ok cause I know that auditbeat won't run. I'd suggest maybe doing a clean up (containers, volumes, networks etc...) and trying again. |
|
Hopefully the referenced pull request clears up some of these issues. The setup script seems to hang for me, I suspect it should be doing more work past the output below. Environment:
|
|
@mjpowersjr I'm guessing that something failed to start in Elasticsearch. And what's happening is the setup for kibana and logstash are hung cause elasticsearch isn't up (or hasn't come up yet). If you like you can take a look at the referenced PR and give that a shot. Please note that the README has changed as well, so please read over that too. |
|
Looks like this issue has not been resolved in master branch. |
|
I'm getting the same issue as mjpowersjr Managed to get it working at some point but its hit or miss. Any idea when this can be resolved? |
docker-compose -f setup.yml up --> This helped me setup everything. Thank you! |
|
This is, Setup is dosent creating de .keystore in all diretorys. |
|
Dont work, just copy the keystore... This is a error inside the development... I choose to use a total source, without docker. |
|
I had an issue with this today. My problem was with autocrlf. I had cloned down the repo with autocrlf=true, and that caused the compose to hang and not create any of the keystores because of the new line characters in the shell scripts. When I set "git config core.autocrlf false" and re-cloned, then it started working for me. Edit: Forgot to mention, for the issue creator's original issue. The issue is with kernel 3.10 not knowing what "CAP_AUDIT_READ" is. Source: #14 |
Hello, having some issues bringing up the stack,
I ran the docker-compose -f setup.yaml up, the entire setup is done and gives me a password.
when I startup the entire thing, getting bind errors,
The text was updated successfully, but these errors were encountered: