Docker Q&A on the New Compose Specification Community

Docker have created an open community for developing the Compose specification to help developers build cloud-native applications using Compose. There have been different implementations of Docker compose in order to make it work in platforms like Kubernetes or AWS ECS. But Docker wants to work with the community to provide better support and define the future of Compose. The Compose spec has been created to let people use compose in different platforms and make any new features as a first-class feature in Compose.

InfoQ recently talked to Justin Cormack, security lead at Docker, to learn more about the Compose specification community.

InfoQ: What is the Compose specification community? What type of problems is the spec looking to solve?

Justin Cormack: Originally, there was only one implementation, the Docker compose in Python. But there have been more implementations where they’ve looked at what Docker compose does and tried to copy as much of it as possible. But sometimes they’re doing different things. Even within Docker, we have three different implementations like Docker compose for Kubernetes or Swarm. So, all these implementations had to copy what we did and then try to make it work, but they didn’t get any real influence on how to implement Docker compose on different platforms.

The Compose spec is to let people use compose in different platforms and make any new features as a first-class feature in Compose, allowing the community to influence how the spec progress. We knew there were problems with running compose on Kubernetes because it does networks and volumes differently. And other platforms like AWS ECS has its implementation to interact with other AWS services. So we thought the best thing to do is to make an open spec to help people use compose within other platforms different than Docker Swarm or the desktop.

#containers #kubernetes #compose #community #docker #architecture & design #devops #development #news

What is GEEK

Buddha Community

Docker Q&A on the New Compose Specification Community

Docker Q&A on the New Compose Specification Community

Docker have created an open community for developing the Compose specification to help developers build cloud-native applications using Compose. There have been different implementations of Docker compose in order to make it work in platforms like Kubernetes or AWS ECS. But Docker wants to work with the community to provide better support and define the future of Compose. The Compose spec has been created to let people use compose in different platforms and make any new features as a first-class feature in Compose.

InfoQ recently talked to Justin Cormack, security lead at Docker, to learn more about the Compose specification community.

InfoQ: What is the Compose specification community? What type of problems is the spec looking to solve?

Justin Cormack: Originally, there was only one implementation, the Docker compose in Python. But there have been more implementations where they’ve looked at what Docker compose does and tried to copy as much of it as possible. But sometimes they’re doing different things. Even within Docker, we have three different implementations like Docker compose for Kubernetes or Swarm. So, all these implementations had to copy what we did and then try to make it work, but they didn’t get any real influence on how to implement Docker compose on different platforms.

The Compose spec is to let people use compose in different platforms and make any new features as a first-class feature in Compose, allowing the community to influence how the spec progress. We knew there were problems with running compose on Kubernetes because it does networks and volumes differently. And other platforms like AWS ECS has its implementation to interact with other AWS services. So we thought the best thing to do is to make an open spec to help people use compose within other platforms different than Docker Swarm or the desktop.

#containers #kubernetes #compose #community #docker #architecture & design #devops #development #news

Paris  Turcotte

Paris Turcotte

1617974220

Connecting with the Docker Community– Recap of Our First Community All Hands

Last week, we held our first Community All Hands and the response was phenomenal. A huge thank you to all 1,100+ people who joined. If you missed it, you can watch the recording here. You can also find answers to those questions that came in towards the end that we didn’t have time to answer here.

This all-hands was an effort to further deepen our engagement with the community and bring users, contributors and staff together on a quarterly basis to share updates on what we’re working on and what our priorities are for 2021 and beyond. The event was also an opportunity to give the community direct access to Docker’s leadership and provide a platform to submit questions and upvote those that are most relevant and important to people.

The overwhelming piece of feedback we got from attendees was that the event was too short and people would have loved to see more demos. We certainly had a packed agenda and we did our best to squeeze in as much into an hour. For our next one (in February 2021!), we’ll aim to extend the event by 30 minutes and include more live demos. We’ll also try to make it more interactive and give additional time to answer more questions. If you have any other ideas on how we can improve the all-hands and make it more engaging, don’t hesitate to send me a note on our community slack (@William).

Community events are a key pillar of our community-building strategy and we look forward to experimenting with new types of events like this one to continue pushing for more participation, openness and engagement. Onwards!

#community #community #developers #docker #docker community

Iliana  Welch

Iliana Welch

1595249460

Docker Explained: Docker Architecture | Docker Registries

Following the second video about Docker basics, in this video, I explain Docker architecture and explain the different building blocks of the docker engine; docker client, API, Docker Daemon. I also explain what a docker registry is and I finish the video with a demo explaining and illustrating how to use Docker hub

In this video lesson you will learn:

  • What is Docker Host
  • What is Docker Engine
  • Learn about Docker Architecture
  • Learn about Docker client and Docker Daemon
  • Docker Hub and Registries
  • Simple demo to understand using images from registries

#docker #docker hub #docker host #docker engine #docker architecture #api

Loma  Baumbach

Loma Baumbach

1600402920

A Chat With Docker’s New Community Manager

Community is a backbone of all sustainable open source projects and so at Docker, we’re particularly thrilled to announce that William Quiviger has joined the team as our new Head of Community.

William is a seasoned community manager based in Paris, having worked with open source communities for the past 15 years for a wide range of organizations including Mozilla Firefox, the United Nations and the Open Networking Foundation. His particular area of expertise is in nurturing, building and scaling communities, as well as developing mentorship and advocacy programs that help push leadership to the edges of a community.

To get to know William a bit more, we thought we’d ask him a few questions about his experience as a community manager and what he plans to focus on in his new role:

#community #community #william quiviger #docker

August  Murray

August Murray

1617878100

Docker Captain Take 5 - Gianluca Arbezzano

_Docker Captains are select members of the community that are both experts in their field and are passionate about sharing their Docker knowledge with others. “Docker Captains Take 5” is a regular blog series where we get a closer look at our Captains and ask them the same broad set of questions ranging from what their best Docker tip is to whether they prefer cats or dogs (personally, we like whales and turtles over here). Today, we’re interviewing Gianluca Arbezzano who has been a Docker Captain since 2016. He is a Senior Software Staff Engineer at Equinix Metal and is based in Italy. _

How/when did you first discover Docker?

At this point, it is not easy to pick a date. Four years ago I was in Dublin away from my home town near Turin. The Docker Meetup along with many other meetups were a great opportunity for nerds like me looking for new friends and to grab free pizza while having a good time. Back then I was working for a company that helps businesses move to the cloud. I saw that Docker was a powerful tool to master. Not only was Docker a useful tool and led me to meet a lot of cool people, but it also helped me to become a better open source citizen and enabled me to have some awesome experiences.

What is your favorite Docker command?

I am an old-style Docker user. Many of the new cool commands are unknown to me. One of the powerful combos I use from time to time is still “docker rm -fv $(docker ps -aq)”– I know, there are better ways! It clearly shows how powerful a good CLI tool and the UNIX philosophy are. I love buildkit, so buildx is also something I use a lot.

#community #community #developers #docker captains #docker community