The latest release of Docker Enterprise Edition (EE) allows organizations to modernize Windows, Linux, and Linux-on-mainframe applications—all with minimal disruption. The release also allows organizations to run containers at scale with advanced capabilities around secure multi-tenancy and policy-based automation.
In last week’s webinar, we walked through the key new features of this release and saw a demo of Docker EE in action. If you missed the webinar, you can watch it here:
Here are the top questions from the webinar:
Q: Can you provide more information about Windows support? Which version of Windows? Is this only available with Docker Enterprise Edition?
A: You can run Windows Docker containers either with Docker Community Edition for Windows (PC) which supports Windows 10 or Docker Enterprise Edition for Windows Server 2016 (including Nano Server). Docker EE Basic is included with the Windows Server 2016 license, and you also have the option to upgrade to EE Standard or EE Advanced for Windows Server 2016 to get complete lifecycle management capabilities, Docker Trusted Registry, and advanced security features like image signing and scanning.
Q: Is it possible to deploy the Windows containers on top of a native Linux host?
A: As a form of packaging an application, you can only deploy Windows containers on a Windows host as the application will need to access the underlying OS kernel and in this case, it would be a Windows OS kernel. With this release, it is possible to manage a Docker EE cluster that contains both Windows and Linux nodes as well as Linux on IBM Z nodes.
Q: Does Docker EE support legacy Windows applications?
A: The Docker engine runtime only works on Windows 10 and Windows Server 2016, but containerized Windows applications built on older stacks will still work as long as it is based on the same underlying kernel. As an example, .NET is backwards compatible allowing you to containerize a .NET 2.0 application. In the Linux world, the equivalent is running Ubuntu-based apps and RHEL-based apps on the same Docker host because it leverages the same underlying Linux kernel.
Q: Does image scanning look for known CVEs? Or do we have to provide scripts? Is that feature available in all plans?
A: Image scanning looks at the NIST CVE database of known vulnerabilities, but you can also add your own inputs from a .TAR file. Image scanning is available in Docker EE Advanced and does work for both Windows and Linux images.
Q: Is it recommended to run Dockerized e-commerce applications in production?
A: Many of our customers leverage Docker for production e-commerce apps. Docker works very well with Java and .NET/IIS apps.
Q: How many containers can run on a single Docker host?
A: It depends on a number of factors. It will depend on if you’re running bare metal or in a virtual machine, what resources are available (CPU/memory) and the size of the containers. If you’re dealing with larger monolithic apps or microservices, the size of your containers can vary greatly.
Q: The use case of modernizing traditional apps – does that mean rewriting the application or just containerizing the application as it is? If the latter, wouldn’t that go against the “theoretical” best practices of keeping containers small?
A: Docker supports the containerizing of applications as they are, meaning you can containerize a monolithic application without reworking the code. While the resulting container may be larger than a microservice, it will still receive some of the same benefits in terms of portability, easier maintenance and faster deployments. Organizations can also see significant cost savings from decreased infrastructure requirements. You can learn more about the core benefits of this by signing up here: https://www.docker.com/mta
Dive Deeper with Docker Enterprise Edition: