Docker at Microsoft Ignite 2017

Docker will be at Microsoft Ignite in Orlando, FL the week of Sept 24th to showcase the latest release of Docker Enterprise Edition (EE) and the joint solutions with our partner Microsoft. Docker Enterprise Edition is the only platform available to secure and manage Linux and Windows containers in production.
In the Docker Booth #2127
Visit Docker in Booth #2127 for a #DockerSelfie, a chance for cool swag and to learn more about how Docker Enterprise Edition can help you save costs on legacy applications, accelerate your cloud strategy and uniformly secure and manage your Linux and Windows app landscape.
Register Here for daily in-booth talks or to schedule time to ask questions about containers and clouds on Linux and Windows Server.

Monday 3pm: Save $ on Legacy Apps with Docker
Tuesday 11am: Windows and Linux Together with Docker EE
Tuesday 3pm: Docker Enterprise Edition Demo
Wednesday 11am: Take Legacy .NET Apps to Azure with Docker
Thursday 11am: Docker Enterprise Edition Demo

Add these great sessions to your schedule
Container Fest on Sunday Sept 24th:
Docker will be on hand at the Container Fest Pre Day to discuss the possibilities of Docker Enterprise Edition for modernizing traditional Windows and Linux applications. Talks will feature Docker product specialists and the MetLife team sharing their journey on Docker EE and Azure. Register to save your seat.
BRK3322  Wednesday 2:15pm
Windows Server feature release: How to maximize developer efficiency today and tomorrow
Join this session to learn more about Windows Server and Docker Enterprise Edition and how they are used together in practice at Fox Interactive to leverage the latest capabilities in Windows Server and accelerate their cloud strategy without having to recode apps to get started.
BRK3214  Thursday 9:00am
Containers: From Infrastructure to Applications on Thursday 9am:
MetLife is a global provider of insurance for life, auto & home, dental, vision and more. Attend the session to hear how they approach infrastructure and applications with containers and cloud with Docker Enterprise Edition and Azure to transform 150 years of technology and customer data. 
Cisco Booth #735

Tuesday 2:45pm: Modernize Traditional Apps with Docker EE and Cisco UCS

Swing by for an in booth session about the Cisco and Docker program to Modernize Traditional Apps (MTA) to the latest UCS servers. This program uses Docker EE to containerize Linux and Windows applications to accelerate tech refresh, increase security and gain IT efficiency. Join Partner Integration Engineer, Uday Shetty on the combined benefit of Docker EE on UCS.

Tuesday 4:00pm: Container Q&A at the Cisco Genius Bar

Are you an MVP? Stop by for Coffee & Chocolate with Elton Stoneman
On Wednesday at 1pm in the Docker booth Elton Stoneman, Docker Developer Advocate and Microsoft MVP, will discuss the Docker technology and the new resources exclusively available to Microsoft MVPs. Sign up here for this session.
Docker Meetup on Tuesday 5:00pm
Free workshop: Deploying Multi-OS Applications with Docker EE
Full Sail University – Bldg 4D, Room 108  – 517 S Semoran Blvd, Winter Park, FL
Enter through door with large “D” and glass facade. Parking in front.
Bring your laptop, it’s workshop time! Mike Coleman and Elton Stoneman are helping to present a workshop on deploying Multi-OS Applications with Docker EE. This is your opportunity to learn how enterprises can manage a diverse set of applications that includes both traditional applications and microservices, built on Linux and Windows, and intended for x86 servers, mainframes, and public clouds. Save your seat!
Learn More:

Sign up for a Docker booth talk
Learn more about Docker and Microsoft
Visit IT Starts with Docker and sign up for ongoing alerts
Start a hosted trial
Sign up for upcoming webinars
Check out the video series: Modernize .NET Apps

Check out all the #Docker sessions and activities at #MSIngiteClick To Tweet

The post Docker at Microsoft Ignite 2017 appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

Preview: Linux Containers on Windows

Microsoft is getting ready for the next big update for Windows Server (check out today’s complimentary Microsoft blog post) and some of the new features are very exciting for Docker users. One of the most important enhancements is that Docker can now run Linux containers on Windows, using Hyper-V technology.
Running Docker Linux containers on Windows requires a minimal Linux kernel and userland to host the container processes. This is exactly what the LinuxKit toolkit was designed for: creating secure, lean and portable Linux subsystems that can provide Linux container functionality as a component of a container platform.
We’ve been busy prototyping LinuxKit support for Docker Linux containers on Windows and have a working preview for you to try. This is still a work in progress, and requires either the recently announced  “Windows Server Insider” or Windows 10 Insider builds.
 
Running Docker Linux Containers on Windows with LinuxKit
The instructions below have been tested on Windows 10 and Windows Server Insider builds 16278 and 16281.
Be sure to install Docker for Windows (Windows 10) or Docker Enterprise Edition (Windows Server Insider) before starting.

Setup Docker and LinuxKit
A preview build of  LinuxKit is available by simply running the following commands in PowerShell (with Administrator rights):
$progressPreference = ‘silentlyContinue’
mkdir “$Env:ProgramFilesLinux Containers”

Invoke-WebRequest -UseBasicParsing -OutFile linuxkit.zip <https://github.com/friism/linuxkit/releases/download/preview-1/linuxkit.zip<

Expand-Archive linuxkit.zip -DestinationPath “$Env:ProgramFilesLinux Containers.”
rm linuxkit.zip
Now get a master branch build of the Docker daemon that contains preview support for Linux containers on Windows:
Invoke-WebRequest -UseBasicParsing -OutFile dockerd.exe https://master.dockerproject.org/windows/x86_64/dockerd.exe
Start a new Docker daemon listening on a separate pipe and using a separate storage location from the default install:
$Env:LCOW_SUPPORTED=1
.dockerd.exe -D -H “npipe:////./pipe//docker_lcow” –data-root c:lcow
Try it
Run a Linux container:
docker -H “npipe:////./pipe//docker_lcow” run -ti busyboxbusybox@sha256:b82b5740006c1ab823596d2c07f081084ecdb32fd258072707b99f52a3cb8692 sh
Docker just launched a minimal VM running a LinuxKit instance hosting the Linux container!
Since this is an early preview there are some limitations, but basic Docker operations like pull and run work.

Looking ahead
Both Windows Server Insider builds and Docker support for Linux containers on Windows are in early preview mode. When GA, Docker Linux containers on Windows will improve the Docker Linux container experience for both Windows developers and server administrators. Developers will be able to more easily build and test mixed Windows/Linux Docker applications by running containers for both platforms side-by-side on the same system.
And IT-admins that prefer Windows will soon be able to easily run (mostly) Linux-only software like HAProxy and Redis on Windows systems by way of Docker Linux containers on Windows. For example, Docker Linux containers on Windows will make setting up Docker Enterprise Edition and Universal Control Plane (which relies on some Linux-only components) on Windows Server much simpler.
We hope this LinuxKit-based walkthrough will set you up to start experimenting. Feedback is always welcome! For general help and getting started with Insider builds use the Windows Feedback Hub (Windows 10), or the Windows Server Insiders Tech Community. For issues with LinuxKit and Docker support for Linux containers on Windows use the Docker for Windows issue tracker on GitHub. And let us know on Twitter if you build something cool!
 
More Resources:

Read the complimentary post about Linux Container on Windows on the Microsoft blog
Download Docker for Windows 10 and Docker for Windows Server
Learn more about Docker Enterprise Edition
Attend the Linux Container on Windows and LinuxKit sessions @DockerCon

Preview @Linux Containers on @Windows using #LinuxKit by @neugebar cc @MS_ITProClick To Tweet

The post Preview: Linux Containers on Windows appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

Docker Enterprise Edition for Linux on IBM Z (yes, mainframe!)

Recently we released a new version of Docker Enterprise Edition featuring expansion of the multi-architecture capabilities from Linux to Windows Server and now the IBM Z mainframe platform. Enterprise IT architecture is complex and diverse and include workloads across different server hardware types and operating systems.
Docker and IBM have partnered together to deliver the support for Red Hat Enterprise Linux, Ubuntu and SUSE Linux Enterprise Server for IBM Z (x390x) systems as certified infrastructure for Docker Enterprise Edition. This first release features support for the the IBM Z product family.
Why bring Docker containers and mainframe systems together? Enterprises across industries like financial services, government, manufacturing and more use mainframe systems for many high throughput applications. Many organizations recognize that these applications are at the core of their systems but rewriting and refactoring them for a different platform is expensive and time-consuming. By wrapping them in a container, organizations can make these applications easier to maintain and update while bringing them into the same software supply chain as other x86 applications
Multi-Architecture Support for Mainframe Systems
Docker Enterprise Edition allows for the same orchestration, security model, supply chain and integrated management that can be applied across a broader range of your application portfolio and drive IT operational efficiency.
Multi-architecture support means that a single cluster of worker nodes can include x86 Linux and Windows Server in addition to mainframe systems. Each server or VM will have their respective Docker Enterprise Edition installed and with swarm mode activated, the cluster will form and be orchestrated by the manager nodes running the control plane. Today, all manager nodes remain x86 Linux nodes that manage and orchestrate the heterogeneous cluster. The Trusted Registry, Image Scanning and Signing can all be applied to containerized mainframe applications. The granular Role Based Access Control (RBAC) and labels can also be applied to the diverse set of nodes in the cluster and containers in the registry. The best part is the same UI, same process and operating model can be applied across all these different application types.
Try Docker on IBMZ
Docker Enterprise Edition for Linux on IBM Z is available directly from IBM and their network of channel partners. Level 1 and Level 2 support is provided directly by IBM support engineers. Companies who already have a mainframe footprint can extend their existing partnership with IBM to add Docker EE to their technology stack for their critical applications.
Additionally, IBM recently announced a new release of the enterprise Linux platform designed specifically for mainframe systems. This next generation of IBM LinuxONE systems and Docker EE together provide complementary security capabilities from the system to the application and the ability for massive scale – up to two million containers per system.
Learn More:

Learn more about Docker Enterprise Edition and try online
About the Docker and IBM partnership
Contact Sales to try Docker on IBM Z

.@Docker Enterprise Edition for @Linux on @IBM Z (yes, #mainframe!) cc @IBMzSystemsClick To Tweet

The post Docker Enterprise Edition for Linux on IBM Z (yes, mainframe!) appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

Windows Networking at Parity with Linux for Kubernetes

Editor’s note: today’s post is by Jason Messer, Principal PM Manager at Microsoft, on improvements to the Windows network stack to support the Kubernetes CNI model.Since I last blogged about Kubernetes Networking for Windows four months ago, the Windows Core Networking team has made tremendous progress in both the platform and open source Kubernetes projects. With the updates, Windows is now on par with Linux in terms of networking. Customers can now deploy mixed-OS, Kubernetes clusters in any environment including Azure, on-premises, and on 3rd-party cloud stacks with the same network primitives and topologies supported on Linux without any workarounds, “hacks”, or 3rd-party switch extensions.”So what?”, you may ask. There are multiple application and infrastructure-related reasons why these platform improvements make a substantial difference in the lives of developers and operations teams wanting to run Kubernetes.  Read on to learn more!Tightly-Coupled CommunicationThese improvements enable tightly-coupled communication between multiple Windows Server containers (without Hyper-V isolation) within a single “Pod”. Think of Pods as the scheduling unit for the Kubernetes cluster, inside of which, one or more application containers are co-located and able to share storage and networking resources. All containers within a Pod shared the same IP address and port range and are able to communicate with each other using localhost. This enables applications to easily leverage “helper” programs for tasks such as monitoring, configuration updates, log management, and proxies. Another way to think of a Pod is as a compute host with the app containers representing processes.Simplified Network TopologyWe also simplified the network topology on Windows nodes in a Kubernetes cluster by reducing the number of endpoints required per container (or more generally, per pod) to one. Previously, Windows containers (pods) running in a Kubernetes cluster required two endpoints – one for external (internet) communication and a second for intra-cluster communication between other nodes or pods in the cluster. This was due to the fact that external communication from containers attached to a host network with local scope (i.e. not publicly routable) required a NAT operation which could only be provided through the Windows NAT (WinNAT) component on the host. Intra-cluster communication required containers to be attached to a separate network with “global” (cluster-level) scope through a second endpoint. Recent platform improvements now enable NAT”ing to occur directly on a container endpoint which is implemented with the Microsoft Virtual Filtering Platform (VFP) Hyper-V switch extension. Now, both external and intra-cluster traffic can flow through a single endpoint.Load-Balancing using VFP in Windows kernelKubernetes worker nodes rely on the kube-proxy to load-balance ingress network traffic to Service IPs between pods in a cluster. Previous versions of Windows implemented the Kube-proxy’s load-balancing through a user-space proxy. We recently added support for “Proxy mode: iptables” which is implemented using VFP in the Windows kernel so that any IP traffic can be load-balanced more efficiently by the Windows OS kernel. Users can also configure an external load balancer by specifying the externalIP parameter in a service definition. In addition to the aforementioned improvements, we have also added platform support for the following:Support for DNS search suffixes per container / Pod (Docker improvement – removes additional work previously done by kube-proxy to append DNS suffixes)[Platform Support] 5-tuple rules for creating ACLs (Looking for help from community to integrate this with support for K8s Network Policy)Now that Windows Server has joined the Windows Insider Program, customers and partners can take advantage of these new platform features today which accrue value to eagerly anticipated, new feature release later this year and new build after six months. The latest Windows Server insider build now includes support for all of these platform improvements.In addition to the platform improvements  for Windows, the team submitted code (PRs) for CNI, kubelet, and kube-proxy with the goal of mainlining Windows support into the Kubernetes v1.8 release. These PRs remove previous work-arounds required on Windows for items such as user-mode proxy for internal load balancing, appending additional DNS suffixes to each Kube-DNS request, and a separate container endpoint for external (internet) connectivity.https://github.com/kubernetes/kubernetes/pull/51063https://github.com/kubernetes/kubernetes/pull/51064These new platform features and work on kubelet and kube-proxy align with the CNI network model used by Kubernetes on Linux and simplify the deployment of a K8s cluster without additional configuration or custom (Azure) resource templates. To this end, we completed work on CNI network and IPAM plugins to create/remove endpoints and manage IP addresses. The CNI plugin works through kubelet to target the Windows Host Networking Service (HNS) APIs to create an ‘l2bridge’ network (analogous to macvlan on Linux) which is enforced by the VFP switch extension.The ‘l2bridge’ network driver re-writes the MAC address of container network traffic on ingress and egress to use the container host’s MAC address. This obviates the need for multiple MAC addresses (one per container running on the host) to be “learned” by the upstream network switch port to which the container host is connected. This preserves memory space in physical switch TCAM tables and relies on the Hyper-V virtual switch to do MAC address translation in the host to forward traffic to the correct container. IP addresses are managed by a default, Windows IPAM plug-in which requires that POD CIDR IPs be taken from the container host’s network IP space.The team demoed (link to video) these new platform features and open-source updates to the SIG-Windows group on 8/8. We are working with the community to merge the kubelet and kube-proxy PRs to mainline these changes in time for the Kubernetes v1.8 release due out this September. These capabilities can then be used on current Windows Server insider builds and the Windows Server, version 1709.Soon after RTM, we will also introduce these improvements into the Azure Container Service (ACS) so that Windows worker nodes and the containers hosted are first-class, Azure VNet citizens. An Azure IPAM plugin for Windows CNI will enable these endpoints to directly attach to Azure VNets with network policies for Windows containers enforced the same way as VMs.FeatureWindows Server 2016 (In-Market)Next Windows Server Feature Release, Semi-Annual ChannelLinuxMultiple Containers per Pod with shared network namespace (Compartment)One Container per Pod✔✔Single (Shared) Endpoint per PodTwo endpoints: WinNAT (External) + Transparent (Intra-Cluster)✔✔User-Mode, Load Balancing✔✔✔Kernel-Mode, Load Balancing Not Supported✔✔Support for DNS search suffixes per Pod (Docker update)Kube-Proxy  added multiple DNS suffixes to each request✔✔CNI Plugin Support Not Supported✔✔The Kubernetes SIG Windows group meets bi-weekly on Tuesdays at 12:30 PM ET. To join or view notes from previous meetings, check out this document.
Quelle: kubernetes

Secure Multi-Tenancy at Scale with Docker Enterprise Edition

With the latest release of Docker Enterprise Edition (EE), enterprise organizations are able to extend the benefits of containers across their entire application portfolio. Docker EE enables rapid modernization of traditional Windows and Linux applications as well as Linux applications running on IBM Z mainframes. By addressing all of these applications, Docker EE provides the opportunity to standardize around a common packaging format for greater portability, agility, and with an additional layer of security, resulting in more teams bringing their workloads into Docker EE.
The key to operating this diverse environment is to have a way to secure and isolate the applications and the multiple teams who build, ship, and deploy them. This release of Docker Enterprise Edition makes it possible for organizations to modernize traditional applications of every variety and to do so in a secure manner that aligns to complex organizational needs.
Building a Secure Software Supply Chain for Windows Applications
 

Windows applications make up about half of all enterprise applications. Docker has been working closely with Microsoft to ensure that the same security benefits that are available to Linux containers are also available to Windows Server containers. When Windows containers are managed with Docker EE, organizations get access to the same secure end-to-end software supply chain that is based on usable security features and trusted delivery across any infrastructure. For example, Docker EE security features like image signing and Windows Server security features like Windows Code Integrity combine to ensure the integrity of the applications that you deploy into production.
Docker and Microsoft have worked together to help our customers deliver safer apps. This joint effort is described in this new white paper, Delivering Safer Apps with Docker Enterprise Edition and Windows Server 2016. You can also read more about this in this Microsoft TechNet blog.  
Granular and Flexible Multi-Tenancy
Docker Enterprise Edition now includes the ability to define custom granular Role-based Access Controls (RBAC) down to the API operation level. This latest release also introduces a new resource control model that allows organizations to define resource collections which are granted to specific users, teams or orgs. These combine to deliver powerful access controls that align to any organization.

To learn more about these new capabilities, be sure to review the Docker Enterprise Edition documentation and register for the upcoming webinar Enhanced Access Controls with Docker Enterprise Edition delivered by Mark Church from our Customer Success team.

Check out these new #Docker assets to help you modernize your traditional applicationsClick To Tweet

Learn more about Docker Enterprise Edition:

Watch this video series about modernizing .NET applications
Read more about Docker Enterprise Edition
Register for other upcoming webinars

The post Secure Multi-Tenancy at Scale with Docker Enterprise Edition appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

Docker in the Enterprise Showcased at VMworld 2017

Last week, in the blistering heat of Las Vegas, Docker had a chance to interact with thousands of VMworld attendees to talk about containers. The message we heard again and again was that those in charge of infrastructure and virtualization are now being asked to manage containers. Sometimes it is being driven by developer teams that are already using Docker, but sometimes it is the infrastructure teams who recognize the benefits of moving applications to containers for easier maintenance and operations as well as cost savings. With Docker Enterprise Edition (EE), we have a solution that is designed to let IT secure and manage containerized applications.
Learn More About Docker for VMware Admins
If you’re interested in learning more about how Docker EE allows IT to improve operations, move workloads to the cloud and increase application agility all while saving costs, we’re happy to be partnering with the VMware User Group (VMUG) to deliver a webcast tomorrow. Register now to see how Docker EE is being used by some of the world’s largest container deployments, how Docker works with Windows applications or to clarify any confusion you may have about how Docker containers and VMs work together.
Docker + vSphere: Two Great Tools That Work Great Together
Wednesday, September 6
12:00 PM Central / 10:00 AM Pacific
Experience Docker EE Yourself
Attendees were able to play with Docker EE through our in-booth hands-on demos at VMworld, but don’t worry if you missed the conference! You can get that same experience at home through the hosted trial environments at https://www.docker.com/trial. Without any software to install, you can get access within minutes to a full Docker EE Advanced environment complete with the primary administrative interface and private registry solution, Docker Trusted Registry. Once inside the environment, you can follow the provided guide or explore and learn on your own.

For more on Docker Enterprise Edition:

Read more about Docker Enterprise Edition
Watch this video series about the latest release of Docker EE
Register for other upcoming webinars
Visit Docker for IT Professionals site to learn how Docker is used by IT team

Register for tomorrow’s #VMUG webcast about how #Docker and #VMware can work togetherClick To Tweet

The post Docker in the Enterprise Showcased at VMworld 2017 appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

Docker in Higher Education: Announcing Tools & Resources for Teachers

At the beginning of the summer we published a blog post announcing the Docker Student Developer Kit and Campus Ambassador program. The positive reception from students has been overwhelming and we were so excited to see hundreds of applications flood in!
Many teachers took notice of the enthusiasm of their students and began to reach out, asking us for tools, resources and support in using Docker in the classroom and adding Docker to their curriculum. To this end we have put together a free package for teachers!
Making use of this offer will enable teachers to effectively use and teach Docker in the classroom as we will be able to provide:

Free Tools: eliminating the need for students to install anything locally, thus saving you valuable class time
Resources: the most up to date presentations, hands-on labs, workshops etc. on every topic for every skill level
Support and recognition: you will have a dedicated contact at Docker to help you through the process and also be welcomed into the online Docker Teachers community where you can collaborate and learn from other educators

If you are a teacher at a higher-education institution who would like to unlock the benefits outlined above, please fill in this form and we will get in touch with next steps.
If you are still unsure about whether Docker is right for your classroom, Michael Irwin, Computer Science Instructor at Virginia Tech, has some wisdom to share. He believes that using Docker will save time and hassle in the classroom and show students that your course material is cutting edge:
“When a class starts up especially if it’s a language or a framework that they [the students] have never used before, they are spending the whole first day saying ‘Uugh.. How do I install everything? How do I configure the various pieces?’ … Using Docker allows more time for instruction and more time for the instructor to actually talk about the material itself rather than spending so much time on the periphery talking about ‘how do you set everything up?’”
“A lot of the time curriculum is written several years ago. Things have changed, but the documentation hasn’t been updated along with it.”
“Doing this kind of stuff shows them [the students] that we are playing with the latest and greatest. You can use Docker, you can use these containers and then you can use the right tool for the job to solve the problem at hand.”

To unlock Docker greatness in your classroom, please fill in this form.

#Docker unveils free tools, resources & support for teachers in higher educationClick To Tweet

The post Docker in Higher Education: Announcing Tools & Resources for Teachers appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

What’s New in Docker Enterprise Edition Webinar Recap

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

What’s new in #Docker Enterprise Edition? @TechGalJenny recaps the latest featuresClick To Tweet

Dive Deeper with Docker Enterprise Edition:

Read more about Docker Enterprise Edition
Test drive Docker EE without installing any software
Watch this video series about the latest release of Docker EE
Register for other upcoming webinars

The post What’s New in Docker Enterprise Edition Webinar Recap appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

An Inside Look at the Docker Captains Program

Since launching the Docker Captains over a year ago, we’ve received a lot of questions: What is a Docker Captain? What do Captains do? How do I become a Captain? So who better to answer that than the Docker Captains themselves? At DockerCon Austin, we asked the Docker Captains to share their favorite thing about wearing the Captain’s hat.

What is a Captain?
Captains are Docker experts that are leaders in their communities, organizations or ecosystems. As Docker advocates, they are committed to sharing their knowledge and do so every chance they get!
What do Captains do?
Captains are advisors, ambassadors, coders, contributors, creators, tool builders, speakers, mentors, maintainers and super users and are required to be active stewards of Docker in order to remain in the program.
In addition to sharing their knowledge with the community, Captains provide insight and feedback to Docker. They have direct access to our technical teams, and are first to hear about and try upcoming features, product releases and big announcements.

What do Captains get? 
In return for their efforts, Captains get access to the existing captains community and Docker staff. They get ongoing training, private briefings and Slack chat channels where Captains have real-time access to each other and the Docker team. Docker amplifies the efforts of Captains by sharing their activities on social media, in the Docker Weekly, and through speaking opportunities. They also get additional training and resources at Docker events like DockerCon. Oh and SWAG… lots of SWAG!
How do I follow what the Captains are up to?
Follow all of the Captains on twitter. Also check out the Captains GitHub repo to see what projects they have been working on.

How can I learn more about each Captain?
Docker Captains are eager to bring their technical expertise to new audiences both offline and online around the world – don’t hesitate to reach out to them via the social links on their Captain profile pages. You can filter the captains by location, expertise, and more.
What does Docker look for when selecting Captains?
Captains were nominated as candidates for the program because their passion for inspiring and educating others about Docker translates into creating incredible value for Docker’s users. Specifically, Captains meet some or all of the following criteria:

Technical: Captains are Docker practitioners – they use Docker and stay up to date with the latest Docker features and releases.
Innovators: Captains have created some amazing projects and are constantly inspired by the way they push the envelope:

Play with Docker – A sandbox training playground that allows users to immediately test Docker and related projects with no setup.
Open FaaS Project – OpenFaaS is a framework for building serverless functions with Docker which has first class support for metrics.

Creators: Captains create content to educate and support the Docker community, they respond to questions in forums and chat, and speak in public at meetups and conferences about Docker.
Influencers: Captains are leaders in their community, organization or ecosystem and focus on advancing the adoption and proper use of Docker technology.
Credible: Captains know their way around the container lifecycle and its applied uses, they’ve tried and worked with other technologies, and they share their findings. They are passionate about Docker as a solution, but the first to tell us we haven’t gotten something quite right.

How do I become a Captain?
We are actively looking to add additional leaders that inspire and educate the Docker community. Sign up for community.docker.com, let Captains know of your interest, share your activities on social media and hashtag #Docker, get involved in a local meetup as a speaker or organizer and continue to share your knowledge of Docker in your community and organization.

What does it mean to be a #DockerCaptain? @TheBurce shares an inside look at the programClick To Tweet

The post An Inside Look at the Docker Captains Program appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

Video Series: Modernizing .NET Apps for IT Pros

 
This is a new 5-part video series in Docker’s Modernize Traditional Apps (MTA) program, aimed at Microsoft IT Pros. The video series shows you how to move a .NET 3.5 app from Windows Server to a Windows Docker container and deploy it to a scalable, highly-available environment in the cloud – without any changes to the app.
Part 1 introduces the series, explaining what is meant by “traditional” apps and the problems they present. Traditional apps are built to run on a server, rather than on a modern application platform. They have common traits, like being complex to manage and difficult to deploy. A portfolio of traditional applications tends to under-utilize its infrastructure, and over-utilize the humans who manage it. Docker Enterprise Edition (EE) fixes that, giving you a consistent way to package, release and manage all your apps, without having to re-write them.

Part 2 shows how easy it is to move traditional apps to Docker EE. I start with an ASP.NET 3.5 WebForms application running on Windows Server 2003, and use Image2Docker to extract the app and package it as a Docker image. Then I run the application in a Docker Windows container on my Windows 10 workstation. I do that without changing the app, and without needing to access the original source code.

Part 3 covers the upgrade workflow in Docker EE. I build a new version of the Docker image for my app, using an updated version of the Windows Server Docker image. That’s how you roll out Windows updates and application updates in Docker EE, building a new version of the image and replacing running containers with the new version. I push the image to a private Docker registry and run the app in a VM on Azure. With minimal effort I’ve moved my traditional app from Windows Server 2003 to Windows Server 2016 in the cloud.

Part 4 demonstrates a highly-available staging environment, using Docker Cloud to spin up a multi-node Docker swarm in Azure. I deploy my app to the staging environment, running the website and a SQL Server database in Docker Windows containers. Then I add monitoring to the app, publishing the .NET and IIS Performance Counters from the container and collecting them with Prometheus, an open-source monitoring system which is popular in the Docker ecosystem.

Part 5 walks through Docker in production, using Docker Enterprise Edition Advanced. Docker EE can be deployed in the cloud or in the datacenter, and it gives you a production-grade Containers-as-a-Service (CaaS) solution. I show the security in Docker EE, with role-based access control and a secure software supply chain. I digitally sign my application images and store them in Docker Trusted Registry, then deploy the app to a production Docker cluster running Universal Control Plane.

Migrating traditional apps to Docker EE gives you increased efficiency, portability and security. If you’re planning a move to the cloud, or upgrading to modern infrastructure – or if you just want to consolidate workloads on existing infrastructure – Docker makes it easy.

IT Pros – learn how to modernize #dotnet apps with #Docker in a new video series from @EltonStonemanClick To Tweet

Find out more with the following links:

Learn about Docker’s MTA program for Docker EE
YouTube playlist for the Microsoft IT Pro MTA Series
Self-paced labs for IT Pros to modernize .NET apps

The post Video Series: Modernizing .NET Apps for IT Pros appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/