Vanessa Diaz

Back By Popular Demand – Docker Pals Is Coming To Barcelona!

At DockerCon Copenhagen we launched the Docker Pals program in order to connect attendees and help them make the most out of their trip to DockerCon. Attending a conference by yourself can be intimidating and we don’t want anyone to feel that way at DockerCon! Pals get matched with a few others who are new (the “Pals”), and someone who knows their way around (the “Guide”) so that you will know someone before you arrive at the conference. So, DockerCon veterans, please consider signing up to be a Guide and help welcome those newer to DockerCon to the amazing Docker community. Participating gives you the opportunity to learn even more, grow an even bigger network, and have even more fun! Here’s what Pals had to say: “Docker Pals was an excellent opportunity to meet new Docker Captains and Community Leaders who Continue reading…

Jenny Burcio

5 Reasons to Attend DockerCon

Are you ready to get started with Docker and containers or level up your current use? Join the Docker team, the container ecosystem, contributors and maintainers, developers, IT professionals and executives at DockerCon Barcelona December 3-5. DockerCon is the must attend conference to learn, network and innovate with the container industry. Besides Barcelona being a beautiful city with delicious food, here are our top 5 reasons to attend DockerCon: Think big. Docker containers and our container platform are being used everywhere for everything. Your possibilities are endless, from sending rockets to space to literally save the earth from asteroids, to running intensive genomics analysis to find cures for diseases or keeping e-commerce running smoothly for black Friday shoppers. Come to DockerCon and imagine your digital future. Start small. The promise of containerization is big, but the sheer volume of options can Continue reading…

Karen Bajza

Docker Online Meetup #41: Deep Dive into Docker 1.12 Networking

For this week’s Docker Online Meetup, Sr. Director, Networking at Docker, Madhu Venugopal, joined us to talk about Docker 1.12 Networking and answer questions. Starting with Docker 1.12, Docker has added features to the core Docker Engine to make multi-host and multi-container orchestration simple to use and accessible to everyone. Docker 1.12 Networking plays a key role in enabling these orchestration features. In this online meetup, we learned all the new and exciting networking features introduced in Docker 1.12: Swarm-mode networking Routing Mesh Ingress and Internal Load-Balancing Service Discovery Encrypted Network Control-Plane and Data-Plane Multi-host networking without external KV-Store MACVLAN Driver   The number of questions Madhu got at the end of the online meetup was amazing and because he did not have time to answer all of them, we’ve added the rest of the Q&A below: Q: Will you address Continue reading…

Jana Radhakrishnan

Docker Networking Design Philosophy

From the experimental networking in Docker 1.7 to the initial release in Docker 1.9, the reception from the community has been fantastic! First of all we want to thank you for all the discussions, evaluations, PRs and filed issues. As the networking capabilities evolving with every release, we wanted to spend some time explaining the guiding principles behind the design.

Get the Latest Docker News by Email

Docker Weekly is a newsletter with the latest content on Docker and the agenda for the upcoming weeks.

Docker Core Engineering

Docker 1.10: New Compose file, improved security, networking and much more!

We’re pleased to announce Docker 1.10, jam-packed with stuff you’ve been asking for. It’s now much easier to define and run complex distributed apps with Docker Compose. The power that Compose brought to orchestrating containers is now available for setting up networks and volumes. On your development machine, you can set up your app with multiple network tiers and complex storage configurations, replicating how you might set it up in production. You can then take that same configuration from development, and use it to run your app on CI, on staging, and right through into production. Check out the blog post about the new Compose file to find out more.

Chris Hines

Webinar Q&A: Docker Networking

Many enterprises have moved from monolithic to microservices architectures, and are using Docker to help manage these services. With loosely coupled services existing in multiple containers, these containers must be able to communicate with one another, and sometimes even exist in multiple networks at a time. Docker makes this extremely easy for developers and IT operations teams. We have found that enterprises today are using Docker and our pluggable architecture (plugins with Microsoft, Cisco, Vmware, Weave, and other) for multi-segmentation, multi-tenancy, as well as cloud portability.

Victor Coisne

Docker Online Meetups #28 and #29: Production-Ready Docker Swarm and Docker Networking is Now GA

This week, we hosted two Docker Online Meetups. The first on Wednesday featured Alexander Beslic presenting on production-ready Swarm. For the second one on Thursday, Madhu Venugopal discussed the recently-GA Docker Networking. Below are the recorded videos and slides from both presentations.  

Ben Firshman

Announcing Docker 1.9: Production-ready Swarm and Multi-host Networking

Today we’re releasing Docker 1.9 – and it’s a big one. Docker Swarm and multi-host networking are production-ready, Docker Engine has a new volume management system, and Docker Compose has much better support for multiple environments. These in combination establish the foundation for scaling your distributed apps in production. Containerization is changing how you build infrastructure, and you need to use the right tools for the job. Docker Swarm turns your infrastructure into a single pool of resources for running your distributed apps, but all of the containers that are part of those apps need managing somehow. And they all probably need to talk to each other. And some of them probably need to store data somewhere. In a world where a container could be running on any host in your infrastructure, this is a difficult thing to manage.