search

belane / docker-bloodhound

BloodHound Docker Ready to Use
86 stars 34 forks source link

belane/bloodhound under unRAID #12

Open servebeer opened 1 year ago

servebeer commented 1 year ago

I just finished building out the belane/bloudhound image on my unRAID server. The container is all set as well as the image. It connects to neo4j w/o any issues. However it always ends with this error: "/opt/run.sh: line 6: 262 Segmentation fault /opt/BloodHound-linux-x64/BloodHound --no-sandbox 2> /dev/null"

Any ideas on how I can fix this?

v/r Jon

belane commented 1 year ago

Run docker run with --shm-size=1g argument to see if it fixes the problem.

If not, replace /opt/BloodHound-linux-x64/BloodHound --no-sandbox 2> /dev/null with ELECTRON_ENABLE_LOGGING=true /opt/BloodHound-linux-x64/BloodHound --no-sandbox to see the debug log.

servebeer commented 1 year ago

No joy...

docker run --shm-size=1g 7d4d2698c967

Selecting JVM - Version:11.0.16+8-post-Debian-1deb11u1, Name:OpenJDK 64-Bit Server VM, Vendor:Debian Changed password for user 'neo4j'. IMPORTANT: this change will only take effect if performed before the database is started for the first time. Directories in use: home: /var/lib/neo4j config: /etc/neo4j logs: /var/log/neo4j plugins: /var/lib/neo4j/plugins import: /var/lib/neo4j/import data: /var/lib/neo4j/data certificates: /var/lib/neo4j/certificates licenses: /var/lib/neo4j/licenses run: /var/lib/neo4j/run Starting Neo4j. Started neo4j (pid:151). It is available at http://localhost:7474 There may be a short delay until the server is ready. Log in with bolt://127.0.0.1:7687 (neo4j:blood) /opt/run.sh: line 6: 246 Aborted /opt/BloodHound-linux-x64/BloodHound --no-sandbox 2> /dev/null

I'll go ahead and try an get a log dump.

servebeer commented 1 year ago

I believe the problem might be that Docker, under unRAID, do not support the --no-sandbox switch

servebeer commented 1 year ago

One last post today. It appears that unRAID handles Docker a little differently. Their preferred way of installing Docker images is from their App Store. That being said, I have gotten images to run under unRAID, who did not have App Store packages. I have mostly done it by using Portainer. I am very new to Docker, so I am probably messing this up myself. Can you tell me how to implement your original commands via Portainer?

belane commented 1 year ago

Sorry but I don't know Portainer, can you try the second option and paste the log here?

If not, replace /opt/BloodHound-linux-x64/BloodHound --no-sandbox 2> /dev/null with ELECTRON_ENABLE_LOGGING=true /opt/BloodHound-linux-x64/BloodHound --no-sandbox to see the debug log.

DukeSavage commented 1 year ago

Has this issue been resolved yet? I am encountering the same thing.

servebeer commented 1 year ago

I have been away on bushiness, but I am back now and will take another stab at it this weekend.

belane commented 1 year ago

@servebeer @DukeSavage I've created a debug Dockerfile that will print errors to the console so we can figure out the source of the problem. Check the instructions here https://github.com/belane/docker-bloodhound/issues/8#issuecomment-1582683455 .