You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Docker exit code 137 means insufficient memory was supplied for the container to function. If you'd like to provide additional information such as fuller logs or system details we can take a look, but generally it means more resources (memory) are required.
Description:
cant login new instance. bloodhound crashes.
bloodhound-1 exited with code 137
Component(s) Affected:
Steps to Reproduce:
setup new instance,
docker compose up
then using password supplied andadmin
as username it fails and then I get error blooodhound exitExpected Behavior:
A description of what you expected to happen.
Actual Behavior:
A description of what actually happened.
Screenshots/Code Snippets/Sample Files:
If applicable, add screenshots, relevant code snippets, or sample files that help illustrate the issue.
Environment Information:
BloodHound: [BloodHound version or revision]
Collector: [SharpHound version / AzureHound version]
OS: Ubuntu ARM
Browser (if UI related): [browser name and version]
Node.js (if UI related: [Node.js version]
Go (if API related): [Go version]
Database (if persistence related): [Neo4j version / PostgreSQL version]
Docker (if using Docker): [docker version]
Additional Information:
Any additional context or information that might be helpful in understanding and diagnosing the issue.
Potential Solution (Optional):
If you have any ideas about what might be causing the issue or how it could be fixed, you can share them here.
Related Issues:
If you've found related issues in the project's issue tracker, mention them here.
Contributor Checklist:
The text was updated successfully, but these errors were encountered: