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
This is apparently new, but under macOS I'm getting something like this:
./scripts/logs
Name Command State Ports
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
...
ERROR: Couldn't connect to Docker daemon. You might need to start Docker for Mac.
Running docker-compose manually works fine. There's probably some environment variable that isn't getting set in the ocntext of the control script.
The text was updated successfully, but these errors were encountered:
mmguero
added
bug
Something isn't working
docker
Relating to docker and docker-compose as used by Malcolm
macOS
Related to running Malcolm under macOS
labels
Aug 19, 2020
* Carved file scanning improvements
* Multiple file scanners can now be enabled concurrently (previously only one at a time was allowed)
* [Yara](https://github.com/VirusTotal/yara) [added](idaholab#148) as carved file scanner feeding signatures.log with [Florian Roth](https://github.com/Neo23x0)'s [Signature-Base](https://github.com/Neo23x0/signature-base) Yara ruleset enabled by default and the ability to provide other yara signatures under `yara/rules` under the Malcolm directory (see #148 and #14)
* Bumped versions
* Moloch [v2.4.0](https://github.com/aol/moloch/blob/v2.4.0/CHANGELOG#L21-L42)
* Bug fixes
* #150 docker-compose having issues with start and logs under macOS
* Hedgehog was missing new environment variables for finer control of Zeek local policy behavior
* miscellaneous tweaks to Docker and ISO images (mainly for file size)
This is apparently new, but under macOS I'm getting something like this:
Running docker-compose manually works fine. There's probably some environment variable that isn't getting set in the ocntext of the control script.
The text was updated successfully, but these errors were encountered: