Bug: Bloodhound-setup fails when run in a docker container #2192
Description
Description:
Attempting to setup a customer kali docker container with bloodhound installed fails. This use case is needed for configuring a custom image for a closed environment.
Are you intending to fix this bug?
Yes
Component(s) Affected:
- bloodhound-setup
Steps to Reproduce:
- Shell into a kali container:
docker run -it kalilinux/kalilinux-rolling /bin/bash
- Install bloodhound and systemd using apt
apt-get update -y && apt-get install bloodhound systemd -y
- Attempt to run bloodhound-setup
bloodhound-setup
- You will see the following error:
[*] Starting PostgreSQL service
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to system scope bus via local transport: Host is down
I believe the root cause of this is that systemd cannot be used within a containerized environment. Perhaps using an alternate way to launching PSQL might work?
Expected Behavior:
To start PSQL and Neo4j correctly when in a containerized environment.
Actual Behavior:
Bloodhound-setup fails to configure required services.
Screenshots/Code Snippets/Sample Files:
N/A
Environment Information:
BloodHound: Unsure (Keeps displaying setup with no support for a version flag)
OS: Kali GNU/Linux Rolling 2025.4
Docker (if using Docker): Client 27.5.1+dfsg4 / API 1.47
Additional Information:
N/A
Potential Solution (optional):
Add some environment checks to detect when run in a containerized environment, then use CLI commands instead of systemd to setup and launch required services.
Related Issues:
N/A
Contributor Checklist:
- I have searched the issue tracker to ensure this bug hasn't been reported before or is not already being addressed.
- I have provided clear steps to reproduce the issue.
- I have included relevant environment information details.