Re: Running Pyro (nameserver for now) in a Docker container

Giovanni Porcari <giovanni.porcari@...> writes:

> > Il giorno 16/lug/2014, alle ore 19:50, Steven Pav
> <shabbychef@...> ha scritto:

[snip] 

> > in a docker container. However, I am unable to locate the nameserver 
once it 
> > is running. I believe this might be related to some of the issues noted 
in 
> > this post: http://comments.gmane.org/gmane.comp.python.pyro/2490 , 
namely 
> > that the nameserver running within the docker container has funny ideas 
about 
> > the name of the localhost, or what port it should be listening on, etc. 
> > 
> > As a MWE, I have posted the Dockerfile and some shell code to run it 
here: 
> > https://gist.github.com/shabbychef/72657f769eba7ddeed9d . 

[snip]
 
> i am a pyro4 user and also a docker user. I never used nameserver but i 
suppose
> that the container should have UDP enabled and maybe you should also 
expose
> also the broadcast server port.
> 
> I think that it is more a docker configuration problem than a pyro one.
> 
> Using docker i use unix-socket for pyro and it works very well. 

Thanks for the reply, and I suspect you are right. I have tried to specify 
'--bcport=6433' to the nameserver running in the container, and run the 
container with -p 0.0.0.0:6433:6433/udp . Nevertheless, I cannot access the 
nameserver. I am not as familiar with the unix socket approach. Could you 
elaborate on how that would work? For the nameserver, it seems clear that 
one would use
--unixsocket=UNIXSOCKET
However, I am not sure how to create the socket and how to connect it 
between the container and host. Any help appreciated,



------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds