Attend a #LearnDocker Workshop This Fall

Join a Docker for Developers Workshop Near You
From October through December, Docker User Groups all over the world are hosting a workshop for their local community! Join us for an Introduction to Docker for Developers, a hands-on workshop we run on Play with Docker. 
This Docker 101 workshop for developers is designed to get you up and running with containers. You’ll learn how to build images, run containers, use volumes to persist data and mount in source code, and define your application using Docker Compose. We’ll even mix in a few advanced topics, such as networking and image building best-practices. There is definitely something for everyone! 
Visit your local User Group page to see if there is a workshop scheduled in your area. Don’t see an event listed? Email the team by scrolling to the bottom of the chapter page and clicking the contact us button. Let them know you want to join in on the workshop fun! 
Join the Docker Virtual Meetup Group
Don’t see a user group in your area? Never fear, join the virtual meetup group for monthly meetups on all things Docker.  

The #LearnDocker for #developers workshop series is coming to a city near you! Learn more on our blog:Click To Tweet

To find out more about Docker for developers:

Read about Docker Developer Tools, including Docker Desktop Enterprise.
Download Docker Desktop for Windows or Mac.

The post Attend a #LearnDocker Workshop This Fall appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

Women in Tech Week Profile: Renee Mascarinas

We’re continuing our celebration of Women in Tech Week into this week with another profile of one of many of the amazing women who make a tremendous impact at Docker – this week, and every week – helping developers build modern apps.

Renee Mascarinas is a Product Designer at Docker. You can follow her on Twitter @renee_ners.

What is your job?
Product Designer. 

How long have you worked at Docker?
11 months.

Is your current role one that you always intended on your career path? 
The designer part, yes. But the software product part, not necessarily. My background is in architecture and industrial design and I imagined I would do physical product design. But I enjoy UX; the speed at which you can iterate is great for design.

What is your advice for someone entering the field?
To embrace discomfort. I don’t mean that in a bad way. A mentor once told me that the only time your brain is actually growing is when you’re uncomfortable. It has something to do with the dendrites being forced to grow because you’re forced to learn new things.

Tell us about a favorite moment or memory at Docker or from your career? 
There’s so many, but one that stood out was my visit to the Docker Paris office. It wasn’t so much about going to Paris, which was amazing. It was more about the bonding experience with the product team. It was my third week at Docker and I was forced to learn quickly about applications for our enterprise distribution offering.  I have a long list of favorite people from Docker, and most of them were from that trip.

What are you working on right now that you are excited about?
Enhancing the UX in Docker Hub. There’s so much work being done and released, it’s super exciting!  I have always worked on products that aren’t quite a SaaS offering so user feedback can sometimes be limited.  With Hub, you can dig up opinions from Twitter and Reddit, and feedback is collected in GitHub.  

What do you do to get “unstuck” on a really difficult problem/design/bug?
I do competitive and comparative analysis on a similar product on their UX workflows.  I like to review some of my findings with colleagues to see if I’m on the right path. 
What is your superpower?
I am a super planner. If I’m going on a vacation, there will be an itinerary. I think it was a coping mechanism growing up to defend against my bossy older brother. 

What is your definition of success?
Success in a project is when I’ve reached a level of contentment that I’m not up at night still thinking about it. And everything can be a project, I set a lot of goals to challenge myself and attribute success to achieving goals.

What are you passionate about?
Problem solving. It’s very egotistical but I like to challenge myself to see if I have what it takes to figure things out.

What is something you love to do? And something you dislike?
I love teaching myself new skills., I am a YouTubeyoutube DIY junkie. I hate indecision. 

Share a story about something or someone who has been very impactful on your life or career?
My calculus teacher was really passionate about the subject and it made me passionate as well. I ended up tutoring calculus to high school students for four years because I wanted them to love calculus too.

.@renee_ners shares her experience being a Product Designer at Docker. #WomenInTechWeekClick To Tweet

The post Women in Tech Week Profile: Renee Mascarinas appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

Designing Your First App in Kubernetes: An Overview

Kubernetes is a powerful container orchestrator and has been establishing itself as IT architects’ container orchestrator of choice. But Kubernetes’ power comes at a price; jumping into the cockpit of a state-of-the-art jet puts a lot of power under you, but knowing how to actually fly it is not so simple. That complexity can overwhelm a lot of people approaching the system for the first time.
I wrote a blog series recently where I walk you through the basics of architecting an application for Kubernetes, with a tactical focus on the actual Kubernetes objects you’re going to need. The posts go into quite a bit of detail, so I’ve provided an abbreviated version here, with links to the original posts.

Part 1: Getting Started 

Just Enough Kube
With a machine as powerful as Kubernetes, I like to identify the absolute minimum set of things we’ll need to understand in order to be successful; there’ll be time to learn about all the other bells and whistles another day, after we master the core ideas. No matter where your application runs, in Kubernetes or anywhere else, there are four concerns we are going to have to address:

Processes: In Kubernetes, that means using pods and controllers to schedule, maintain and scale processes.
Networking: Kubernetes services allow application components to talk to each other.
Configuration: A well-written application factors out configuration, rather than hard-coding it. In Kubernetes, volumes and configMaps are our tools for this.
Storage: Containers are short-lived, so data you want to keep should be stored elsewhere. For this, we’ll look at Container Storage Interface plugins and persistentVolumes.

Just Enough Design
There are some high-level design points we need so we can understand the engineering decisions that follow, and to make sure we’re getting the maximum benefit out of our containerization platform. Regardless of what orchestrator we’re using, there are three key principles we need to keep in mind that set a standard for what we’re trying to achieve when containerizing applications: portability, scalability, and shareability. Containerization is fundamentally meant to confer these benefits to applications; if at any time when you’re containerizing an app and you aren’t seeing returns in these three areas, something may well need to be rethought.
For more information on Kubernetes and where to start when using them to develop an application, check out Part 1 of our series.
Part 2: Setting up Processes
The heart of any application is its running processes, and in Kubernetes, we create processes as pods, which are used to schedule groups of individual containers. Pods are a bit fancier than individual containers, in that they can schedule whole groups of containers, co-located on a single host, which brings us to our first decision point — How should our processes be arranged into pods?

A pod can contain one or more containers, but containers in the pod must scale together.

There are two important considerations for how we set up pods:
Pods and containers must scale together. If you need to scale your application up, you have to add more pods; these pods will come with copies of every container they include. 
Kubernetes controllers are the best way to schedule pods, since controllers like deployments or daemonSets provide numerous operational tools for scaling and maintenance of workloads beyond what’s offered by bare pods.
To learn more about setting up processes for managing your applications, check out Part 2 of our series. 
Part 3: Communicating via Services
After deploying workloads as pods managed by controllers, you have to establish a way for those pods to reliably communicate with each other without incurring a lot of complexity for developers.
That’s where Kubernetes services come in. They provide reliable, simple networking endpoints for routing traffic to pods via the fixed metadata defined in the controller that created them. For basic applications, two services cover most use cases: clusterIP and nodePort services. That brings us to another decision point: What kind of services should route to each controller?
The simplest way to decide between them is to determine whether the target pods are meant to be reachable from outside the cluster or not.

A Kubernetes nodePort service allows external traffic to be routed to the pods
A Kubernetes clusterIP service only accepts traffic from within the cluster.

You can learn more about communication via Kubernetes services and how to decide between clusterIP and nodePort services in Part 3 of our series. 
Part 4: Configuration
One of the core design principles of any containerized app is portability. When you build an application with Kubernetes, you’ll want to address any problems with the environment-specific configuration expected by that app.
A well-designed application should treat configuration like an independent object — separate from the containers themselves and provisioned to them at runtime. When we design applications, we need to identify what configurations we want to make pluggable in this way — which brings us to another decision point:
What application configurations will need to change from environment to environment?
Typically, these will be environment variables or config files that change from environment to environment, such as access tokens for different services used in staging versus production or different port configurations.
Once we’ve identified the configs in our application that should be pluggable, we can enable the behavior we want by using Kubernetes’ system of volumes and configMaps.

The configMap and Volume interact to provide configuration for containers.

You can read more about configuration in Part 4 of the series.
Part 5: Storage
The final component we want to think about when we build applications for Kubernetes is storage. Remember, a container’s filesystem is transient, and any data kept there is at risk of being deleted along with your container if that container ever exits or is rescheduled. 
Any container that generates or collects valuable data should be pushing that data out to stable external storage; conversely, any container that requires the provisioning of a lot of data should be receiving that data from an external storage location. 
Which brings us to our last decision point: What data does your application gather or use that should live longer than the lifecycle of a pod?
Tackling that requires working with the Kubernetes storage model. The full model has a number of moving parts: The Container Storage Interface (CSI) Plugins, StorageClass, PersistentVolumes (PV), PersistentVolumeClaims (PVC), and Volumes.

To learn more about how to leverage the Kubernetes storage model for your applications, be sure to check out Part 5 of the series. 
The Future
I’ve walked you through the basic Kubernetes tooling you’ll need to containerize a wide variety of applications, and provided you with next-step pointers on where to look for more advanced information. Try working through the stages of containerizing workloads, networking them together, modularizing their config, and provisioning them with storage to get fluent with the ideas above.
After mastering the basics of building a Kubernetes application, ask yourself, “How well does this application fit the values of portability, scalability and shareability we started with?” Containers themselves are engineered to easily move between clusters and users, but what about the entire application you just built? How can we move that around while still preserving its integrity and not invalidating any unit and integration testing you’ll perform on it?
Docker App sets out to solve that problem by packaging applications in an integrated bundle that can be moved around as easily as a single image. Stay tuned to Docker’s blog for more guidance on how to use this emerging format with your Kubernetes applications.
To learn more about Kubernetes and Docker:

Find out more about running Kubernetes on Docker Enterprise and Docker Desktop.
Check out Play with Kubernetes, powered by Docker.

We will also be offering training on Kubernetes starting in early 2020. In the training, we’ll provide more specific examples and hands on exercises.To get notified when the training is available, sign up here:
Get Notified About Training

Building Your First App in #Kubernetes – a summary of our 5 part blog seriesClick To Tweet

The post Designing Your First App in Kubernetes: An Overview appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

Women in Tech Week Profile: Clara McKenzie

We’re continuing our celebration of Women in Tech Week with another profile of one of many of the amazing women who make a tremendous impact at Docker – this week, and every week – helping developers build modern apps.
Clara McKenzie (center) is a Support Escalation Engineer.

What is your job?
SEG Engineer (Support Escalation Engineer).

How long have you worked at Docker?
4 months.

Is your current role one that you always intended on your career path? 
The SEG role is a combination that probably doesn’t exist as a general rule. I’ve always liked to support other engineers and work cross-functionally, as well as unravel hard problems, so it’s a great fit for me.

What is your advice for someone entering the field?
The only thing constant about a career in tech is change. When in doubt, keep moving. By that, I mean keep learning, keep weighing new ideas, keep trying new things.  

Tell us about a favorite moment or memory at Docker or from your career? 
In my first month at Docker, we hosted a summer cohort of students from Historical Black Colleges who were participating in a summer internship. As part of their visit a few of us were asked to share our insights about working in tech, career paths with a BS in engineering, and how different roles work together to build and release a product. My colleagues Savaugn and Shanea were able to give them deeply personal and practical advice. I was able to give them the advice I’d give my own children who are just a bit ahead of them in their career. The students had lots of questions and it was a really nice event.

What are you working on right now that you are excited about?
There is so much for me to learn at Docker. I wasn’t familiar with the Enterprise products when I arrived.  Now I’m learning mostly DTR and UCP from both inside and out. Escalations keep you on your toes. It’s a unique experience to hear the client dilemmas and piece together the story. Was this an unintended consequence, a bug? How did we get here? And more importantly, how are we going to address it?

What do you do to get “unstuck” on a really difficult problem/design/bug?
I ask my colleagues! This happens quite often – these are hard problems. It takes the skills sets both Support and Product to solve escalations.  You need to know what to ask the clients for in terms of logs and debugging data, sometimes issues get solved just in the process of doing that. 

What is your superpower?
Persistence.

What is your definition of success?
Happiness.

What are you passionate about?
I love dogs. I enjoy genealogy, puzzles, and I like volunteering. I was on the board of Berkeley Ballet Theater as Treasure for a while; that was really rewarding. My husband and I collect and sometimes race old Volkswagens too, which is a lot of fun.

What is something you want non-women in tech to know?
We have not yet created the level playing field we all want, one where we get the best out of everyone.  It’s complicated but we can make strides. Docker can be the kind of workplace you refer back to your entire career as the way things should be done.

Who do you look up to?
Leaders who take risks for the greater good: Martin Luther King Jr., Ruth Bader Ginsburg, Mahatma Gandhi.

What is something you love to do? And something you dislike?
I love hanging out with my family.  And I hate sitting in traffic.

Share a story about something or someone who has been very impactful on your life or career.
A director I had in a very successful startup I was at,  would say “Success is failing less than the next guy”. He also showed me how to take everything in stride, the good and the bad, which was good because there was a lot of rolling with the punches on that job. The company was acquired for a lot of money and we all remember it with pride and exhaustion.

Clara McKenzie, Docker Support Escalation Engineer, on her career and why you always need to be learning. #WomeninTechWeekClick To Tweet

The post Women in Tech Week Profile: Clara McKenzie appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

Women in Tech Week Profile: Amn Rahman

We’re continuing our celebration of Women in Tech Week with another profile of one of many of the amazing women who make a tremendous impact at Docker – this week, and every week – helping developers build modern apps. 
Amn Rahman is a Data Engineer. You can follow her on Twitter @amnrahman.

What is your job?
I work as a data engineer – building and maintaining data pipelines and delivery tools for the entire company. 

How long have you worked at Docker?
2 years. 

Is your current role one that you always intended on your career path? 
Not quite! As a teenager, I wanted to become a cryptographer and spent most of my time in undergrad and grad school on research in privacy and security. I eventually realized I liked working with data and was pretty good at dealing with databases, which pushed me into my current role. 

What is your advice for someone entering the field?
Become acquainted with the entire data journey and try to pick up one tool or language for each phase. For example, you may choose to use Python to fetch and transform data from an API and load it in a MySQL database and then expose the data using a BI tool like Tableau.  In the process, you’ll develop a mental model for a data pipeline and will be able to categorize each new tool or pipeline you come across. 
Never be afraid to ask questions and do not get overwhelmed by all that is out there! When applying for jobs, do not worry about meeting 100% of the qualifications!

Tell us about a favorite moment or memory at Docker or from your career? 
Delivering a live demo in the Dockercon keynote! 

What are you working on right now that you are excited about?
I’m working on various exciting projects right now: helping Customer Success in efficiently tracking customer requests and support backlog, providing analytics to HR to track diversity, and surfacing product telemetry for product managers.  

What do you do to get “unstuck” on a really difficult problem/design/bug?
There’s a running joke in my team that I simply sleep on it! I’ve woken up many times with solutions and bug fixes in my head. Sometimes I just like to step away from my computer and phone and just grab a pen and paper or attack a whiteboard and go through the problem step by step. We get so caught up in jumping from one task to the next that we forget to make time for deep reflection. It’s usually in moments like these that I find answers to problems bugging me. 

What is your superpower?
Making people laugh at ridiculous jokes! On a more serious note, communication. 

What is your definition of success?
Bringing a positive impact to lives other than yours. 

What are you passionate about?
Tech for social good, mentoring women in tech and female students, promoting more mindfulness in the use of technology, standing against addictive and biased design patterns and algorithms, creating inclusive spaces and communities. 

Who do you look up to?
Abdul Sattar Edhi – one of the greatest humanitarians to walk the earth. He spent his entire life dedicated to serving the poor and the ill through the world’s largest volunteer run ambulance network and shelters. 

What is something you love to do? And something you dislike?
I love to build stuff whether it’s assembling IKEA furniture or geeking out on an Arduino. I also love to read poetry! And I have an intense dislike for washing dishes! 

Share a story about something or someone who has been very impactful on your life or career?
My undergrad advisor, Dr. Fareed Zaffar at the Lahore University of Management Sciences pushed me into applying to graduate schools when I had no plans of doing so and didn’t believe in myself. I ended up getting accepted by some of the most prestigious universities in the world and I owe him a great deal for being where I am today. He continues to be a mentor who I regularly reach out to for advice.
The post Women in Tech Week Profile: Amn Rahman appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

Women in Tech Week Profile: Jenny Fong

We’re continuing our celebration of Women in Tech Week with another profile of one of many of the amazing women who make a tremendous impact at Docker – this week, and every week – helping developers build modern apps. 

Jenny Fong is a Senior Director of Product Marketing at Docker. Follow her on Twitter @TechGalJenny.

What is your job? 
Senior Director of Product Marketing.

How long have you worked at Docker? 
2 ½ years.

Is your current role one that you always intended on your career path? 
Nope! I studied engineering and started in a technical role at a semiconductor company. I realized there that I really enjoyed helping others understand how technology works, and that led me to Product Marketing! What I love about the role is that it’s extremely cross-functional. You work closely with engineering, product management, sales and marketing, and it requires both left brain and right brain skills. My technical background helps me to understand our products, while my creative side helps me communicate our products’ core value propositions. 

What is your advice for someone entering the field?
It’s always good to be self-aware. Know your strengths and weaknesses, and look for opportunities that align to your strengths or give you a chance to work on areas you wish to develop. You’ll be able to shine and you’ll be happier too!

Tell us about a favorite moment or memory at Docker or from your career? 
My second week at Docker was DockerCon in Austin in 2017. I met a few of our customers who were speaking at the event, and they spoke with such passion and excitement about the projects they led and the outcomes they delivered to their organizations. I knew I had made the right decision to join Docker at that moment.

What do you do to get “unstuck” on a really difficult problem/design/bug?
I love using analogies! If you can’t wrap your head around a new problem, is it similar to any other problems? The analogy can sometimes help you test some ideas – if it’s true for the analogy, is it true for your particular problem? 
What is your superpower? 
Puzzles! I love solving puzzles – both literal ones (I’m a daily NY Times crossword solver and always love a good jigsaw puzzle), and business ones (launching a new product to a new market). 

What is your definition of success?
Beyond job titles and awards, I think success is when you’ve helped someone else. That could be helping them to do their job faster, helping them learn about something new, helping them close the deal or finish the project. When you help someone else, you’re impacting her or his life, and that is very rewarding. 

From #engineering to marketing, discover @TechGalJenny’s career transformation journey.Click To Tweet

The post Women in Tech Week Profile: Jenny Fong appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

Docker Enterprise: The First DISA STIG’ed Container Platform!

Docker Enterprise was built to be secure by default. When you build a secure by default platform, you need to consider security validation and governmental use. Docker Enterprise has become the first container platform to complete the Security Technical Implementation Guides (STIG) certification process. Thanks to Defense Information Systems Agency (DISA) for its support and sponsorship. Being the first container platform to complete the STIG process through DISA means a great deal to the entire Docker team.
The STIG took months of work around writing and validating the controls. What does it really mean? Having a STIG allows government agencies to ensure they are running Docker Enterprise in the most secure manner. The STIG also provides validation for the private sector. One of the great concepts with any compliance framework, like STIGs, is the idea of inherited controls.  Adopting a STIG recommendation helps improve an organization’s security posture. Here is a great blurb from DISA’ site:

The Security Technical Implementation Guides (STIGs) are the configuration standards for DOD IA and IA-enabled devices/systems. Since 1998, DISA has played a critical role enhancing the security posture of DoD’s security systems by providing the Security Technical Implementation Guides (STIGs). The STIGs contain technical guidance to “lock down” information systems/software that might otherwise be vulnerable to a malicious computer attack.

This GCN article also makes a good point about using the STIG as a security baseline:

If you look at any best practice guidance, regulation or standards around effective IT security out on the market today, you will see that it advises organizations to ensure their computing systems are configured as securely as possible and monitored for changes.
If you look at any best practice guidance, regulation or standards around effective IT security out on the market today, you will see that it advises organizations to ensure their computing systems are configured as securely as possible and monitored for changes.

What STIG Means for Docker’s Customers
So what’s in the STIG? STIGs are formatted in xml and require the STIG viewer to read. The STIG viewer is a custom GUI written in Java (see DISA’s page on STIG Viewing tools for more). Specifically you can find the latest DISA STIG Viewer here.

The Docker Enterprise STIG can be found here: Docker Enterprise 2.x Linux/UNIX STIG – Ver 1 Rel 1  (You will need to unzip it). Although the current STIG calls out Docker Enterprise 2.x, it absolutely applies to Docker Enterprise 3.X!

Lets dig into the STIG itself. There is some good information about the STIG and DISA’s authority from Overview pdf.
From the STIG itself there are only 100 controls.  For the uninitiated, a control is config that needs to be checked and possibly changed. This is the real meat and potatoes for the System Administrators.
Here is the breakdown:

Category
Controls

CAT 1
23

CAT 2
72

CAT 3
5

Total
100

CAT 1 controls are the most important controls to pay attention to. As you can see there are only 23 CAT 1, and the bulk of those controls are “what not to do” controls — checks to ensure an undesirable situation is not occurring. With only 100 total controls, there is not a lot of work to do to harden Docker Enterprise.
The STIG will be updated as often as needed. We want to ensure that all our customers and partners have access to the latest security information around Docker Enterprise.
Why STIG Matters to Docker
We are thankful to our sponsors within DISA that paved the way for us to be accepted into the STIG process and complete it. The primary goal of the Docker Public Sector team is to provide technology that serves those who serve our country. Completing the STIG process was a big step for us in gaining a level of trust necessary to fulfill that goal. 
We have always felt that new technology like Docker is tangibly valuable to production enterprise and mission environments only if we do our due diligence with security through the certifications and evaluations that are required for our technology to be approved and used safely in real world environments.

Exciting news! #Docker Enterprise is the first container platform to complete the @USDISA Security Technical Implementation Guides (STIG) certification process.Click To Tweet

To learn more about why Docker Enterprise is secure by default:

Take a look at our Security Reference Architecture.
Read about our solutions for Government .

Watch the Docker Enterprise 3.0 webinar series to see a demo of built-in features that are designed to provide enterprise-grade security without slowing down your organization.
Chris Cyrus, Director Enterprise Sales at Docker, also contributed to this blog post.
The post Docker Enterprise: The First DISA STIG’ed Container Platform! appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

Women in Tech Week Profile: Anusha Ragunathan

It’s Women in Tech Week, and we want to take the opportunity to celebrate some of the amazing women who make a tremendous impact at Docker – this week, and every week – helping developers build modern apps.

Anusha Ragunathan is a Software Engineer at Docker. You can follow her on Twitter @AnushaRagunatha.

What is your job?
Software Engineer. I build systems, write and review code, test and analyze software. I’ve always worked on infrastructure software both at and before Docker. I participate in Moby and Kubernetes OSS projects. My current work is on persistent storage for Kubernetes workloads and integrating it with Docker’s Universal Control Plane. I also enjoy speaking at technical conferences and writing blogs about my work. 
How long have you worked at Docker?
 4 years and 1 month!

Is your current role one that you always intended on your career path? 
Yes, I’ve always been on this path. In my high school, we had the option to take biological sciences or Computer Sciences (CS). I chose CS and since then that has been my path. I earned both my bachelors’ and master’s degrees in CS.

What is your advice for someone entering the field?
If you love problem solving and enjoy learning a new system, building on top of it, observing it, reverse engineering it – if any of this excites you – give software engineering a shot.  It’s not just about writing code. It’s not just about learning new languages, frameworks and tools, it’s about having a holistic view of how things work together. Pursue a career in engineering if you have this inclination. And be brave! It can sound scary, but its not. It’s a set of machines that you need to understand. More you do it, the better you get at it.

Tell us about a favorite moment or memory at Docker or from your career? 
All the DockerCons! I get a huge high attending and watching the keynotes and announcements. 
My first year at Docker was also memorable. I didn’t come from an Open Source background. I have such fond memories of how welcoming everyone was at Docker. Arnaud Porterie, Solomon Hykes and many of the engineers who I still work with, Sebastiaan van Stijn, Tonis Tiigi, Tibor Vass, Michael Crosby were very welcoming and very eager to help – there was a great camaraderie.

What are you working on right now that you are excited about?
Kubernetes. It is a project that has a lot going on from both a community contribution as well as the feature set it carries every release. It’s a great project to be involved with, especially given its wide adoption. According to https://octoverse.github.com/projects.html, it’s in the top 10 OSS projects. It can be chaotic as well, but if you have a focus and a few specific projects to follow, it’s a great community to learn from and contribute to.

What do you do to get “unstuck” on a really difficult problem/design/bug?
Whether it’s a technical, team or business problem, the first thing I always tell myself or advise colleagues is simply “do not panic.” Then methodically, I try to see if any of my prior knowledge can be applied to this new problem and if I can connect the dots.
If that doesn’t work, then you try new things. If its a technical problem you can look things up, or try to understand the system more by focusing on observability, it’s very measurable, you just have to methodical.
If it is a team problem or a customer issue, I tend to communicate. You don’t need to over-communicate, but it’s always good to keep people in the loop. Offer a solution as part of your communication; don’t go into the conversation only with the problem. If you give your audience something to work with, then it’s much easier to work towards a solution.
Lastly, leave your ego aside. Ask for help and reciprocate when others ask help from you.

What is your superpower?
Authenticity.

What is your definition of success?
It’s not a traditional view of success. To me success is being able to contribute to something and feel good about it in the end – build something, get features working and seeing your work deployed, adopted and used by customers. To me, success is about working on something you think is significant and eventually sees the light of day.

What are you passionate about?
At work, distributed systems and all the nuts and bolts that go with it. I love automation, observability and debugging challenging problems – I get a kick out of that.
At home, my family. Spending time with both of my girls.
Icebreaker Round
When we interviewed Anusha, we also did a quick icebreaker round. Her answers were great so we’ve included them here!

Icons and graphics sourced from Lineal, Darius Dan and Smashicon on Flaticon.

We’ll feature profiles of some more of the amazing women who work at Docker throughout the week!

We’re celebrating Women In Tech Week! Discover @AnushaRagunatha’s story of being an #Engineer at Docker.Click To Tweet

The post Women in Tech Week Profile: Anusha Ragunathan appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

Top Questions Answered: Docker and Kubernetes? I Thought You Were Competitors!

Last week, we covered some of the questions about container infrastructure from our recent webinar “Demystifying VMs, Containers, and Kubernetes in the Hybrid Cloud Era.” This week, we’ll tackle the questions about Kubernetes, Docker and the software supply chain. One common misperception that we heard in the webinar — that Docker and Kubernetes are competitors. In fact, Kubernetes is better with Docker. And Docker is better with Kubernetes.
Docker And Kubernetes? I thought you were competitors?
We hear questions along this line all the time. Here are some quick answers:
Can I use Kubernetes with Docker?

Yes, they go together. You need a container runtime like Docker Engine (based on open source containerd) to start and stop containers on a host.
When you have a bunch of containers running across a bunch of hosts, you need an orchestrator to manage things like: Where will the next container start? How do you make a container highly available? How do you control which containers can communicate with other containers? That’s where an orchestrator such as Kubernetes comes in.

Comparing traditional, virtualized, containerized and Kubernetes deployment architectures.

The container runtime and the orchestrator are the two core atomic units that go together. You could just install Kubernetes and Docker Engines and have something that works, but enterprise organizations need security, monitoring and logging, enterprise storage and networking, and much more. 
This is where a container platform like Docker Enterprise comes in: Docker Enterprise is the easiest and fastest way to use containers and Kubernetes at scale and delivers the fastest time to production for modern applications, securely running them from hybrid cloud to the edge. It also ships with a CNCF-conformant version Kubernetes!

Docker Enterprise adds important capabilities to Kubernetes and makes it easier to use.
Does Kubernetes replace Docker Swarm?

No, they can be used together. Kubernetes and Docker Swarm are both orchestrators, so they have the same end goals. New users find it much easier to understand Docker Swarm. However, Kubernetes has evolved to add a lot of functionality.
The good news: you can use both side-by-side in Docker Enterprise. Enable your developers and operators to decide which route they want to go: you don’t have to tie yourself to one decision or the other.

You can learn more about this choice from the on-demand webinar, Swarm vs. Kubernetes, Presented by BoxBoat.
Container images, security, and CI/CD
 A Secure Software Supply Chain is another big part of what makes up a container platform. After all, Docker Engine and Kubernetes wouldn’t have anything to do without container images! This was clearly another area with lots of interest.
We demonstrated vulnerability scanning and some questions came up about where scanning fits in the development lifecycle.
Do you scan containers in development? Test? QA? Production?
Vulnerability scanning is a feature of Docker Trusted Registry (DTR), which is part of Docker Enterprise. Scanning can happen any time a new image is pushed to the registry, when the vulnerability database is updated, or on demand. 

The answer is “Always be scanning.” Scanning can occur in both development and production. You want to scan the images when they are pushed to the registry and then continue to check them against the latest vulnerability discoveries. Vulnerabilities have a way of getting discovered months or even years after libraries are released. If you only scan the container when it’s originally created, you risk missing these new vulnerabilities in your existing applications.
The Application Designer in Docker Desktop Enterprise (our locally installed tool for developers) has pre-configured Templates. In reality, those Templates are container images that “live” in DTR. With Desktop Enterprise, developers automatically pull scanned images to their machines. In addition, the templates can be customized to your organization’s particular standards and approved frameworks. You can build-in your coding standards, plug-ins or other artifacts directly into the templates as well.
We automatically check existing images against the vulnerability database whenever it is updated. On the production side, you might have long-running containers in your environment. Those get scanned and we surface the results in the Universal Control Plane. From there, you can easily tell which of your running applications are affected and choose how to address the issues.

Getting Started
A lot of people had questions about how to get started with Kubernetes. Fortunately, they’re much easier questions to answer and many of the resources are free!

If you want to get started with Docker and Kubernetes on your own and you have a Windows 10 (with Hyper-V features) or macOS machine, go get Docker Desktop. It’s free, incredibly easy to set up, and you’ll have both Docker and Kubernetes ready to go.
If you have a Linux workstation you can get Docker Engine for free. Make sure you’re getting the actual Docker Engine and not a forked version by following the instructions here.
If you can’t install software on your machine or you don’t have an OS that meets the requirements, you can use Play with Docker and Play with Kubernetes for free. . Both provide access to nodes directly from your browser. They also have lab content to guide you through introductory exercises.
Read the excellent blog series from Bill Mills on our training team about designing your first application in Kubernetes.

Are #Docker and #Kubernetes competitors? @jdarmstro answers your questions on the blog.Click To Tweet

The post Top Questions Answered: Docker and Kubernetes? I Thought You Were Competitors! appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

Don’t Miss Docker’s Hands-on Workshop at Arm TechCon 2019

Photo by Zan Ilic on Unsplash
Momentum is building for edge computing
With the rise of the Internet of Things (IoT) combined with global rollout of 5G (Fifth-generation wireless network technology), a perfect storm is brewing that will see higher speeds, extreme lower latency, and greater network capacity that will deliver on the hype of IoT connectivity.
And industry experts are bullish on the future. For example, Arpit Joshipura, The Linux Foundation’s general manager of networking, predicts edge computing will overtake cloud computing by 2025. According to Santhosh Rao, senior research director at Gartner, around 10% of enterprise-generated data is created and processed outside a traditional centralized data center or cloud today. He predicts this will reach 75% by 2025.
Back in April 2019, Docker and Arm announced a strategic partnership enabling cloud developers to build applications for cloud, edge, and IoT environments seamlessly on the Arm® architecture. We carried the momentum with Arm from that announcement into DockerCon 2019 in our joint Techtalk, where we showcased cloud native development on Arm and how multi-architecture containers with Docker can be used to accelerate Arm development.  
A hands-on workshop for ARM developers
As part of our strategic partnership, Docker will be participating at ARM TechCon scheduled this October 8-10, 2019 at the San Jose Convention Center. Docker is excited to announce that we will be delivering a hands-on workshop exclusive to All-Access Pass holders in attendance:
Software Development for the Arm Architecture with DockerOctober 8, 2019: 3:30 PM to 5:30 PM 
This workshop builds on previously announced multi-architecture builds to introduce new tools and concepts to accelerate development and streamline deployments of Artificial Intelligence (AI) and Machine Learning (ML) workloads on Arm edge and IoT devices.
The workshop will provide a hands-on session with Docker Desktop on Windows or Mac, Amazon Web Services (AWS) A1 instances, and embedded Linux. The session will cover the latest Docker features to build, share, and run multi-architecture images with transparent support for Arm. Attendees will be provided with a 60-day trial license of Docker Desktop Enterprise including multiple examples and demos as well as the latest Raspberry Pi 4 development board to keep.
Our strategic partnership benefits both Arm developers and the Docker community by bringing together a common development platform where users can access Arm technology in the cloud, on the desktop, and with embedded and IoT devices. Arm and Docker are educating software developers on the benefits and simplicity Docker brings to the development process. We hope to see you at TechCon and your participation at the hands-on workshop.
Read Our Guide to Arm TechCon
To learn more about how Docker can help bring life to your edge and IoT ideas:

Come see us at the Docker booth in the Infrastructure Zone, at ArmTechCon 2019
Read about Building Multi-Arch Images for Arm and x86 with Docker Desktop
Watch the DockerCon session on Developing Containers for Arm

Learn how to bring #IoT and edge computing to life with Docker and @arm at #ArmTechCon Click To Tweet

The post Don’t Miss Docker’s Hands-on Workshop at Arm TechCon 2019 appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/