Re: EPICS Docker Container

[Florian Feldbauer via Tech-talk <tech-talk@aps.anl.gov>]

Hi Jack,

normally I also use compose files. But for testing I used the docker run 
command directly.

Using the host network also works for me to use pvget from a remote 
host. But if I want to have multiple IOCs running on the same host and 
want to use CA and PVaccess in parallel, I guess using the host network 
is not a good idea. IIRC you would need to define individual CAS ports 
for each IOC and tell all your clients to also use those ports. 
Therefore I wanted to have the IOCs in a virtual (bridge) network and 
use a PVaccess gateway in the end.

I was not able to have host network together with a bridge network 
inside one compose file...

Best regards,
Florian

On 7/8/19 2:38 PM, Jack Harper - UKRI STFC wrote:
> Hi Florian,
>
>
> I see what you mean. Yes, i have only tried running pvget from inside the container and on the host machine.
>
>
> I have run it in host network mode and that seemed to work as well. I use a docker-compose file to do all the port matching so can't say what command line arguments would be best to use in your case, but using compose might be at least an option to set all the ports up instead of doing it every time when running the container? you can also use it to choose what type of network to run the container in.
>
>
> Jack
>
> ________________________________
> From: Florian Feldbauer <florian@ep1.ruhr-uni-bochum.de>
> Sent: 08 July 2019 13:27:01
> To: Harper, Jack (STFC,RAL,ISIS)
> Subject: Re: EPICS Docker Container
>
> Hey Jack,
>
> yes, I have exposed the ports in the Dockerfile. But it is not working
> for me.
>
> Did you tried `pvget` on the same host, as the container is running on?
> Than the network access happens via the virtual network of Docker.
>
> Running a docker container with no arguments means, the container is
> inside the default bridge network ( 172.17.0.0/16 ) and the host system
> is connected to this network as 172.17.0.1.
>
> This way pvget works for me. The problem is, accessing the IOC from a
> different PC in the physical network. In this case you have to
> explicitly publish the ports with the `-p` option of the docker run
> command.
>
> On 7/8/19 2:20 PM, Jack Harper - UKRI STFC via Tech-talk wrote:
> > Hi Florian,
> >
> > Have you exposed your ports in the Dockerfile correctly?
> >
> > I have just fixed this in one of the Dockerfiles i have been working on - here is the line that exposes the ports:
> >
> > EXPOSE 5064 5065 5064/udp 5075 5076 5075/tcp 5076/udp
> >
> > I had to be explicit that i was exposing 5075 as tcp and 5076 as udp - pv access would not work otherwise. I just run the container with no arguments and it seems to work.
> >
> > Hope this helps,
> > Jack Harper
> --
> Dr. Florian Feldbauer
>
> Ruhr-Universität Bochum
> Experimentalphysik I AG
> Universitätsstr. 150
> Fach-Nr. 125
> D-44801 Bochum
>
> Office: NB 2/134
> Phone:  (+49)234 / 32-23563
> Fax:    (+49)234 / 32-14170
> https://paluma.ruhr-uni-bochum.de
--
Dr. Florian Feldbauer

Ruhr-Universität Bochum
Experimentalphysik I AG
Universitätsstr. 150
Fach-Nr. 125
D-44801 Bochum

Office: NB 2/134
Phone:  (+49)234 / 32-23563
Fax:    (+49)234 / 32-14170
https://paluma.ruhr-uni-bochum.de