Kategorie: Kubernetes

What developers need to know about Docker, Docker Engine, and Kubernetes v1.20

The latest version of Kubernetes Kubernetes v1.20.0-rc.0 is now available. The Kubernetes project plans to deprecate Docker Engine support in the kubelet and support for dockershim will be removed in a future release, probably late next year. The net/net is support for your container images built with Docker tools is not being deprecated and will still work as before.

What does this mean for you if you use Docker and Kubernetes?

First of all, don’t panic Developers can still use the Docker platform to build, share, and run containers on Kubernetes! This change primarily impacts operators and administrators for Kubernetes and doesn’t impact developer work flows. The images Docker builds are compliant with OCI (Open Container Initiative), are fully supported on containerd, and will continue to run great on Kubernetes.

If you’re using Docker, you’re already using containerd. We build Docker’s runtime upon containerd while providing a great developer experience around it. For production environments that benefit from a minimal container runtime, such as Kubernetes, and may have no need for Docker’s great developer experience, it’s reasonable to directly use lightweight runtimes like containerd.

Docker created the containerd project, along with Google and IBM, in 2016, with the goal of this transition in mind. The deprecation of docker-shim (and Docker Engine as runtime) marks the completion of a long-term commitment to provide a modern runtime for Kubernetes. Containerd was created as a core low-level, extensible runtime for both Docker and Kubernetes to each use in the most appropriate way.

Containerd was donated to the CNCF in 2017, and has grown to incorporate the containerd CRI project to interface with Kubernetes, as well as seeing a host of innovation and investment from across the industry, including from Amazon, Google, Microsoft and IBM.

In 2019 it became a graduated CNCF project, the highest project level, showing its maturity and it remains the only container runtime with this status. Over the last few years the leading Kubernetes service providers such as AWS and Google have migrated to Containerd as their Kubernetes runtime. This process of depreciation now reflects the great success of this work, and of the thriving community around containerd.

Support for your container images built with Docker tools is not being deprecated.

Container images you build using Docker tools will continue to run on Kubernetes. Buildkit, our next generation build infrastructure, has a flexible architecture so that while it can be used as the builder with Docker, it can also talk directly to containerd or runc instead for use in infrastructure where Docker might not be available.

Docker is committed to containerd development: we will continue to further invest, along with the growing buildkit community, in helping you use Docker builds wherever and however your infrastructure is hosted.

You can continue to build and run Docker images locally and in your Kubernetes cluster as this deprecation will not impact that experience.

What is the Kubernetes project deprecating then?

Kubernetes is deprecating dockershim, which is a component in Kubernetes’ kubelet implementation, communicating with Docker Engine. Arnaud Porterie had some great thoughts on this that he shared here.

The Kubernetes project has also published this FAQ.  Kat Cosgrove did a great job explaining the changes very simply here.

Do you need to take action?

Today, and in Kubernetes v1.20, Kubernetes administrators can continue to use docker commands and kubectl commands to manage their Kubernetes clusters.

In a future release of Kubernetes, a few minor releases from now, when support for dockershim is eventually removed, you will no longer be able to use docker commands to inspect your cluster. 

Many of these commands have similar commands in kubectl and ctr (the containerd CLI).  While the commands to inspect your cluster in Kubernetes may change in the future, Developers will still be able to use Docker tools to docker build, docker push and docker run containers and container images on Kubernetes.  

Further Background

KEP-1985: Kubernetes Enhancement Proposal to remove dockershim from Kubelet

Questions? Feedback?

Please reach out on Docker’s slack if you have questions or other feedback. 
The post What developers need to know about Docker, Docker Engine, and Kubernetes v1.20 appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

Join Docker’s Community All-Hands

Openness and transparency are key pillars of a healthy open source community. We’re constantly exploring ways to better engage the Docker community, to better incorporate feedback and to better foster participation.

To this end, we’re very excited to host our first Community All-Hands on Thursday December 10th at 8am PST / 5pm CET. This one-hour event will be a unique opportunity for Docker staff and the broader Docker community to come together for company and product updates, live demos, community shout-outs and a Q&A. 

The All-Hands will include updates from:

Scott Johnston (CEO, Docker) who will go over Docker’s strategic vision and where the company is heading in 2021 and beyondDonnie Berkholz (VP of Products, Docker) who will walk us through our product roadmap  Jean-Laurent de Morlhon (VP of Engineering, Docker) who will provide an inside peek on engineering.

We’ll then dive into specific product updates around Docker Desktop, Hub and Developer Tooling, followed by two awesome live demos where we’ll show cool new features and integrations. 

A Community All-Hands is not complete without a community update. We will announce new community initiatives and recognize outstanding contributors who have gone above and beyond to help push Docker forward.

Do you have a question for Docker? Ask away!

We know many in the community have lots of questions but don’t always know where to ask them. Worry not, now’s your opportunity to submit any question you have and up-vote your favorite ones from the community. You can submit your questions anonymously (if you prefer) and we’ll make a selection of the most up-voted ones to be answered during the live Q&A. 

We’re really excited about this All-Hands and we hope to bring together as many people from the community from as many parts of the world as possible. Of course, finding the perfect time for this is impossible and a large chunk of the community won’t be able to dial-in so we’ll make sure to share the recording shortly after the event. As mentioned, this is experimental territory for us and we’ll be trying out different formats and time zones for future All-Hands, incorporating feedback from the community along the way.

See you next week!

Click here to register for the event.

Submit your questions here for the live Q & A 
The post Join Docker’s Community All-Hands appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

The Docker Developer Guide to AWS re:Invent

This is the busiest time of the year for developers targeting AWS. Just over a week ago we announced the GA of Docker Compose for AWS, and this week we’re getting ready to virtually attend AWS re:Invent. re:Invent is the annual gathering of the entire AWS community and ecosystem to learn what’s new, get the latest tips and tricks, and connect with peers from around the world. Instead of the traditional week-long gathering of 60,000 attendees in Las Vegas, the event has pivoted to a flexible three-week online conference. This year the event is free, and anyone can participate on their own schedule. This blog post covers highlights of the event so Docker developers can get the most from re:Invent.

In the kickoff keynote by CEO Andy Jassy, AWS announced a number of new features for container developers, including a new capability, ECS Anywhere, which allows Amazon Elastic Container Service (ECS) to run on-prem and in the cloud to support hybrid computing workloads as well as the launch of AWS Proton, an end-to-end pipeline to deliver containerized and microservices applications. Separately, AWS also announced a new public Elastic Container Registry (ECR) and gallery today. We’re excited to see a cloud leader like AWS validate our approach to build, share, and run apps using container-based images, and it’s great for AWS-focused developers to have choices.

Developers want freedom of choice, and we’re proud that our container registry model is not only validated by AWS, but also by millions of organizations including industry leaders such as Canonical/Ubuntu, Apache, CNCF, and Google Istio. They all use Docker Hub to efficiently distribute images to the millions of Docker developers. The numbers are staggering–for projects such as Ubuntu/Canonical, the number of images served by Hub measures in the billions. For open source projects and Docker commercial partners, any pull requests made by developers can be initiated without rate limits for free and paid subscribers. Our “who’s who” of open source and commercial software publishers gives developers the choices they need to confidently innovate with velocity and underscores our commitment to the developer ecosystem. 

Over the next three weeks, re:Invent has a number of interesting sessions for Docker developers. Here are some of the sessions we’ll be attending:

Infrastructure Keynote

THURSDAY, DEC. 10, 8:00 AM – 9:20 AM (PST)

Live from Seattle, join Peter DeSantis, senior vice president of Global Infrastructure and Customer Support, to learn how AWS has optimized its cloud infrastructure to run some of the world’s most demanding workloads and give your business a competitive edge.

Leadership Deep Dive on Containers with Deepak Singh

THURSDAY, DEC. 10, 10:45 AM – 11:45 AM (PST)

Hear directly from AWS leaders as they share the latest advances in AWS technologies, set the future product direction, and motivate you through compelling success stories. Stay tuned for updates and more information on Leadership Sessions.

Werner Vogels Keynote

TUESDAY, DEC. 15, 8:00 AM – 9:30 AM (PST)

Join Dr. Werner Vogels as he goes behind the scenes to show how Amazon is solving today’s hardest technology problems. Based on his experience working with some of the largest and most successful applications in the world, Dr. Vogels shares his insights on building truly resilient architectures and what that means for the future of software development.

Containers at AWS: More options and power than ever before

WEDNESDAY, DEC 16, 1:15 PM – 1:45 PM (PST)

Are you confused by the many choices of container services that you can run on AWS? This session explores all your options and the advantages of each. Whether you are just beginning to learn Docker or are an expert with Kubernetes, join this session to learn how to pick the right services that would work best for you.

You can sign up for these sessions and peruse the entire schedule for re:Invent at their agenda page. 

And finally, in honor of re:Invent week, our Developer Advocate Peter McKee has created a list of the best Docker resources for AWS developers. You can check out the list (and register for his upcoming appearance on the AWS “Howdy Partner” webinar during re:Invent) at his blog post. Peter’s resources will help you learn some new skills and a couple of “I didn’t know you could do that” insights into AWS development with the Docker platform.

We’ll “see” you all at re:Invent over the next few weeks!
The post The Docker Developer Guide to AWS re:Invent appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/