Create base container image with MSMQ-Server
The MSMQ-Server role is a prerequisite for Particular NServiceBus installation. As NServiceBus handlers are potentially a good fit for containerization, it was disappointing to find that it is not possible to install MSMQ-Server in a container. Please create a base image with this support!
Chris Kingsley
shared this idea
19 comments
-
Ken Schlobohm
commented
New location for the blog related to this fix:
https://techcommunity.microsoft.com/t5/containers/a-smaller-windows-server-core-container-with-better-application/ba-p/382412 -
Pete
commented
its a shame that msmq-multicasting is not available - showstopper for me to containerise my apps.
-
Anonymous
commented
This have been generally available on Windows Server, version 1803 since May.
-
Anonymous
commented
Any word on when this will be generally available?
-
Weijuan Shi Davis
commented
Thanks Shahid. Yes indeed, in the latest Server Insider build, MSMQ now can install on a Server Core container build. Please go ahead and give it try. Let us know if this works for your use case. Thanks.
Here is the Server Core container insider build:
https://hub.docker.com/r/microsoft/windowsservercore-insider/Here is a blog related to this fix and other ones:
https://blogs.technet.microsoft.com/virtualization/2018/01/22/a-smaller-windows-server-core-container-with-better-application-compatibility/ -
Shahid Iqbal
commented
As this user voice hasnt been updated people might be interested to know the latest insiders build now supports msmq!
https://blogs.technet.microsoft.com/virtualization/2018/01/22/a-smaller-windows-server-core-container-with-better-application-compatibility/ -
Anonymous
commented
any updates?
-
Shahid Iqbal
commented
Even if you're not trying to run local queues it would seem you need to have the feature installed to access remote queues so this would be a significant barrier to a lot of enterprise apps which use MSMQ they are basically completely blocked from containers without some kind of re-write
-
Myles
commented
Hi everyone,
I hate to be the bearer of bad news, but an MSMQ-Server container image is not an easy thing to do.
It's quite unlikely we or the MSMQ team will be able to take on this work.
I know this is discouraging and frustrating, but I do want you to know we seriously do care and listen to your ideas. A great deal of our product development is solutions for problems or ideas you bring to us.
However, we can't build everything you ask for and this is one of those cases.
We're bummed too.
See the forum for a more full answer
https://social.msdn.microsoft.com/Forums/en-US/bce99a7d-aa60-44fa-a348-450855650810/msmqserver-is-it-supported?forum=windowscontainers -
Yuriy Zaletskyy
commented
Any plans on when msmq will become available in docker?
-
Anonymous
commented
We use transactions, but everything is local (no cross-container support from us)
-
Ross
commented
We use MSMQ in an old-school but massive asp.Net app. We are using MSMQ for simple queuing services, and we chose MSMQ because it is reliable and robust. We require no cross-queue operations, distributed queues, or SQL Server support.
Without MSMQ we must re-implement our queuing model using SQL Server, and unattractive prospect.
-
Adam
commented
We also use NServiceBus on a fairly large on-prem app. This is also currently stopping us from using containers.
-
Gary
commented
Not only nservicebus. Wcf uses them too.
-
Yuriy
commented
For my team ~700 people this is a big stopper
-
Anonymous
commented
That is a show stopper for us. Without this we cannot use docker container as our website requires MSMQ
-
wauk hill
commented
most of our services rely on msmq and there is no way forward without a container that can run msmq.So I cant use docker for now.
-
Anonymous
commented
Having the MSMQ feature available in windows containers will also make automated testing significantly easier. At present you have to spin a virtual machine to test anything MSMQ/DTC related.
-
Ross Beehler
commented
Note that NServiceBus also relies on MSDTC by default, so that would also make sense to include alongside MSMQ. Also, I'm sure there are other missing features, such as a manageable way to map endpoints across container boundaries, as I'm under the impression the networking abstractions are quite limited and clunky with Windows Containers at this point.