Docker on Windows Server 2016 Technical Preview 5
blog.docker.com
Docker on Windows Server 2016 Technical Preview 5
1–10 of 44 posts
Re: Docker on Windows Server 2016 Technical Preview 5
#2What about licensing? Does the docker image manifest include machine-readable licensing metadata required for automated licence compliance verification?
Re: Docker on Windows Server 2016 Technical Preview 5
#3If this starts utilizing the "Ubuntu on Windows"[0], I think, with minor modifications, most of the images should already work; which is great. I can't wait to see how containerization (and tools built for orchestration of those) will evolve in the coming years to help dev/devops.
[0]: https://insights.ubuntu.com/2016/03/30/ubuntu-on-windows-the...
Re: Docker on Windows Server 2016 Technical Preview 5
#4What about licensing? Does the docker image manifest include machine-readable licensing metadata required for automated licence compliance verification?
That was my first thought, too. At first sight, Windows containers seem to run only on Windows hosts.
Maybe the licensing is covered through the hosts' licencse (speculation: you can run n Windows containers if you buy license x for the host OS).
Re: Docker on Windows Server 2016 Technical Preview 5
#5The only drawback of the current onslaught of Microsoft activity is the fact that most "enterprise" businesses and software products are completely unprepared or unwilling to move in step.
As an integrator, I've barely started seeing Win2012 in production last year, so it will be another 5 years before I can start playing with these new toys. Hell, some people are still chugging along with 2003sp2... and I'm talking Big Business, not some godforsaken countryside school.
Re: Docker on Windows Server 2016 Technical Preview 5
#6The only drawback of the current onslaught of Microsoft activity is the fact that most "enterprise" businesses and software products are completely unprepared or unwilling to move in step. As an integrator, I've barely started seeing Win2012 in production last year, so it will be another 5 years before I can start playing with these new toys. Hell, some people are still chugging along with 2003sp2... and I'm talking…
And one might argue they are taking the sane approach to the upgrade treadmill. It's easy to forget technology is supposed to solve real problems and that there's no economic incentive to use new toys to solve already solved problems, possibly introducing new issues with less well-known solutions.
The fact businesses are extending the life of systems not because they are unwilling to invest in upgrades but because they work just fine is a sign that the industry has reached a good level of maturity. It's a good thing. We should all be working collectively to solve new problems instead of reiterating over the same problems again and again.
In the old days of NT4 a 4-year old system would accumulate maintenance costs. Today, Windows 2003 is 13 years old and still pretty serviceable.
I'd be more worried about businesses accumulating unsustainable technical debt than accumulating old (but stable) technologies.
Re: Docker on Windows Server 2016 Technical Preview 5
#7The only drawback of the current onslaught of Microsoft activity is the fact that most "enterprise" businesses and software products are completely unprepared or unwilling to move in step. As an integrator, I've barely started seeing Win2012 in production last year, so it will be another 5 years before I can start playing with these new toys. Hell, some people are still chugging along with 2003sp2... and I'm talking…
I don't see how this is a drawback. Maybe not 5 years but this stuff is still cutting edge, untested and unproven. Do you really want to use this kind of stuff in production when most of the issues haven't even been found yet let alone fixed ? No best practices, no other people mistakes to learn from ? Maybe tomorrow Microsoft decides it wasn't such a good idea and starts moving away from with (TBH they are better than most in this regard but still).
Re: Docker on Windows Server 2016 Technical Preview 5
#8What about licensing? Does the docker image manifest include machine-readable licensing metadata required for automated licence compliance verification?
The main windows server 2016 page has pretty clear guidance on this[0]:
---
OSEs/Hyper-V containers
DataCenter: Unlimited
Standard: 2
----
Windows Server containers
Datacenter: Unlimited
Standard: Unlimited
---
[0] - https://www.microsoft.com/en-us/server-cloud/products/window...
Re: Docker on Windows Server 2016 Technical Preview 5
#9What about licensing? Does the docker image manifest include machine-readable licensing metadata required for automated licence compliance verification?
That was my first thought, too. At first sight, Windows containers seem to run only on Windows hosts. Maybe the licensing is covered through the hosts' licencse (speculation: you can run n Windows containers if you buy license x for the host OS).
> you can run n Windows containers if you buy license x for the host OS
Licenses for Windows Server generally convey some rights for virtualization. https://hyperv.veeam.com/blog/virtualization-rights-windows-...
Re: Docker on Windows Server 2016 Technical Preview 5
#10The only drawback of the current onslaught of Microsoft activity is the fact that most "enterprise" businesses and software products are completely unprepared or unwilling to move in step. As an integrator, I've barely started seeing Win2012 in production last year, so it will be another 5 years before I can start playing with these new toys. Hell, some people are still chugging along with 2003sp2... and I'm talking…
And one might argue they are taking the sane approach to the upgrade treadmill. It's easy to forget technology is supposed to solve real problems and that there's no economic incentive to use new toys to solve already solved problems, possibly introducing new issues with less well-known solutions. The fact businesses are extending the life of systems not because they are unwilling to invest in upgrades but because th…
I absolutely agree! I guess my complaint is that MS is developing all this new stuff with no regards for the installed userbase -- they are all add-ons for Windows 10 and 2016 Server, rather than standalone cross-version apps that could be deployed sooner on existing infrastructure. It's obviously easier for them, but it means "normal people" will not be able to enjoy most of these advances for a very long time.