Kategorie: Kubernetes

DockerCon Europe Diversity Scholarship!

Each year, DockerCon brings the community together to learn, belong and contribute. With generous support from the  OCI) our team has created the DockerCon Europe Scholarship Program to provide members of the Docker community, who are traditionally underrepresented, mentorship and a financial scholarship to attend DockerCon in Copenhagen this year. This scholarship program aims to foster inclusivity by supporting members of our community through access to resources, tools and mentorship needed to facilitate career and educational development.

If you are interested in applying for the DockerCon Scholarship, follow the steps below:
Application Process:
The application process includes completing one of the five self-paced trainings along with the scholarship application form.
Step 1
Complete at least one of the free self-paced courses available in the Docker Playground. These courses are intended for both Dev and Ops beginner and intermediate level Docker users. Select which course you feel best fits you.
Step 2
After you’ve finished one of the courses, complete the application here. In the application, you will need to provide the name(s) of the lab(s) you completed along with the answers to the quiz at the end of the course.  
Deadline to Apply:
Tuesday, 5 September, 2017 at 5:00PM PST
Selection Process
A committee of Docker community members will review and select the scholarship recipients based on the completion of one of the courses and application. Recipients will be notified by the week of 18 September 2017.  
What’s included if you are selected for the scholarship:

Full DockerCon Conference Pass
Round-trip airfare
Hotel accommodations for 4 nights (16 October, 17 October, 18 October, 19 October )
1:1 mentorship session with a member of the  Docker community on-site at DockerCon

Requirements

All applicants must complete at least one self-paced online course found at: http://training.docker.com/category/self-paced-online 
Must be able to attend DockerCon Europe 2017 (16 October – 19 October, 2017)
Must be 18 years old or older to apply
Must have a valid passport to travel to Copenhagen, Denmark.
Learn more about the DockerCon Diversity Scholarship here. 

Have questions or concerns? Reach us at dockercon@docker.com
More free Docker ressources:

Attend local Docker meetups
Check out the Docker Playground
View the Docker Youtube Channel

#DockerCon Europe Diversity Scholarship is now open! Learn more and apply here!Click To Tweet

The post DockerCon Europe Diversity Scholarship! appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

Be a Budget Hero with Docker Enterprise Edition

We recently started a multi-part learning series for SysAdmins and IT professionals called IT Starts With Docker. We started with the basics, covering container technology and Docker solutions for the enterprise. Now, we shift to the important question: Is it worth your time and your company’s investment to further explore Docker Enterprise Edition (EE)?
The resounding answer to that question is YES. IT teams who have adopted Docker EE are finding it faster and easier to deploy and maintain their applications, plus drive better infrastructure utilization, all without touching the underlying code. Developer teams are realizing productivity gains of their own by being able to onboard new developers faster, shortening the cycles from development to production, and elimination of the burdensome “it worked on my machine” problems.

Try the simple ROI calculator for yourself. It takes just a couple of minutes and allows you to estimate your own savings with Docker EE and how you can become the budget hero of your department. Then, register for our live webinar on Tuesday, August 15th, The Business Value of Docker, where we will outline how organizations like your own are saving 50% on their total costs with Docker EE. 
The calculator is based on real data from Docker EE customers across a broad range of industries. In just the first 5 days of a Proof-of-Concept through the Modernize Traditional Apps program, customers are seeing how they can:

cut application deployment times from days or even weeks to hours or minutes
streamline application maintenance, cutting time spent on upgrades by as much as 99%
consolidate and maximize infrastructure utilization (yes, it works with your existing VMs)
and enable development teams and IT operations teams to work efficiently together to accelerate application delivery

Where IT Begins
If you’re new to IT Starts With Docker, learn the basics of Docker and containers with our online hands-on learning environment. Within a few minutes of following the labs, you will see why so many organizations are now running containers in production. These labs may trigger your own ideas of how Docker might help you in your job: smoother deployment and maintenance of applications, securing apps throughout your software supply chain, and managing apps across disparate infrastructure. Docker can help with all of these and more.
From the first application that gets containerized with Docker, you can show positive returns. We invite you to sign up for updates on this special learning series and see how Docker can make you a budget hero.
To learn more about Docker EE:

Read more about Docker Enterprise Edition 
Try the ROI calculator and download the whitepaper
Visit IT Starts with Docker and sign up for updates
Explore and register for other upcoming webinars or join a local Meetup
Learn everything you need to know about Docker at DockerCon Europe

Four Paths To Become an IT Budget Hero with #Docker #ITStartsWithDockerClick To Tweet

The post Be a Budget Hero with Docker Enterprise Edition appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

What is containerd ?

We have done a few talks in the past on different features of containerd, how it was designed, and some of the problems that we have fixed along the way.  Containerd is used by Docker, Kubernetes CRI, and a few other projects but this is a post for people who may not know what containerd actually does within these platforms.  I would like to do more posts on the featureset and design of containerd in the future but for now, we will start with the basics.
I think the container ecosystem can be confusing at times. Especially with the terminology that we use. Whats this? A runtime. And this? A runtime…  containerd as the name implies, not contain nerd as some would like to troll me with, is a container daemon.  It was originally built as an integration point for OCI runtimes like runc but over the past six months it has added a lot of functionality to bring it up to par with the needs of modern container platforms like Docker and Kubernetes.

Since there is no such thing as Linux containers in the kernelspace, containers are various kernel features tied together, when you are building a large platform or distributed system you want an abstraction layer between your management code and the syscalls and duct tape of features to run a container.  That is where containerd lives.  It provides a client layer of types that platforms can build on top of without ever having to drop down to the kernel level.  It’s so much nicer towork with Container, Task, and Snapshot types than it is to manage calls to clone() or mount().
Containerd was designed to be used by Docker and Kubernetes as well as any other container platform that wants to abstract away syscalls or OS specific functionality to run containers on linux, windows, solaris, or other OSes.  With these users in mind, we wanted to make sure that containerd has only what they need and nothing that they don’t.  Realistically this is impossible but at least that is what we try for.  Things like networking are out of scope for containerd.  The reason for this is, when you are building a distributed system, networking is a very central aspect.  With SDN and service discovery today, networking is way more platform specific than abstracting away netlink calls on linux.  Most of the new overlay networks are route based and require routing tables to be updated each time a new container is created or deleted.  Service discovery, DNS, etc all have to be notified of these changes as well.  It would be a large chunk of code to be able to support all the different network interfaces, hooks, and integration points to support this if we added networking to containerd.  What we did instead is opted for a robust events system inside containerd so that multiple consumers can subscribe to the events that they care about.  We also expose a task API that lets users create a running task, have the ability to add interfaces to the network namespace of the container, and then start the container’s process without the need for complex hooks in various points of a container’s lifecycle.
Another area that has been added to containerd over the past few months is a complete storage and distribution system that supports both OCI and Docker image formats.  You have a complete content addressed storage system across the containerd API that works not only for images but also metadata, checkpoints, and arbitrary data attached to containers.
We also took the time to rethink how “graphdrivers” work.  These are the overlay or block level filesystems that allow images to have layers and you to perform efficient builds.  Graphdrivers were initially written by Solomon and I when we added support for devicemapper.  Docker only supported AUFS at the time so we modeled the graphdrivers after the overlay filesystem.  However, making a block level filesystem such as devicemapper/lvm act like an overlay fillesystem proved to be much harder to do in the long run.  The interfaces had to expand over time to support different features than what we originally thought would be needed.  With containerd, we took a different approach, make overlay filesystems act like a snapshotter instead of vice versa.  This was much easier to do as overlay filesystems provide much more flexibility than snapshotting filesystems like BTRFS, ZFS, and devicemapper as they don’t have a strict parent/child relationship.  This helped us build out a smaller interface for the snapshotters while still fulfilling the requirements needed from things like a builder as well as reduce the amount of code needed, making it much easier to maintain in the long run.
So what do you actually get using containerd?  You get push and pull functionality as well as image management.  You get container lifecycle APIs to create, execute, and manage containers and their tasks. An entire API dedicated to snapshot management.  Basically everything that you need to build a container platform without having to deal with the underlying OS details.  I think the most important part of containerd is having a versioned and stable API that will have bug fixes and security patches backported.

What’s #containerd? All you need to know about #Docker’s open and reliable #container runtime Click To Tweet

Learn more about containerd:

Check out the containerd GitHub Repo
Join the containerd Slack channel
Register for the Moby Summit LA alongside Open Source Summit North America
Register for DockerCon Europe and DockerCon Moby Summit

The post What is containerd ? appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

Docker 101: Introduction to Docker webinar recap

Docker is standardizing the way to package applications, making it easier for developers to code and build apps on their laptop or workstation and for IT to manage, secure and deploy into a variety of infrastructure platforms
In last week’s webinar, Docker 101: An Introduction to Docker, we went from describing what a container is, all the way to what a production deployment of Docker looks like, including how large enterprise organizations and world-class universities are leveraging Docker Enterprise Edition (EE)  to modernize their legacy applications and accelerate public cloud adoption.
If you missed the webinar, you can watch the recording here:

We ran out of time to go through everyone’s questions, so here are some of the top questions from the webinar:
­Q: How does Docker get access to platform resources, such as I/O, networking, etc.­ Is it a type of hypervisor?
A: Docker EE is not a type of hypervisor. Hypervisors create virtual hardware: they make one server appear to be many servers but generally know little or nothing about the applications running inside them. Containers are the opposite: they make one OS or one application server appear to be many isolated instances. Containers explicitly must know the OS and application stack but the hardware underneath is less important to the container. In Linux operating systems, the Docker engine is a daemon installed directly in a host operating system kernel that isolates and segregates different procedures for the different containers running on that operating system. The platform resources are accessed by the host operating system and each container gets isolated access to these resources through segregated namespaces and control groups (cgroups). cgroups allow Docker to share available hardware resources to containers and optionally enforce limits and constraints. You can read more about this here.
Q: ­Are containers secure since they run on the same OS?­
Yes, cgroups, namespaces, seccomp profiles and the “secure by default” approach of Docker all contribute to the security of containers. Separate namespaces protects processes running within a container meaning it cannot see, and even less affect, processes running in another container, or in the host system. Cgroups help ensure that each container gets its fair share of memory, CPU, disk I/O; and, more importantly, that a single container cannot bring the system down by exhausting one of those resources. And Docker is designed to limit root access of containers themselves by default, meaning that even if an intruder manages to escalate to root within a container, it will be much harder to do serious damage, or to escalate to the host. These are just some of the many ways Docker is designed to be secure by default. Read more about Docker security and security features here. 
Docker Enterprise Edition includes additional advanced security options including role-based access control (RBAC), image signing to validate image integrity, secrets management, and image scanning to protect images from known vulnerabilities. These advanced capabilities provide an additional layer of security across the entire software supply chain, from developer’s laptop to production.
Q: ­Can a Docker image created under one OS (e.g Windows) be used to run on a different operating system (e.g RedHat 7.x)?
A: Unlike VMs, Docker containers share the OS kernel of the underlying host so containers can go from one Linux OS to another but not from Windows to Linux. So you cannot run a .NET app natively on a Linux machine, but you can run a RHEL-based container on a SUSE-based host because they both leverage the same OS kernel.
Q: Is there another advantage other than DevOps for implementing Docker in enterprise IT infrastructure?
A: Yes! Docker addresses many different IT challenges and aligns well with major IT initiatives including hybrid/multi-cloud, data center and app modernization. Legacy applications are difficult and expensive to maintain. They can be fragile and insecure due to neglect over time while maintaining them consumes a large portion of the overall IT budget. By containerizing these traditional applications, IT organizations save time and money and make these applications more nimble. For example:

Cloud portability: By containerizing applications, they can be easily deployed across different certified platforms without requiring code changes.
Easier application deployment and maintenance: Containers are based on images which are defined in Dockerfiles. This simplifies the dependencies of an application, making them easier to move between dev, test, QA, and production environments and also easier to update and maintain when needed. 62% of customers with Docker EE see a reduction in their mean time to resolution (MTTR).
Cost savings: Moving to containers provides overall increased utilization of available resources which means that customers often see up to 75% improved consolidation of virtual machines or CPU utilization. That frees up more budget to spend on innovation,

To learn more about how IT can benefit from modernizing traditional applications with Docker, check out www.docker.com/MTA.
Q: Can you explain more about how Docker EE can be used to convert apps to microservices?
A: Replacing an existing application with a microservices architecture is often a large undertaking that requires significant investment in application development. Sometimes it is impossible as it requires systems of record that cannot be replaced. What we see many companies do is containerize an entire traditional application as a starting point. They then peel away pieces of the application and convert those to microservices rather than taking on the whole application. This allows the organization to modernize components like the web interface without complete re-architecture, allowing the application to have a modern interface while still accessing legacy data.
­Q: Are there any tools that will help us manage private/corporate images? ­Can we have host our own image repository in-house vs using the cloud?
A: Yes! Docker Trusted Registry (DTR) is a private registry included in Docker Enterprise Edition Standard and Advanced. In addition, DTR provides additional advanced capabilities around security (eg. image signing, image scanning) and access controls (eg. LDAP/AD integration, RBAC). It is intended to be a private registry for you to install either in your data center or in your virtual private cloud environment.
Q: ­Is there any way to access the host OS file system(s)?  I want to put my security scan software in a Docker container but scan the host file system.
A: The best way to do this is to mount the host directory as a volume in the container with “-v /:/root_fs” so that the file system and directory are shared and visible in both places. More information around storage volumes, mounting shared volumes, backup and more are here.

Top 7 questions from #Docker 101 – Webinar recapClick To Tweet

Next Steps:

If you’re an IT professional, join our multi-part learning series: IT Starts with Docker
If you’re a developer, check out the Docker Playground 
Learn more about Docker Enterprise Edition or try the new hosted demo environment
Explore and register for other upcoming webinars or join a local Meetup

The post Docker 101: Introduction to Docker webinar recap appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

Announcing the first DockerCon Europe 2017 Speakers

Summer is flying by and DockerCon Europe 2017 (October 16-19) will be here before we know it! The DockerCon team is heads down reviewing all of the proposals submitted and we are almost ready to release a full agenda. With that, we are thrilled to share with you the DockerCon Europe 2017 Website including the first confirmed speakers and sessions.

Abby Fuller, AWS
 

Adrian Mouat, Container Solutions
 

Arun Gupta, AWS
 

 
Bret Fisher, Independent Consultant
 

 
Elton Stoneman, Docker
 

 
Nandhini Santhanam, Docker
 

 
Mike Coleman, Docker
  

Tycho Andersen, Docker
 

Learn more about DockerCon: 

Register to DockerCon Europe
Sign up to receive DockerCon News

Announcing the first @DockerCon Europe 2017 speakers cc @arungupta @adrianmouat @abbyfullerClick To Tweet

The post Announcing the first DockerCon Europe 2017 Speakers appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

IT Starts with Docker

Happy SysAdmin Day! Cheers to all of you who keep your organizations running, keep our data secure, respond at a moment’s notice and bring servers and apps back to life after a crash. Today we say, “Thank You!”

 Anniversaries are a great time to reflect on accomplishments of the last year: the projects you’ve completed, the occasions you’ve saved your company money or time, the new technology you’ve learned. In a role like IT, so much can change each year as technology progresses and becomes more challenging to stay ahead of that curve. So this SysAdmin Day, we at Docker want to congratulate your past successes and prepare you for the year to come.
Containers are not just for developers anymore and Docker is the standard for packaging all kinds of applications – Windows, Linux, traditional, and microservices. Over the next few months, we’ll be covering how SysAdmins like yourself are enabling their organizations to innovate faster while saving their companies’ money by embracing containers with Docker Enterprise Edition.
Sign up here to start your journey and learn how IT Starts with Docker. 

This multi-part series will include:

How Docker Enterprise Edition is helping IT organizations free up money for new initiatives by changing the way applications are deployed and maintained, and how customers are seeing 50-75% infrastructure savings when running containers in production.
Hands-on learning around container management and security to see how organizations are using containers across a broad spectrum of applications and infrastructure platforms.
How IT can lead the containerizing of traditional applications and gain application portability, security, efficiency in just 5 days. We’ll provide a closer look at the Modernize Traditional Applications (MTA) program that is co-delivered by Docker and our strategic partners and how you can leverage that to start your organization’s modernization efforts.
Close examination and customer stories of the key use cases for Docker Enterprise Edition to help you apply this new knowledge to your own upcoming IT projects.

Sign up today and we’ll make sure that by next year’s SysAdmin Day, you’ll be able to reflect on how Docker has helped you accomplish even more in your organization.
To get started:

Visit the Docker page for IT professionals
Begin your learning with the basics
Sign up to receive newsletter updates on this series

Start your IT journey with Docker’s new multi-part learning series. Sign up today! #SysAdminDay…Click To Tweet

The post IT Starts with Docker appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

Happy Second Birthday: A Kubernetes Retrospective

As we do every July, we’re excited to celebrate Kubernetes 2nd birthday! In the two years since GA 1.0 launched as an open source project, Kubernetes (abbreviated as K8s) has grown to become the highest velocity cloud-related project. With more than 2,611 diverse contributors, from independents to leading global companies, the project has had 50,685 commits in the last 12 months. Of the 54 million projects on GitHub, Kubernetes is in the top 5 for number of unique developers contributing code. It also has more pull requests and issue comments than any other project on GitHub.  Figure 1: Kubernetes RankingsAt the center of the community are Special Interest Groups with members from different companies and organizations, all with a common interest in a specific topic. Given how fast Kubernetes is growing, SIGs help nurture and distribute leadership, while advancing new proposals, designs and release updates. Here’s a look at the SIG building blocks supporting Kubernetes:Kubernetes has also earned the trust of many Fortune 500 companies with deployments at Box, Comcast, Pearson, GolfNow, eBay, Ancestry.com and contributions from CoreOS, Fujitsu, Google, Huawei, Mirantis, Red Hat, Weaveworks and ZTE Company and others. Today, on the second anniversary of the Kubernetes 1.0 launch, we take a look back at some of the major accomplishments of the last year: July 2016Kubernauts celebrated its first anniversary of the Kubernetes 1.0 launch with 20 #k8sbday parties hosted worldwideKubernetes v1.3 releaseSeptember 2016Kubernetes v1.4 releaseLaunch of kubeadm, a tool that makes Kubernetes dramatically easier to installPokemon Go – one of the largest installs of Kubernetes ever October 2016Introduced Kubernetes service partners program and a redesigned partners pageNovember 2016CloudNativeCon/KubeCon SeattleCloud Native Computing Foundation partners with The Linux Foundation to launch a new Kubernetes certification, training and managed service provider programDecember 2016Kubernetes v1.5 releaseJanuary 2017Survey from CloudNativeCon + KubeCon Seattle showcases the maturation of Kubernetes deploymentMarch 2017CloudNativeCon/KubeCon EuropeKubernetes v1.6 releaseApril 2017The Battery Open Source Software (BOSS) Index lists Kubernetes as #33 in the top 100 popular open-source software projectsMay 2017Four Kubernetes projects accepted to The Google Summer of Code (GSOC) 2017 programStutterstock and Kubernetes appear in The Wall Street Journal: “On average we [Shutterstock] deploy 45 different releases into production a day using that framework. We use Docker, Kubernetes and Jenkins [to build and run containers and automate development,” said CTO Marty Brodbeck on the company’s IT overhaul and adoption of containerization. June 2017Kubernetes v1.7 releaseSurvey from CloudNativeCon + KubeCon Europe shows Kubernetes leading as the orchestration platform of choiceKubernetes ranked #4 in the 30 highest velocity open source projectsFigure 2: The 30 highest velocity open source projects. Source: https://github.com/cncf/velocityJuly 2017Kubernauts celebrate the second anniversary of the Kubernetes 1.0 launch with #k8sbday parties worldwide!At the one year anniversary of the Kubernetes 1.0 launch, there were 130 Kubernetes-related Meetup groups. Today, there are more than 322 Meetup groups with 104,195 members. Local Meetups around the world joined the #k8sbday celebration! Take a look at some of the pictures from their celebrations. We hope you’ll join us at CloudNativeCon + KubeCon, December 6- 8 in Austin, TX.Celebrating at the K8s birthday party in San Francisco Celebrating in RTP, NC with a presentation from Jason McGee, VP and CTO, IBM Cloud Platform. Photo courtesy of @FranklyBrianaThe Kubernetes Singapore meetup celebrating with an intro to GKE. Photo courtesy of @hunternieldNew York celebrated with mini k8s cupcakes and a presentation on the history of cloud native from CNCF Executive Director, Dan Kohn. Photo courtesy of @arieljatib and @coreos Quebec City had custom k8s cupcakes too! Photo courtesy of @zig_max Beijing celebrated with custom k8s lollipops. Photo courtesy of @maxwell9215– Sarah Novotny, Program Manager, Kubernetes Community 
Quelle: kubernetes

Modernize Traditional Applications by Docker Webinar Recap

IT organizations continue to spend 80% of their budget on simply maintaining their existing applications while only spending 20% on innovation. That ratio has not changed over the last 10 years, and yet, there’s no shortage of pressure to innovate. Whether it comes directly from your customers asking for new features, or it comes from your management chain, the story is the same; you have to do more with less.

Thankfully, there is Modernize Traditional Applications from Docker. Where you can take your existing legacy applications, the same ones that underline your business, and make them 70% more efficient, more secure, and best of all – portable across any infrastructure. And you can do all of that, without touching a single line of the underlying application code. Sounds too good to be true right? Well, watch the recording below and you’ll see that it’s absolutely possible.

Give your legacy application modern capabilities without touching code using Docker EE by way of…Click To Tweet

Learn more about the Modernize Traditional Apps program:

Visit docker.com/mta to find out more information about getting involved
Contact Sales to see about getting your own MTA engagement
Take a look at the Docker ROI Calculator and see how much you can save

The post Modernize Traditional Applications by Docker Webinar Recap appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/