[
https://issues.apache.org/jira/browse/METRON-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15805763#comment-15805763
]
ASF GitHub Bot commented on METRON-622:
---------------------------------------
Github user merrimanr commented on the issue:
https://github.com/apache/incubator-metron/pull/393
I usually just leave it up. My current environment has been running for 2
weeks with no problem. The intention behind creating a Metron-specific machine
is that it won't conflict with other Docker machines someone may be using (or
if people are using the default machine, which I would guess is most common).
Not sure how yours went down but sometimes that happens. Would adding a
note in the "Setup" section of the README to make sure machine is running do it
(right before the eval command)? I could also add quick instructions on how to
stop/start a machine.
> Create a Metron Docker Compose application
> -------------------------------------------
>
> Key: METRON-622
> URL: https://issues.apache.org/jira/browse/METRON-622
> Project: Metron
> Issue Type: New Feature
> Reporter: Ryan Merriman
>
> This is an alternative to the Vagrant quick-dev approach of creating a local
> Metron environment for development and testing. It is intended to be leaner
> and easier to manage. This compose application will contain separate images
> for each of the services that Metron depends on as well as the Metron
> services.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
