Installing Reliable Multicast Protocol (PGM) into windowsservercore image RRS feed

  • Question

  • Hi.

    Is there a way to install Reliable Multicast Protocol (PGM) into windows container image based on windowsservercore image, using a command in my Dockerfile.

    I created a transparent network in Docker based on my physical Ethernet adapter that has installed reliable multicast protocol, and properties of my transparent network show that it also has reliable multicast protocol installed. But trying to create a PGM socket in my docker container I get the message 'The support for the specified socket type does not exist in this address family.'.



    Tuesday, May 15, 2018 3:13 PM

All replies

  • Greetings,

    Sorry for the delay response.

    It's an open issue in github.

    I hope the discussions in that issue can help you a little.

    Sic Parvis Magna

    Saturday, May 19, 2018 10:56 AM
  • Thanks for the response.

    After reading this GitHub issue, I think it's not relevant to my problem, since I am not using overlay networks.

    I just want to install reliable multicast protocol in my docker image running locally.

    What I found in the meantime is that there is a command line utility that can be used for my purpose like this

    netcfg -c p -i ms_rmcast

    But this command also fails with this error:

     ... failed. Error code: 0x800106d9.


    Monday, May 21, 2018 3:29 PM
  • Greetings,

    I just found an old doc.

    In that doc, "PGM is only supported when Microsoft Message Queuing (MSMQ) 3.0 is installed" gives me a hint.

    In Windows Server, version 1803, Microsoft Message Queuing (MSMQ) now installs in a Server Core container.

    Do you have a chance to try Windows Server, version 1803?

    Sic Parvis Magna

    Tuesday, May 22, 2018 1:22 AM
  • I doubt that PGM relies on Message Queuing, since we have been using it for years without Message Queuing installed.

    I tried you suggestion anyway, but I'm not able to build my docker image at all. I get the following error:

    docker build -t asynciotest .\
    Sending build context to Docker daemon  23.12MB
    Step 1/8 : FROM microsoft/windowsservercore:1803
    1803: Pulling from microsoft/windowsservercore
    d9e8b01179bf: Extracting [==================================================>]   1.66GB/1.66GB
    65a09b62c235: Download complete
    failed to register layer: re-exec error: exit status 1: output: ProcessUtilityVMImage \\?\C:\ProgramData\Docker\windowsf
    ilter\4cd27891cd179fba7e496c5e9bfab5c61d802b268caacb3d56a3ebfe63379397\UtilityVM: The system cannot find the path specified.

    Thursday, May 24, 2018 3:24 PM
  • It should be used with Windows Server, version 1803 host OS together.

    Sic Parvis Magna

    Saturday, May 26, 2018 11:03 PM
  • Where can I find Windows Server version 1803?

    The machine I am building my docker image is:

    OS Name Microsoft Windows Server 2016 Standard
    Version 10.0.14393 Build 14393

    Thursday, May 31, 2018 3:44 PM
  • Sorry for the delay response.

    If you have a MSDN subscription, you can download Windows Server, version 1803.

    Also, you can try it via Azure.

    Sic Parvis Magna

    Tuesday, June 5, 2018 1:25 AM