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
Hello @RRcwhiting - Thank you for posting the issue. We have identified an issue with order of container start up on system reboot, and will have an update issued for this shortly. We will post the updates here. Thanks !
Describe the bug
deepfence threatmapper's compose mode doesn't handle reboots very gracefully.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
system should handle system restarts.
Components/Services affected
Additional context
some instructions about AWS linux were incorrect for being temporary. that doesn't seem to be the final bug.
the edit should be in /etc/sysctl.conf to be permanent - https://www.elastic.co/guide/en/elasticsearch/reference/current/vm-max-map-count.html
The text was updated successfully, but these errors were encountered: