[
https://issues.apache.org/jira/browse/METRON-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15768069#comment-15768069
]
ASF GitHub Bot commented on METRON-622:
---------------------------------------
Github user kylerichardson commented on the issue:
https://github.com/apache/incubator-metron/pull/393
Thanks for the explanation @merrimanr. I totally agree on the need for the
local IDE to have access to the containerized services. It's an easy enough
fix for me to manipulate the DOCKER_HOST env variable on Fedora and avoid
using docker-machine (although, I do see that as a big win for ease of use
on Mac and Windows).
I haven't had much luck with vagrant myself so am super excited for a
docker alternative to quick dev. As an aside, there are some Ansible
modules for docker (
https://docs.ansible.com/ansible/list_of_cloud_modules.html#docker) that we
could look into for incorporating some of the setup scripts and image
building to make it even more user friendly. Might just be a low priority
nice to have but thought I'd throw it out there.
On Mon, Dec 19, 2016 at 4:32 PM, merrimanr <[email protected]> wrote:
> @kylerichardson <https://github.com/kylerichardson> thank you for
> reviewing it! I updated the documentation to include Docker for Mac or
> Docker for Windows. One of the primary requirements for the way I use this
> is that containers must be accessible from my local environment where my
> IDE is running so services that broadcast their host address are tricky.
> The Kafka advertised listener thing was the single most challenging issue
I
> faced so not surprised you hit it too. The Kafka Dockerfile is wired to
> pull the DOCKER_HOST from an input argument and the compose file is wired
> to pass the local DOCKER_HOST environment variable as the DOCKER_HOST
input
> argument to the Kafka Dockerfile. So you should be able to set your local
> DOCKER_HOST environment variable as such:
>
> $ export DOCKER_HOST="tcp://:2376"
>
> When you run "eval $(docker-machine env metron-machine)" that's pretty
> much what Docker Machine is doing, setting local environment variables to
> match the desired host. Then after you build the environment, the
> advertised.listener property should be set to without you having to
> manually change it.
>
> I only used the virtualbox drive because that's what came out of the box.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
>
<https://github.com/apache/incubator-metron/pull/393#issuecomment-268084862>,
> or mute the thread
>
<https://github.com/notifications/unsubscribe-auth/AJ6R3a4JoffRcq9etOoUAJExjJAeue-aks5rJvf_gaJpZM4LJZHT>
> .
>
> 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)
