Brace yourselves, DockerCon Europe 2017 is coming!

DockerCon Europe 2017 is just around the corner and the whole European Docker community is getting ready for four days of incredible learning, networking and collaboration!

If you’re a registered attendee, login on to the DockerCon Europe Agenda Builder using the information you set up during the registration process. You can use the keyword search bar or filter by topics, days, tracks, experience level or target audience to get recommended sessions and build you schedule.

Every DockerCon Europe Attendee should have received an invitation to join the Docker Community Slack (dockercommunity.slack.com). If that’s not the case, please reach out to community@docker.com and we’ll make sure to resend the invitation.

DockerCon EU

Monday 16 October

Attendees who have signed up for Paid-Workshops or want to check in and pick up their badge and backpacks early should plan to be in Copenhagen by Monday morning.

Registration

Registration will be open from 12:00 – 19:30.

Workshops

Interested in attending a DockerCon EU Workshops on Monday? Here is the list of the workshops that are still available:

  • Introduction to Docker for Enterprise Developers
  • Docker on Windows: From 101 to Production
  • Docker for Java Developers
  • Learn DockerDockerCon EU

If you’ve already registered for a workshop, full day workshops run from 9:00 – 17:00 and the half-day workshops from 14:00 – 18:00 at the Bella Center. Room assignments will be emailed out.

Hallway Track

From 12:00 to 20:00 on Monday you’ll be able to meet and share knowledge with community members and practitioners using the DockerCon Hallway track recommendation algorithm.

Docker Pals

It can be downright intimidating to attend a conference by yourself, much less figure out how to make the most of your experience! Docker Pals gives you a built-in network at the conference by pairing you with another attendee and a DockerCon veteran as your guide. You will meet your pals at a Meet Your Pals Pre-Welcome Reception in the Expo Hall from 17:30 – 18:00. Pre-registration is required.

Welcome Reception

Join us at the evening Welcome reception in the Ecosystem Expo starting at 18:00.

 

Tuesday 17 October

Conference sessions start on Tuesday. Come early and be ready to learn, connect and collaborate with the Docker community.

Registration and Hallway Track

Registration and the Hallway track will be open from 07:30 – 18:00.

Ecosystem Expo

Stop by the booths of the DockerCon Europe Sponsors from 8:00am – 17:50 pm to learn, connect and network! Don’t forget to make your way to the Docker booth to learn more about our products and meet the Docker team.

General Session

Make sure to arrive early to be on time for our Day 1 General Session which starts at 09:00 sharp!

Breakout Sessions

Download the DockerCon App and start scheduling your DockerCon Agenda.

Hands-on Labs

From 11:00 – 18:00, take your Docker learning to the next level by completing self-paced Hands-on-Labs to walk through the process of managing and securing Docker containers.

Docker Professional Certification 

We are launching Docker Certification in Copenhagen. As a DockerCon attendee, you’ll have the opportunity to be among the first in the world to earn the ‘Docker Certified Associate’ designation with the digital certificate and verification to prove it! Learn more.

DockerCon After Party

Starting at 19:00, arcade and classic games like Pong, Asteroids, Tetris, Tron and Breakout will fill the venue providing you with ample entertainment and opportunities to challenge your fellow attendees to some friendly competition. You will be transported to a whole new gaming universe!

Wednesday 18 October

Wednesday brings more awesome content, learning and networking:

Thursday 19 October

On Thursday attendees have the option to attend the Enterprise Summit (sold out) to learn how Docker customers have transformed their Windows or Linux applications to run as a container making it more efficient, more portable, and more secure—all without touching a line of code. To join the waitlist, email dockercon@docker.com.

The Moby Summit (sold out) is also taking place on Thursday. You can join the waitlist by logging into the DockerCon portal for a chance to attend.

Finally, the DockerCon Hands-on labs will be open all day on Thursday and offering a broad range of topics that cover the interests of both developers and IT operations personnel on Windows and Linux.

Learn More:


Time to plan your DockerCon Europe 2017 Week
Click To Tweet


The post Brace yourselves, DockerCon Europe 2017 is coming! appeared first on Docker Blog.


Source: Docker

Like This (0)
Dislike This (0)

Introducing Hallway Track: Learn from People Around You at DockerCon

Docker Hallway track

Photo by: Youssef Shoufan at DockerCon Austin 2017

The DockerCon Hallway Track is coming to DockerCon Europe in Copenhagen. We’ve partnered with e180.co once again to deliver the next level of conference attendee networking. Together, we believe that education is a relationship, not an institution, and that a conversation can change someone’s life. After the success of our collaboration in Austin with Moby Mingle, we’re happy to be growing this idea further for Copenhagen.

DockerCon is all about learning new things and connecting with the right people. The Hallway Track will help you meet and share knowledge with community members and practitioners at the conference.  

Docker hallway track

So, what’s a Hallway Track?

DockerCon Hallway Track is a one-on-one or group conversations based on topics of interest that you schedule with other attendees during DockerCon. Hallway Track’s recommendation algorithm curates an individualized selection of Hallway Track topics for each participant, based on their behavior and interests.

It’s simple:

  1. Explore the knowledge Offer and Requests –where all participants post the knowledge they are willing to share.
  2. Pick something you want to learn or create your own Offer or Request.
  3. Book your Hallway Tracks and meet in person at the Hallway Track Lounge!

If you are interested in attending DockerCon. please register soon as we have only 100 tickets left! If you are already registered and want to book your Hallway Tracks, the platform will be launching today – look out for the email with instructions for logging into the system.


Introducing Hallway Track: Learn from People Around You at #DockerCon
Click To Tweet


The post Introducing Hallway Track: Learn from People Around You at DockerCon appeared first on Docker Blog.


Source: Docker

Like This (0)
Dislike This (0)

Your Docker Agenda for JavaOne

If you are one of the thousands that will be in San Francisco for JavaOne Oct 1-5th, don’t miss the opportunity to level-up your knowledge around container technology and Docker Community and Enterprise Edition. We’ve listed our must-attend sessions below:

Monday, October 2nd

Monday, Oct 02, 11:00 a.m. – 11:45 a.m. | Java in a World of Containers [CON4429]

Speakers: Paul Sandoz and Mikael Vidstedt, Oracle

This session explains how OpenJDK 9 fits into the world of containers, specifically how it fits with Docker images and containers. The first part of the session focuses on the production of Docker images containing a JDK. It introduces technologies, such as J-Link, that can be used to reduce the size of the JDK and discusses the inclusion of class-data-sharing (CDS) archives and ahead-of-time (AOT) shared object libraries. The second part describes how the Java process can be a good citizen when running within a Java container and obeying resource limits. The presentation also covers the role of CDS archives and AOT shared object libraries that can be shared across running containers to reduce startup time or memory usage.

 

Tuesday, October 3rd

8:30 a.m. – 10:30 a.m. |  Hands-on Lab: Docker 101 [HOL7960]

Eric Smalling, Ben Bonnefoy, Mano Marks, Docker

Dennis Foley and Richard Wark, Oracle

If you are just getting started learning about the Docker platform and want to get up to speed, this is the lab for you. Come learn the  basics including running containers, building images, and basics on networking, orchestration, security, and volumes.

8:30 a.m. – 9:15 a.m. | Modernizing Traditional Apps with Docker EE: Java Edition [CON7951]

Sophia Parafina, Docker

Most large enterprises have huge application install bases. Many have apps running in production that were written by people who have moved on to other projects, or even other companies. How do you bring older, critical apps into a new, modern containerized infrastructure? In this presentation, you’ll learn the benefits of moving to a containerized infrastructure and how to easily package a Java EE application to a Docker Enterprise Edition container without changing any code. And then begin the process of modernizing it by replacing the JavaServer Faces client with a JavaScript client written in React.

 

Wednesday, October 4th

Wednesday, Oct 04, 2:45 p.m. – 3:30 p.m. | Best Practices for Developing and Deploying Java Applications with Docker [CON7957]

Speaker: Eric Smalling, Docker

What if you could run your Java application in the same artifacts as your developer workstation, integration, and user acceptance testing environments as it does in production? With the Docker platform, your deployment artifacts conform to a common, portable standard that allows your team to do exactly that. In this session learn how to best run the JVM inside containers; ensure it is built and tested in deterministic, repeatable fashion; and deploy it in a guaranteed known-good-state in every environment. This session explores the basics of the Docker platform, how to build and run your applications in containers, how to deploy a web application using the same artifacts on workstations and servers, and best practices for managing and configuring JVM-based applications in containers.

Wednesday, Oct 04, 2:45 p.m. – 3:30 p.m. | Docker Tips and Tricks for Java Developers [CON4060]

Speaker: Ray Tsang, Google

Everyone is talking about containers—but be aware! It takes discipline to use container technology. It may not be as secure nor as optimal as you thought it would be. Although it’s relatively easy to create a new immutable container image to run everywhere, you may have fallen into many of the caveats. Is it running as the root user? Why are the images taking so much space? Why did your containers run out of space in the first place!? Most importantly, your container images may not be as immutable nor repeatable as you thought, and your Java process might be overutilizing assigned resources! Attend this session to learn how to best address these issues when building your Java container images.


It’s almost time for #JavaOne! Here’s a don’t miss guide to the best #Docker sessions!
Click To Tweet


The post Your Docker Agenda for JavaOne appeared first on Docker Blog.


Source: Docker

Like This (0)
Dislike This (0)

Kubernetes 1.8 release integrates with containerd 1.0 Beta

CRI-containerd

Intent of containerd effort

When containerd was first developed it had two goals. The first was to solve the upgrade problem with running containers and provide a codebase where OCI runtimes, like runc, could be integrated into Docker.  However, as needs change in the container space and after speaking  with various members of the community at the beginning of this year, we decided to expand the scope of containerd and make it a fully functional container daemon with storage, image distribution and runtime.

containerd fully supports the OCI Runtime and Image specifications that are part of the recently released 1.0 specifications. Additionally, it was important to build a stable runtime for users and platform builders. We wanted containerd to be fully functional; but also, it needed to retain a small core codebase so that it is easy to maintain and support in the long run with an LTS release receiving backported patches on a stable API.

To demonstrate the progress made on the project,  Stephen Day presented the current status of containerd 1.0 alpha at the Moby Summit in LA two weeks ago,:

Check out the getting started with containerd guide to get your feet wet with containerd if you want to integrate it in your own container based system.

Introduction of the cri-containerd effort

Docker and Kubernetes both have similar requirements when it comes to a container runtime. They need something small, stable and easy to maintain. They also need an API that abstracts away platform and system specific details so that they can build a featureset for users without being slowed down by the messy syscalls and various driver support that is required to execute containers on a variety of operating systems.        

In order to have Kubernetes consume containerd for its container runtime we needed to implement the CRI interface.  CRI stands for “Container Runtime Interface” and is responsible for distribution and the lifecycle of pods and containers running on a cluster.

At Docker, we have a full time engineer working on the cri-containerd project along with the other maintainers to finish the cri-containerd integration to get Kubernetes running on containerd. Here is a presentation Liu Lantao from Google presented 2 weeks ago at Moby Summit LA about the status of cri-containerd:

Moby Summit LA allowed the various teams from different companies involved in these projects to meet and demo the latest about containerd, cri-containerd, bucketbench, and libnetwork CNI implementation. You can find a recap of the summit on the Moby blog, and get the latest updates from the teams at Moby Summit Copenhagen in a few weeks.


.@Kubernetes 1.8 release integrates w/ @containerd 1.0 Beta 
Click To Tweet


Learn more:

The post Kubernetes 1.8 release integrates with containerd 1.0 Beta appeared first on Docker Blog.


Source: Docker

Like This (0)
Dislike This (0)

Introducing the Docker Global Professional Certification Program

 Docker is excited to announce the first and only official professional certification program for the Docker Enterprise Edition (EE) platform.

The new Docker Certified Associate (DCA) certification, launching at DockerCon Europe on October 16, 2017, serves as a foundational benchmark for real-world container technology expertise with Docker Enterprise Edition. In today’s job market, container technology skills are highly sought after and this certification sets the bar for well-qualified professionals. The professionals that earn the certification will set themselves apart as uniquely qualified to run enterprise workloads at scale with Docker Enterprise Edition and be able to display the certification logo on resumes and social media profiles.

The DCA is the first in a comprehensive multi-tiered certification program and the exam was created by top practitioners using a rigorous development process. It consists of 55 questions to be completed over 80 minutes covering essential skills on Docker Enterprise Edition.  The exam can be taken anywhere in the world at any time and is delivered using remote proctoring technology to ensure exam security while creating a simple and streamlined test taking experience for candidates.

Be among the first to earn the DCA designation and gain recognition for your enterprise container skills.

Get Started now

 

Be Among the First to Get Certified, at DockerCon Europe

Be one of the first to get your DCA on-site at DockerCon Europe. If you’ve reviewed the study guide and think you’ve got what it takes, join us in Copenhagen and take the exam. Testing is offered Tuesday through Thursday and we’ve got some special gifts to hand out to our first Docker Certified Associates.


Be the first #DockerCertified Associate – #Docker launches first official certification exam for…
Click To Tweet


Learn more:

The post Introducing the Docker Global Professional Certification Program appeared first on Docker Blog.


Source: Docker

Like This (0)
Dislike This (0)

The Docker Modernize Traditional Apps (MTA) Program Adds Microsoft Azure Stack

In April of this year, Docker announced the Modernize Traditional Apps (MTA) POC program with partners Avanade, Booz Allen, Cisco, HPE and Microsoft. The MTA program is designed to help IT teams flip the 80% maintenance to 20% innovation ratio on it’s head. The combination of Docker Enterprise Edition (EE), services and infrastructure into a turnkey program delivers portability, security and efficiency for the existing app portfolio to drive down total costs and make room for innovation like cloud strategies and new app development. The program starts by packaging of existing apps into isolated containers, providing the opportunity to migrate them to new on-prem or cloud environments, without any recoding.

 

Docker customers have already been taking advantage of the program to jumpstart their migration to Azure and are experiencing dramatically reduced deployment and scaling times — from weeks to minutes —  and cutting their total costs by 50% or more.

 

The general availability of Microsoft Azure Stack provides IT with the ability to manage their datacenters in the same way they manage Azure. The consistency in hybrid cloud infrastructure deployment combined with consistency in application packaging, deployment and management only further enhance operational efficiency. Docker is pleased to announce the addition of Azure Stack to the MTA Program for hybrid cloud environments. Docker will provide partners with a Technical Preview of the Docker EE template for Azure Stack as an easy and quick way to deploy and manage containers for the MTA project.

The Docker MTA Program is available from the partners:

 

Microsoft and Avande have been actively delivering MTA PoCs to containerize and deploy legacy workloads to Azure cloud and will be applying those same skills to Azure Stack and help further modernize apps to microservices.

“With expertise in Microsoft Azure Stack and great success leading the Modernize Traditional Application program [MTA] with Docker, Avanade is excited to bring these technologies together for clients via a single provider,” said Pat Cimprich, Executive, Cloud and Application Transformation, Avanade. “The Avanade solution provides a turnkey, fully managed Azure-consistent experience so enterprises can quickly move applications to Microsoft Azure or Microsoft Azure Stack via Docker container technology. This combination enables clients to migrate applications to the cloud today to realize significant cost savings immediately and then modernize them over time at their own pace.”

 

Booz Allen Hamilton specializes in modernizing apps to any infrastructure specifically for federal agency IT (civilian and department of defense) with a deep understanding of unique  compliance requirements and continues the transformation to devops and microservices.

 

Cisco Data Center solutions help organizations develop, deploy, and run their business-essential applications and workloads quickly, securely, and reliably across the multi-cloud domain. The Cisco MTA program is an end-to-end “Proof of Value” offer that demonstrates the ease and savings of containerizing traditional applications on Cisco UCS and Docker Enterprise Edition.

Cisco and Microsoft offer a turnkey hybrid cloud solution built on the power of Cisco UCS and Microsoft Azure Stack and it is orderable starting today. With the expansion of the MTA program, our customers can now confidently deploy containerized applications on a validated solution jointly developed by Cisco and Microsoft, taking advantage of the agile and scalable cloud infrastructure provided by the Cisco Integrated System for Microsoft Azure Stack.” said Satinder Sehti, VP Data Center Solutions Engineering & UCS Product Management.

 

The HPE MTA Program is driving engagements to help customers modernize traditional applications on HPE Proliant for Azure Stack integrated solution and a wide range of other datacenter systems available.

“Customers have been asking for more choice in the way they manage and deliver applications. Our goal is to help customers move to modern application architectures that best suit their needs,” said McLeod Glass, Vice President, Product Management, Software-Define and Cloud Group, HPE. “With the integration of HPE ProLiant for Microsoft Azure Stack and Windows Server 2016 validated solutions into Docker’s Modernize Traditional Apps Program, customers now have more options to deploy and manage containerized legacy apps to help them simplify hybrid IT.”

Whether on-premises or in the cloud, the Docker MTA program delivers immediate benefits of portability, security and efficiency for existing applications without recoding the application. Now with Azure Stack, consistency and simplicity of hybrid cloud infrastructures services go hand in hand with consistency and agility of application container deployment. 

Visit www.docker.com/MTA or contact Docker sales.


Modernize Traditional Apps (MTA) to #Azure + #AzureStack with #Docker
Click To Tweet


To learn more about Docker solutions for IT:

The post The Docker Modernize Traditional Apps (MTA) Program Adds Microsoft Azure Stack appeared first on Docker Blog.


Source: Docker

Like This (0)
Dislike This (0)

Exciting new things for Docker with Windows Server 1709

What a difference a year makes… last September, Microsoft and Docker launched Docker Enterprise Edition (EE), a Containers-as-a-Service platform for IT that manages and secures diverse applications across disparate infrastructures, for Windows Server 2016. Since then we’ve continued to work together and Windows Server 1709 contains several enhancements for Docker customers.

Docker Enterprise Edition Preview

To experiment with the new Docker and Windows features, a preview build of Docker is required. Here’s how to install it on Windows Server 1709 (this will also work on Insider builds):

Install-Module DockerProvider
Install-Package Docker -ProviderName DockerProvider -RequiredVersion preview

To run Docker Windows containers in production on any Windows Server version, please stick to Docker EE 17.06.

Docker Linux Containers on Windows

A key focus of Windows Server version 1709 is support for Linux containers on Windows. We’ve already blogged about how we’re supporting Linux containers on Windows with the LinuxKit project.

To try Linux Containers on Windows Server 1709, install the preview Docker package and enable the feature. The preview Docker EE package includes a full LinuxKit system (all 13MB of it) for use when running Docker Linux containers.

[Environment]::SetEnvironmentVariable("LCOW_SUPPORTED", "1", "Machine")
Restart-Service Docker

To disable, just remove the environment variable:

[Environment]::SetEnvironmentVariable("LCOW_SUPPORTED", $null, "Machine")
Restart-Service Docker

Docker Linux containers on Windows is in preview, with ongoing joint development by Microsoft and Docker. Linux Containers is also available on Windows 10 version 1709 (“Creators Update 2”). To try it out, install the special Docker for Windows preview available here.

Docker ingress mode service publishing on Windows

Parity with Linux service publishing options has been highly requested by Windows customers. Adding support for service publishing using ingress mode in Windows Server 1709 enables use of Docker’s routing mesh, allowing external endpoints to access a service via any node in the swarm regardless of which nodes are running tasks for the service.

These networking improvements also unlock VIP-based service discovery when using overlay networks so that Windows users are not limited to DNS Round Robin.

Check out the corresponding post on the Microsoft Virtualization blog for details on the improvements.

Named pipes in Windows containers

A common and powerful Docker pattern is to run Docker containers that use the Docker API of the host that the container is running on, for example to start more Docker containers or to visualize the containers, networks and volumes on the Docker host. This pattern lets you ship, in a container, software that manages or visualizes what’s going on with Docker. This is great for building software like Docker Universal Control Plane.

Running Docker on Linux, the Docker API is usually hosted on Unix domain socket, and since these are in the filesystem namespace, sockets can be bind-mounted easily into containers. On Windows, the Docker API is available on a named pipe. Previously, named pipes where not bind-mountable into Docker Windows containers, but starting with Windows 10 and Windows Server 1709, named pipes can now bind-mounted.

Jenkins CI is a neat way to demonstrate this. With Docker and Windows Server 1709, you can now:

  1. Run Jenkins in a Docker Windows containers (no more hand-installing and maintaining Java, Git and Jenkins on CI machines)
  2. Have that Jenkins container build Docker images and run Docker CI/CD jobs on the same host

I’ve built a Jenkins sample image (Windows Server 1709 required) that uses the new named-pipe mounting feature. To run it, simple start a container, grab the initial password and visit port 8080. You don’t have to setup any Jenkins plugins or extra users:

> docker run -d -p 8080:8080 -v .pipedocker_engine:.pipedocker_engine friism/jenkins
3c90fdf4ff3f5b371de451862e02f2b7e16be4311903649b3fc8ec9e566774ed
> docker exec 3c cmd /c type c:.jenkinssecretsinitialAdminPassword
<password>

Now create a simple freestyle project and use the “Windows Batch Command” build step. We’ll build my fork of the Jenkins Docker project itself:

git clone --depth 1 --single-branch --branch add-windows-dockerfile https://github.com/friism/docker-3 %BUILD_NUMBER%
cd %BUILD_NUMBER%
docker build -f Dockerfile-windows -t jenkins-%BUILD_NUMBER% .
cd ..
rd /s /q %BUILD_NUMBER%

Hit “Build Now” and see Jenkins (running in a container) start to build a CI job to build a container image on the very host it’s running on!

Smaller Windows base images

When Docker and Microsoft launched Windows containers last year, some people noticed that Windows container base images are not as small as typical Linux ones. Microsoft has worked very hard to winnow down the base images, and with 1709, the Nanoserver download is now about 70MB (200MB expanded on the filesystem).

One of the things that’s gone from the Nanoserver Docker image is PowerShell. This can present some challenges when authoring Dockerfiles, but multi-stage builds make it fairly easy to do all the build and component assembly in a Windows Server Core image, and then move just the results into a nanoserver image. Here’s an example showing how to build a minimal Docker image containing just the Docker CLI:

# escape=`
FROM microsoft/windowsservercore as builder
SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"]
RUN Invoke-WebRequest -Uri https://download.docker.com/win/static/test/x86_64/docker-17.09.0-ce-rc1.zip -OutFile 'docker.zip'
RUN Expand-Archive -Path docker.zip -DestinationPath .

FROM microsoft/nanoserver
COPY --from=builder ["dockerdocker.exe", "C:Program Filesdockerdocker.exe"]
RUN setx PATH "%PATH%;C:Program Filesdocker"
ENTRYPOINT ["docker"]

You now get the best of both worlds: Easy-to-use, full-featured build environment and ultra-small and minimal runtime images that deploy and start quickly, and have minimal exploit surface area. Another good example of this pattern in action are the .NET Core base images maintained by the Microsoft .NET team.

Summary

It’s hard to believe that Docker Windows containers GA’d on Windows Server 2016 and Windows 10 just one year ago. In those 12 months, we’ve seen lots of adoption by the Docker community and lots of uptake with customers and partners. The latest release only adds more functionality to smooth the user experience and brings Windows overlay networking up to par with Linux, with smaller container images and with support for bind-mounting named pipes into containers.

To learn more about Docker solutions for IT:


Exciting new things for #Docker with @Windows Server 1709
Click To Tweet


The post Exciting new things for Docker with Windows Server 1709 appeared first on Docker Blog.


Source: Docker

Like This (0)
Dislike This (0)

Yes to databases in containers – Microsoft SQL Server available on Docker Store

Microsoft SQL Server 2017 is now available for the first time on multiple platforms: Windows, Linux and Docker. Your databases can be in containers with no lengthy setup and no prerequisites, and using Docker Enterprise Edition (EE) to modernize your database delivery. The speed and efficiency benefits of Docker and containerizing apps that IT Pros and developers have been enjoying for years are now available to DBAs.

 

Try the Docker SQL Server lab now and see how database containers start in seconds, and how you can package your own schemas as Docker images.

 

If you’ve ever sat through a SQL Server install, you know why this is a big deal: SQL Server takes a while to set up, and running multiple independent SQL Server instances on the same host is not simple. This complicates maintaining dev, test and CI/CD systems where tests and experiments might break the SQL Server instance.

With SQL Server in Docker containers, all that changes. Getting SQL Server is as simple as running `docker image pull`, and you can start as many instances on a host as you want, each of them fresh and clean, and tear them back down when you’re done.

Database engines are just like any other server-side application: they run in a process that uses CPU and memory, they store state to disk, and they make services available to clients over the network. That all works the same in containers, with the added benefit that you can limit resources, manage state with volume plugins and restrict network access.

Many Docker customers are already running highly-available production databases in containers, using technologies like Postgres. Now the portability, security and efficiency you get with Docker EE is available to SQL Server DBAs.

 

Modernize your database delivery with Docker


Traditional database delivery is difficult to fit into a modern CI/CD pipeline, but Docker makes it easy. You use Microsoft’s SQL Server Docker image and package your own schema on top, using an automated process. Anyone can run any version of the database schema, just by starting a container – they don’t even need to have SQL Server installed on their machine.

This is the database delivery workflow with Docker:

sql-ci.jpg

  1. DBA pushes schema changes to source control
  2. CI process packages the schema into a Docker image based on Microsoft-published SQL Server base images
  3. CI process runs test suites using disposable database containers created from the new image
  4. CD process upgrades the persistent database container in the test environment to the new image
  5. CD process runs a database container to upgrade the production database, applying diff scripts to align the schema to the new image

The whole process of packaging, testing, distributing and upgrading databases can be automated with Docker. You run database containers in development and test environments which are fast, isolated, and have identical schema versions. You can continue using your existing production database, but use the tested Docker image to deploy updates to production.

Support and availability

Docker Enterprise Edition is a supported platform for running SQL Server in Linux in containers in production. SQL Server for Linux is a certified container image which means you have support from Microsoft and Docker to resolve any issues.

On Windows Server and Windows 10 you can run SQL Server Express in containers with Docker, to modernize your database delivery process for existing SQL Server deployments, without changing your production infrastructure.

The new SQL containers will be available for download in Docker Store in October – but you can start testing with the pre-GA containers in Store today. Already there have been over 1 million downloads from Docker Hub of the SQL Server preview for Linux containers.


Yes you can run databases in containers – #SQLServer on #Docker EE
Click To Tweet


To learn more about Docker solutions for IT:

The post Yes to databases in containers – Microsoft SQL Server available on Docker Store appeared first on Docker Blog.


Source: Docker

Like This (0)
Dislike This (0)

A Day in the Life of a Docker Admin

About two months ago, we celebrated SysAdmin Day and kicked off our learning series for IT professionals. So far we’ve gone through the basics of containers and how containers are delivering value back to the company through cost savings. Now we begin the next stage of the journey by introducing how to deploy and operate containerized applications.

For the next few weeks, we are going to relate typical IT administrative tasks that many of you are familiar with to the tasks of a Docker admin. In the end, containerized applications are still applications and it is still primarily the responsibility of IT to secure and manage them. That is the same regardless of if the application runs in a container or not.

In this “A Day in the LIfe of a Docker Admin” series, we will discuss how common IT tasks translate to the world of Docker, such as:

  • Managing .NET apps and migrating them off Windows Server 2008
  • How networking with containers work and how to build an agile and secure network for containers
  • How to achieve a secure and compliant application environment for any industry
  • Integrating Docker with monitoring and logging tools

As a first step, let’s make sure we know how to deliver and deploy your first container.

Hello World!

Just like the first time you installed ESXi and built a virtual machine, or when you opened an account on AWS or Azure and spun up your first cloud instance, one of the first things anyone wants to do is deploy their first working Docker container.

Docker Admin

With Docker, there are great hands-on systems you can use to get started right away, with nothing to download or install. The best place to start is the Play With Docker online classroom (PWD). PWD was started by a couple of our Docker Captains to do exactly what the name implies: get hands-on experience and learn. We have gathered together several labs geared towards IT pros into 3 stages, with a handful of short tutorials in each stage.

Stage 1: Hello World!

Create and run your first Docker containers, learn about images and layers, and then turn on Swarm Mode to run a multi-service / multi-container application in a cluster.

Stage 2: Dig Deeper

Learn about Docker platform security, securing containers, and Docker networking, and then combine all of your knowledge of Swarm Mode, Services, and Security in an Orchestration Workshop. Plus, there’s a link to our hosted Docker Enterprise Edition trial so you can try it all in the full system on our hosted site (still, free, of course).

Stage 3: Moving to Production

After you have seen and played with all the pieces, it is time to learn how to bring Docker in to your own environment. You can also download Docker for your own system on both Windows and Mac.

To learn more about Docker for IT Pros, be sure to check out these resources:


Follow our new blog series – A Day in the Life of a #Docker Admin
Click To Tweet


The post A Day in the Life of a Docker Admin appeared first on Docker Blog.


Source: Docker

Like This (0)
Dislike This (0)

Get Familiar with Docker Enterprise Edition Client Bundles

Docker Enterprise Edition (EE) is the only Containers as a Service (CaaS) Platform for IT that manages and secures diverse applications across disparate infrastructure, both on-premises and in the cloud.

There’s a little mentioned big feature in Docker Enterprise Edition (EE) that seems to always bring smiles to the room once it’s displayed. Before I tell you about it, let me first describe the use case. You’re a sysadmin managing a Docker cluster and you have the following requirements:

  • Different individuals in your LDAP/AD need various levels of access to the containers/services in your cluster
  • Some users need to be able to go inside the running containers.
  • Some users just need to be able to see the logs
  • You do NOT want to give SSH access to each host in your cluster.

Now, how do you achieve this? The answer, or feature rather, is a client bundle. When you do a docker version command you will see two entries. The client portion of the engine is able to connect to a local server AND a remote once a client bundle is invoked.

Docker Enterprise Edition Client Bundles

What is a client bundle?

A client bundle is a group of certificates downloadable directly from the Docker Universal Control Plane (UCP) user interface within the admin section for “My Profile”. This allows you to authorize a remote Docker engine to a specific user account managed in Docker EE, absorbing all associated RBAC controls in the process. You can now execute docker swarm commands from your remote machine that take effect on the remote cluster.

Example:

I have a user named ‘bkauf’ in my UCP. I download and extract a client bundle for this user.

Docker Enterprise Edition Client Bundles

Docker Enterprise Edition Client Bundles

I open a terminal session with my docker for mac and issue a docker version command. You will see the server version matches the client. I can do a docker ps and verify nothing is running.

Docker Enterprise Edition Client Bundles

Now, I navigate to the extracted bundle directory and run the env.sh script (env.ps1 for windows)

Docker Enterprise Edition Client Bundles

Notice the server now lists my version as ucp/2.2.2. This is the version of my UCP manager; I’m remotely connected from my laptop to my remote cluster assuming the bkauf user’s access levels. I can now do various things such as create a service, view its tasks(containers) and even log into this REMOTE container from my laptop all through the API, no SSH access needed. I need not worry about what host the container is on! This is made possible by the role/permission set up for the use with the granular Role Based Access Control available with Docker EE.

Docker Enterprise Edition Client Bundles

Docker Enterprise Edition Client Bundles

What about a Windows container on a Windows node in a UCP cluster you ask? Linux OR Windows nodes, remote access through your client bundle all works the same!

Docker Enterprise Edition Client Bundles

 Docker Enterprise Edition (EE) is the only Containers as a Service (CaaS) Platform for IT that manages and secures diverse applications across disparate infrastructure, both on-premises and in the cloud. Docker EE embraces both traditional applications and microservices, built on Linux and Windows, and intended for x86 servers, mainframes, and public clouds. Docker EE unites all of these applications into single platform, complete with customizable and flexible access control, support for a broad range of applications and infrastructure, and a highly automated software supply chain.

Learn More


Get Familiar with #Docker Enterprise Edition Client Bundles
Click To Tweet


The post Get Familiar with Docker Enterprise Edition Client Bundles appeared first on Docker Blog.


Source: Docker

Like This (0)
Dislike This (0)