activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Tully <gary.tu...@gmail.com>
Subject Re: Activemq on Docker
Date Tue, 20 May 2014 11:01:18 GMT
peek at https://issues.apache.org/jira/browse/AMQ-3864 - there is
publishedAddressPolicy element on a transport connector that will
accept an IPADRESS strategy since 5.8

On 18 May 2014 02:50, Noel OConnor <noel.oconnor@gmail.com> wrote:
> Thanks Sonica,
> I'll try this and see how it goes.
>
> Multicast would have been easier and I'm still wondering why the multicast
> payload contains hostnames rather than ip addresses it seems like a
> limitation but there may be a good reason for it. Any idea ?
>
> cheers
> Noel
>
>
> On Sat, May 17, 2014 at 4:43 PM, sonica <sonicaaaa@gmail.com> wrote:
>
>> HI Noel, is Docker"Link hostnames" an option for you?
>>
>> With Docker 1.11
>>
>> running your container with this syntax
>>
>> docker run -i -t --name this_container --link other_container:
>> other_container any_image
>>
>> Is supposed to inject for you an entry in "this_container" /etc/hosts
>> pointing to the dynamic ip of "other_container".
>>
>> see:
>>
>> http://blog.docker.io/2014/05/docker-0-11-release-candidate-for-1-0/
>>
>>
>> On Sat, May 17, 2014 at 6:15 AM, Noel OConnor <noel.oconnor@gmail.com
>> >wrote:
>>
>> > Hi,
>> > I'm trying to get activemq working on a Docker container. I've got the
>> > basic install going and I'm now trying to configure multicast discovery
>> so
>> > that multiple containers can be connected together.
>> > I've turned on the multicast discovery and the containers are trying to
>> > connect.
>> > However the two activemq instances cannot create a network bridge as the
>> > multicast discovery protocol passes the hostname of the activemq instance
>> > rather than the ip address. The other container cannot resolve the passed
>> > hostname and the bridge fails.
>> >
>> > I've seen a number of posts around this and the general response that I
>> can
>> > see is "sort out your DNS setting or edit the /etc/hosts file". This
>> > doesn't really help in a dynamic environment such as a docker container.
>> >
>> > I was wondering if there was a workaround for this i.e. turning off DNS
>> > hostname resolution ?
>> >
>> > thanks for your help
>> > Noel
>> >
>>



-- 
http://redhat.com
http://blog.garytully.com

Mime
View raw message