This is the 3rd post in the Docker on Windows Server 2016 series. Refer back to the initial post for links to all posts in the series.
Microsoft or Docker… Which Is It?
So, not a lot has changed since my last post in this series. I’m still having issues getting my MSDN benefits straightened out because of how I’m currently configured for the Enterprise Agreement (EA) we have with Microsoft. Turns out that there might be some configuration issues with our EA so, once that’s straightened out, I should be really close to being able to make use of my company-sponsored Azure benefits.
In the meantime, I received a question from one of our operations team members along the lines of:
If we move forward with Docker on Windows Server , will Microsoft provide support under our Enterprise Agreement or do we get support from Docker?
Since I did not immediately know the answer, I forwarded the question to Microsoft and they let me know that our Enterprise Agreement would cover support for Docker on Windows Server 2016 and, if they needed to get Docker involved, they would do it on their end.
Great! I followed up with, “is this documented publically anywhere?” Turns out that: a) yes, it is and, b) I’ve been to that page multiple times but never noticed the part about support until now
If you go to Docker Enterprise Edition for Windows Server 2016 is in the Docker Store, look in the upper, right-hand corner and you should see something like this:
Docker EE for Windows Server is available at no additional cost to all Windows Server 2016 customers. Technical support is aligned to the Microsoft support entitlement and provided by Microsoft.
This was there the whole time and I just hadn’t noticed it.
Anyway, I’m hoping the next Docker update in this series will have some better news along the lines of us getting Docker working with a private registry using ACR. Until then, maybe this will answer the support question for someone else who didn’t happen to notice that above statement.
Until the next post…