microsoft / microsoft/Windows-Containers
Howto?: MSMQ in container with persistent volume
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 551
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
Description
In this article https://techcommunity.microsoft.com/blog/containers/msmq-and-windows-containers/1981414
you desrcribe that you tested private transactional queues with persistent volume over 2 containers. Can you please provide some samples for this setup? I'll always get errors when I try to mount a volume at C:\windows\system32\msmq\storage
The Message Queuing service cannot start. The internal private queue 'admin_queue$' cannot be initialized. If the problem persists, reinstall Message Queuing. Error 0xc00e0001:
(From eventlog)
I'll try to isolate the message queue system from the message read and publish pipeline. We wan't to migrate a legacy system into containers.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the linked MSMQ and Windows Containers article, then investigate the reported C:\windows\system32\msmq\storage mount and the 0xc00e0001 startup error. Done means providing reproducible samples for private transactional queues with persistent volumes across two containers and documenting the expected setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, documentation, operating-systems
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100