5 ms·

What about licensing? Does the docker image manifest include machine-readable licensing metadata required for automated licence compliance verification?

• sarnu 10y ago
  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).
  • taspeotis 10y ago
    > 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-server-2012-r2/ https://hyperv.veeam.com/blog/virtualization-rights-windows-...
• dsp1234 10y ago
  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/windows-server-2016/ https://www.microsoft.com/en-us/server-cloud/products/window...
  • terom 10y ago
    What about running Docker containers on desktop/laptop machines during development? It's a major part of the Docker usecase. Trying to keep track of Windows licensing compliance across multiple versions and deployment models is confusing enough as it is. Different sources will give different answers to the same questions when interpreting licensing scenarios, and you can never know unless you get audited (?)
    • justincormack 10y ago
      Currently Windows containers are only available on Server not on desktop at all, hence there is no licensing information available for desktop.
      • SteveLas 10y ago
        Windows Hyper-V Containers are available on the Windows 10 Client, through the insiders program. This is intended for development scenarios. You can run your Windows Containers locally, building up your app/service, then deploying on servers running the Container feature. We're still early in the Windows container development efforts. http://aka.ms/DockerToolsForVS http://aka.ms/DockerToolsForVS. The experience built for Linux containers will support Nano Server as well. In the current Windows insiders program, you can run Nano Server based containers locally, which you can develop .NET core apps against.
    • josteink 10y ago
      Traditionally, you've been allowed near anything for development and testing purposes using an MSDN subscription. I would assume that also applies to VMs or containers.
    • dsp1234 10y ago
      Different sources will give different answers to the same questions when interpreting licensing scenarios 1.) Containers are not available on desktop SKUs. So there is no licensing consideration for Windows 10. If they later add containers to Windows 10, then they'll release licensing rules at that time. 2.) If you are running a server OS for your desktop, then the licensing is pretty clear. Hyper-v VM containers follow the same rules as normal hyper-v VMs (1 physical + 2 virtual for standard then each additional VM requires a license, unlimited for datacenter). For Windows Server Containers (which are not hyper-v based), it's even easier, it's unlimited regardless of edition. 3.) As always, the host OS must be licensed fully in order to have the appropriate rights (2016 is moving to core licensing, with a minimum of 8 core licenses per processor, and a minimum of 2 processors). All in all, it's one of the easier features to understand the licensing for since it doesn't directly deal with CALs or internal/external usage rights.