Skip to content
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

Exit status 14 from docker on bloodhound-cli install #5

Open
Adamkadaban opened this issue Feb 11, 2025 · 3 comments
Open

Exit status 14 from docker on bloodhound-cli install #5

Adamkadaban opened this issue Feb 11, 2025 · 3 comments

Comments

@Adamkadaban
Copy link

I'm having some trouble using bloodhound-cli. I have the docker compose plugin and script installed.

[+] Checking the status of Docker and the Compose plugin...
[+] Starting BloodHound environment installation
[+] Downloading the production YAML file from https://raw.githubusercontent.com/SpecterOps/BloodHound_CLI/refs/heads/main/docker-compose.yml...
[+] Downloading the development YAML file from https://raw.githubusercontent.com/SpecterOps/BloodHound_CLI/refs/heads/main/docker-compose.dev.yml...
open /home/adam/.local/bin/docker-compose.yml: no such file or directory
[-] Error from `docker`: exit status 14
2025/02/10 22:08:39 Error trying to build with docker-compose.yml: exit status 14

BloodHound-CLI ( v0.1.3, 31 Jan 2025 )

Linux adam 6.1.0-29-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.123-1 (2025-01-02) x86_64 GNU/Linux

Docker version 20.10.24+dfsg1, build 297e128

docker-compose version 1.29.2, build unknown

@adityatelange
Copy link

Yeah the bin takes the location of directory where it is present rather than from where it is being executed from, current working directory. But docker-compose file is downloaded in current directory. Needs a fix

@adityatelange
Copy link

Also the docker logs look weird

Image

@Adamkadaban
Copy link
Author

Yeah the bin takes the location of directory where it is present rather than from where it is being executed from, current working directory. But docker-compose file is downloaded in current directory. Needs a fix

Ahhh, I should have noticed from the path in the error message. I'll just run in cwd from now. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants