Docker Services Descriptions

Table of Contents

Docker Professional Services

Scoped Services

Docker Build Service

Docker MTA Accelerator Service

Docker MTA Accelerator Add-On

Docker Technical Account Management Services

Docker Technical Account Management Services

Docker Enterprise Technical Account Management Services

Docker Training Services

General Terms

Docker Fundamentals

Docker for Enterprise Operations

Docker for Enterprise Developers

Docker Fundamentals + Docker for Enterprise Operations Bundle

Docker Fundamentals + Docker for Enterprise Developers Bundle

Docker Security

Docker Production Support

Docker Custom On-Site Training

Docker Learning Credits

Services Agreement

Please Note: The following terms only apply if the applicable service is specifically listed in an Order Form to which these terms are incorporated. For the avoidance of doubt, terms for services which are not identified in an Order Form do not apply.

Docker Professional Services

SCOPED SERVICES

THE FOLLOWING TERMS APPLY TO SCOPED SERVICES DESCRIBED IN A STATEMENT OF WORK (“SOW”)[see comment below].

CONTRACT STRUCTURE: All scoped services (“Scoped Services”) are delivered on a time and materials basis unless explicitly stated in a SOW. Each hour worked in support of a SOW will be invoiced as per the customer’s contractual arrangement with Docker (the “Agreement”) and, if applicable, the Payment Terms below.

CONTRACT STRUCTURE: All scoped services (“Scoped Services”) are delivered on a time and materials basis unless explicitly stated in a SOW. Each hour worked in support of a SOW will be invoiced as per the customer’s contractual arrangement with Docker (the “Agreement”) and, if applicable, the Payment Terms below.

LEVEL OF EFFORT, FEES: The level of effort for the Scoped Services described in the SOW is estimated based on the following:

  • Extent of the work defined in the SOW
  • Project Prerequisites defined below, as well as any additional or superseding Project Prerequisites in the SOW
  • Assumptions defined below, as well as any additional or superseding Assumptions in the SOW
  • Customer Responsibilities defined below, as well as any additional or superseding Customer Responsibilities in the SOW
  • Exclusions defined below, as well as any additional or superseding Exclusions in the SOW

Any variance in the specific efforts outlined above may affect the estimated level of effort and the associated fees. Any change in level of effort, fees or other costs shall be effective only upon a signed written agreement between the parties as outlined in the Change Management process defined below.

Any customer purchase order for the Scoped Services must include adequate funding for all fees defined on the Order Form and align with the level of effort and fees for the applicable project.

TRAVEL: The Docker Professional Services team will deliver Scoped Services subject to any reasonable travel and expense policy provided by Customer prior to the applicable project’s kickoff. If the travel and expense policy is not provided in a timely manner, or the Customer does not have a travel policy for contractors, then the Docker Professional Services team will deliver Scoped Services subject to Docker’s own internal travel and expense policies.

Customer should budget for fees associated with travel and expenses at an estimated twenty percent (20%) of the total fees as described in the Order Form. Actual travel expenses will depend on a number of factors including the applicable travel policy, amount of time spent at a customer site and other variables. Actual expenses will be invoiced in accordance with the Agreement or as otherwise agreed.

The execution of the SOW incorporating the terms and conditions contained herein shall be deemed pre-approval for the travel and related expenses incurred by Docker on the applicable project.

No cap on travel expenses will be applicable unless it has been specifically stipulated and agreed to as a term in the SOW.

Any Customer Purchase Order must include adequate funding for all travel expenses and other associated costs.

PROJECT PREREQUISITES: The prerequisites below are essential to the success of the applicable project.

Collaboration. The primary prerequisite for success is extensive collaboration between the Customer infrastructure team(s), the Customer applications team(s) and the Docker project team. Lack of full participation from any of the teams will affect the schedule, cost and success of the applicable project.

Applications

  • Access to source code for all applications targeted for inclusion in the applicable project.
  • Access to application-specific subject matter experts for all applications targeted for inclusion in the applicable project as per the project plan defined during the project initiation process.

Infrastructure

  • Available infrastructure on one of: VMWare, baremetal, AWS, Azure
  • VMs with system requirements and access to appropriate package repository
  • Machine image(s) of supported OS
  • Shared storage (NFS and S3)
  • External load balancer
  • Existing subscriptions for the applicable Docker products

Customer Team

  • A business sponsor to own the business case and governance and to provide overall leadership
  • A project manager or scrum master to drive the applicable project
  • Application teams with:
    • Specified minimum workstation requirements and capability to install Docker Desktop Enterprise on their workstations
    • Knowledge of Continuous Integration/Continuous Delivery (“CI/CD”) concepts and processes
  • A platform team with access and the capability to design, deploy and maintain the required infrastructure

Project

  • Sponsor, Application and Operational team ownership in driving change
  • Willingness to adopt new tooling and processes

ASSUMPTIONS:

  • Delivery of Scoped Services will be scheduled by mutual agreement of the parties after execution of this SOW.
  • This SOW for Scoped Services is not a part of maintenance and technical support services provided through any software services agreement between Company and Docker.
  • Only server-side applications (e.g. web apps, service apps, API backends, etc.) will be considered as candidates for the applicable project.

TIME CONSTRAINTS:

  • All SOWs have a duration of twelve (12) months and will expire at the end of such period.
  • Any extension of the period requires a written agreement between all parties using the Change Management process described below.
  • Project work must be scheduled in advance as part of project planning and is subject to resource availability.

CUSTOMER RESPONSIBILITIES:

  • Customer is responsible to secure all appropriate and necessary Docker commercial product subscriptions.
  • Customer will ensure that the subject matter experts are available for the applicable project in a timely manner and as per the project plan defined during the project initiation process.
  • Customer is responsible to provide, configure and maintain all hardware and software required for the applicable project; said hardware and software will be available on a timely basis for use by Docker throughout the applicable project.
  • Customer is responsible for its data, including selection and implementation of controls on its access and use, and security for its data.
  • Customer is responsible for ensuring it maintains appropriate backup, security and virus-checking procedures in place for any facilities Customer provides or which may be affected by Scoped Services and that any such data remains retrievable speedily and economically.
  • Customer is responsible for ensuring its specifications comply with applicable law.
  • Customer is responsible for obtaining any third party consents and cooperation necessary for the performance of Scoped Services.

PAYMENT TERMS:

  • Docker shall invoice Customer monthly for Scoped Services delivered under the SOW. Customer shall pay invoices from Docker in accordance with the payment terms in the Agreement.
  • Customer agrees to reimburse for travel and related expenses subject to the SOW, the terms herein, and the Agreement.

CHANGE MANAGEMENT: Initial estimates of the level of effort, fees and expenses associated with the SOW are provided in the SOW or described in the terms described above. These estimates may be refined upon further scoping and planning after work has begun.

Any variance from the terms and conditions defined herein, or from the scope of work as defined in the SOW, may affect the level of effort, scope definition, schedule and fees and associated costs.

Should a variance cause a change in level of effort, scope definition, schedule or fees and costs, such change must be made in a written Change Order signed by the parties prior to the acceptance or adherence of the cause of the variance.

DOCKER BUILD SERVICE

THE SERVICE:  The Docker Enterprise Build Service (“Service” or “DBS”) is a fixed-scope, fixed-price service that includes design assistance and installation of a single, highly-available, Docker Enterprise Edition (“DEE”) cluster . The Service is comprised of one phase, delivered 100% remotely through web and video conference.

The Docker Build Services provides the design and full installation of the Docker Enterprise Edition (“DEE”) platform including the Docker Engine, UCP (“Universal Control Plane”), and DTR (“Docker Trusted Registry”) in a Customer’s compute environment. The Service does not include support for any unit of software (such as engines, registries, etc.) for which Customer does not have an active paid subscription and can only be combined with Business Day and Business Critical subscriptions. It also does not include application containerization and migration.  This phase includes the following:

  1. Education.  Docker will provide up to three hours of DEE architecture best practices and discussion of build requirements which includes gaining a fundamental understanding of Docker Engine, Universal Control Plane, and Docker Trusted Registry.

  2. Docker Engine Installation.  Docker will install and configure the Docker engine in the target host environment which includes configuration of Engine Graph Storage Driver and other Docker Engine settings.

  3. UCP Installation.  Docker will provide design assistance for a UCP cluster that includes UCP Controller Nodes and UCP Worker Nodes for application deployment. Docker will provide live installation and configuration assistance for the UCP cluster. UCP configuration includes:  1) LDAP/AD Configuration, 2) Cluster Certificates, 3) UCP Infrastructure Logging, 4) UCP Content Trust, and 5) UCP Routing Mesh.

  4. DTR Installation.  Docker will provide design assistance for a DTR application.  Docker will provide live installation and configuration assistance for DTR. DTR configuration includes:  1) DTR Storage Configuration, 2) DTR Certificates, 3) Garbage Collection Configuration, 4) Image Scanning Configuration, 5) DTR Content Cache Configuration.

E.     Supported Environments. Only the following environments and compatible systems are supported for DBS service: 1) Commercially Supported Host Operating Systems (https://success.docker.com/Policies/Compatibility_Matrix), 2) Commercially Supported Docker Software Versions (https://success.docker.com/Policies/Compatibility_Matrix), and 3) Limited to one computing environment per engagement.  A compute environment includes on-premise data center, Amazon Web Services, Microsoft Azure, or other similar environments.

PAYMENT:  In consideration for the Service, Customer will pay Docker the fees set forth in the applicable Order Form. Docker will invoice Customer up front for the Service. Customer will pay all invoices issued by Docker in full within thirty (30) days of the date of each invoice, without setoff, counterclaim, or deduction of any kind.

EXPENSES: The DBS is designed as a remotely service, however if an onsite build is requested, Docker will invoice separately for travel and other related expenses incurred while delivering the DBS.

SKU: CONS-DBS-000001

DOCKER MTA ACCELERATOR SERVICE

THE SERVICE: The Modernizing Traditional Application (“MTA”) Accelerator Service ("Service") is a professional service package comprised of:  1) the guided setup of a single functional Docker Enterprise Edition ("DEE") Environment, 2) assistance with containerizing a traditional Windows or Linux Application of Customer and deploying it to the DEE Environment, and 3) follow up weekly check-in calls.

The Service is delivered both remotely through web and video conference and onsite as set forth below:

 

Phase

Duration

Location

1. Workshop Phase

5 hours

Remote

2. Infrastructure Preparation Phase

16 hours

Remote

3. Application Modernization Phase

32 hours

Onsite

4. Support Phase

3 hours

Remote

For the avoidance of doubt, the Service excludes: 1) Integration with continuous integration or build environments, 2) disaster recovery configuration, and 3) performance and load testing.

ADDITIONAL SERVICES/HOURS: In the event Customer selects an application that requires more than 32 hours of effort during the Application Modernization Phase, then Customer may purchase one or more Docker MTA Services Add-On(s), each of which is an additional 4-hour block of service.

Definitions:

A. Application” means a container-compatible, custom server-side application based on Java or .NET frameworks

B. Application Component” means an application tier or part of application with an independent runtime requiring an independent container

C. Application Stack” means a composition of containerized Application Components to make up a complete Application, not including databases.

D. Docker Universal Control Plane” or “UCP” means Docker’s enterprise-grade cluster management solution

E. Docker Trusted Registry” or “DTR” means Docker’s enterprise-grade container registry which includes image signing and scanning

F. Environment” means the deployment destination through each step of the Application lifecycle (e.g. development, testing, staging, production).

 

1. Workshop Phase:

During the Workshop Phase, Docker will review Applications with Customer and will provide Customer with basic product knowledge on DEE.

A.     Applications. Docker will work with Customer to review Applications as candidates for migration. Customer shall select three Applications, ranked by preference. Docker will assist Customer in the migration of a single Application during the Application Modernization Phase, however the remaining Applications shall serve as ‘fallbacks’ should Docker and Customer run into unforeseen difficulties in the migration. An Application may contain no more than five (5) Application Components.

B.     Product Knowledge Transfer.  Prior to installation and configuration, a Docker solution architect will discuss DEE fundamentals with Customer. The topics will include the Docker EE Container Engine, Universal Control Plane, and Docker Trusted Registry.

 

2. Infrastructure Preparation Phase:

The Infrastructure Preparation Phase provides the design and full installation of DEE including the Docker EE Container Engine, UCP and DTR in Customer’s Environment. The services associated with this phase (a) does not include support for any unit of software (such as engines, registries, etc.) that is not a Docker Product (b) requires at least ten (10) nodes of Docker EE Standard or Advanced, to which Customer must subscribe separate from this Agreement. This phase includes the following:

A.     Docker EE Container Engine Installation.  Docker will guide Customer’s installation and configuration of the Docker engine in the target Environment which includes configuration of Engine Graph Storage Driver and other Docker Engine settings.

B.     UCP Installation.  Docker will provide design assistance for a UCP cluster that includes UCP Controller Nodes and UCP Worker Nodes for application deployment. Docker will provide live installation and configuration assistance for the UCP cluster. UCP configuration includes:  1) LDAP/AD Configuration, 2) Cluster Certificates, 3) UCP Infrastructure Logging, 4) UCP Content Trust, and 5) UCP Routing Mesh.

C.     DTR Installation.  Docker will provide design assistance for a DTR application.  Docker will provide live installation and configuration assistance for DTR. DTR configuration includes:  1) DTR Storage Configuration, 2) DTR Certificates, 3) Garbage Collection Configuration, 4) Image Scanning Configuration, 5) DTR Content Cache Configuration.

D.     MTA Build Supported Environments.  This phase is only supported for the following environments and compatible systems: 1) Commercially Supported Host Operating Systems (https://success.docker.com/Policies/Compatibility_Matrix), 2) Commercially Supported Docker Software Versions (https://success.docker.com/Policies/Compatibility_Matrix), and 3) Limited to one computing environment per engagement.

 

3. Application Modernization Phase:

The Application Modernization Phase provides the identification and migration of a traditional Windows or Linux application to the Environment established during the Infrastructure Preparation Phase. Docker will work with Customer to identify a suitable Application for containerization, then guide Customer through the migration. Up to three (3) Applications will be identified as appropriate for the Application Migration Phase. One of the Applications will be containerized and migrated with the remaining two to be used if, upon further investigation, the selected application is not appropriate. The services associated with this phase (a) does not include support for any unit of software (such as engines, registries, etc.) that is not a Docker Product, and (b) requires at least ten (10) nodes of Docker EE Standard or Advanced.

A.     Containerize Applications Components.  Docker will assist Customer to 1) create a Docker image for each Application Component, 2) validate that the Application Component runs on a single node, then externalize Environment-specific configurations as runtime environment variables and secrets (e.g. connection strings, API keys, etc.)

B.     Compose Application Components.  Docker will help Customer 1) assemble Application Components into a full Application Stack, 2) centralize logging, 3) create Docker Compose file for the Environment (e.g. development/UAT environments may include database tier, while staging/production environments may not), and 4) validate that the Application Stack runs on a single node.

C.     Deploy Application Components.  Docker will guide Customer through 1) pushing the Application Component images to DTR, and 2) deploying composed Application to UCP.

D.     Application Validation and Testing.  Docker will assist Customer to 1) run a functional test plan, and 2) validate end-to-end deployment process.

E.     Knowledge Transfer. Prior to completion of this phase, Docker will review configurations, assets (e.g., Dockerfile, docker-compose, yml, bootstrap scripts), commands, and general information on how to deploy the application onto DEE.

 

4. Support Phase

The Support Phase provides Customer a number of check points after the Application Modernization Phase.

Weekly Checkpoints.  Docker will host a 1-hour conference call each week for the first 3 weeks after the Application Modernization Phase to discuss Customer’s status, and provide any additional guidance. Any support outside of the conference calls is based on the underlying Docker subscription services.

PAYMENT:  In consideration for the Service, Customer will pay Docker the fees set forth in the applicable Order Form. Docker will invoice Customer up front for the Service. Customer will pay all invoices issued by Docker in full within thirty (30) days of the date of each invoice, without setoff, counterclaim, or deduction of any kind.

EXPENSES: The Application Modernization Phase is designed for delivery at a customer location. Docker will invoice separately for travel and other related expenses incurred while delivering the Service.

SKU: CONS-MTA-000001

DOCKER MTA ACCELERATOR SERVICES ADD-ON

The Docker MTA Accelerator Service Add-On is a 4-hour add-on to the Application Modernization Phase of the Docker MTA Accelerator Service.

See:  APPLICATION MODERNIZATION PHASE:

The Application Modernization Phase provide the identification and migration of a traditional Windows or Linux application to the Environment established during the Build Phase. Docker will work with Customer to identify a suitable application for containerization, then guide Customer through the migration. Up to three (3) Applications will be identified as appropriate for the Application Migration Phase. One of the applications will be containerized and migrated with the remaining two to be used if upon further investigation the selected application is not appropriate. This phase does not include support for any unit of software (such as engines, registries, etc.) that is not a Docker Product.

A.     Containerize Applications Components.  Docker will assist Customer 1) create a Docker image for each Application Component, 2) validate the Application Component runs on a single node, then externalize Environment-specific configurations as runtime environment variables and secrets (e.g. connection strings, API keys, etc.)

B.     Compose Application Components.  Docker will help Customer 1) assemble Application Components into a full Application Stack, 2) centralize logging, 3) create Docker Compose file for the Environment (e.g. development/UAT environments may include database tier, while staging/production environments may not), 4) validate Application Stack runs on a single node

C.     Deploy Application Components.  Docker will guide Customer through 1) pushing the Application Component images to DTR, 2) deploying composed Application to UCP.

D.     Application Validation and Testing.  Docker will assist Customer 1) run functional test plan, 2) validate end-to-end deployment process

E.     Knowledge Transfer. Prior to completion of the Phase, Docker will review configurations, assets (e.g., Dockerfile, docker-compose.yml, bootstrap scripts), commands, and general information on how to deploy the application on the DEE platform.

PAYMENT:  In consideration for the Service, Customer will pay Docker the fees set forth in the applicable Order Form. Docker will invoice Customer up front for the Service. Customer will pay all invoices issued by Docker in full within thirty (30) days of the date of each invoice, without setoff, counterclaim, or deduction of any kind.

EXPENSES: The Application Modernization Phase is designed for delivery at a customer location. Docker will invoice separately for travel and other related expenses incurred while delivering the Service.

SKU: CONS-MTA-000002

 

Docker Technical Account Management Services

DOCKER TECHNICAL ACCOUNT MANAGEMENT SERVICES

Technical Account Management services last for the term identified in the Order Form and provides Customer for enhanced ongoing support in addition to the standard Docker Commercial Support Subscription.

The Docker Technical Account Managed Services is a remote service with a resource allocated at 20% of full time allocation. The TAM Service does not include support for any unit of software (such as engines, registries, etc.) for which Customer does not have an active paid product subscription and can only be combined with Business Day and Business Critical subscriptions. Customer receives access to a designated Docker Technical Account Manager to provide Customer with:

§  Architectural Guidance:  1) Solution Reviews, 2) Implementation guidance, 3) Lifecycle Planning.

§  Access and Advocacy:  1) Arrangement of Specialist Engagements, 2) Advocacy for product enhancements, and 3) Access to advanced betas and other special programs.

§  Strategic Support:  1) Oversight of support cases including quarterly service performance metrics, 2) Preventative notifications, and 3) Ongoing engagement via at least monthly conference calls.

A. TAM Regional Coverage. The TAM Service is limited to the following regions:   AMER (North and South America), EMEA (Europe, Middle East, Africa).  The specific supported region shall be mutually agreed upon by Docker and Customer upon initiation of the TAM Service. Each TAM is limited to covering a single region.

B. TAM Customer Team Coverage. The TAM Service is limited to a specific division, group, line of business or team within a Customer (e.g., research and development, support, system administration, etc.). The specific division, group, line of business or team will be identified and agreed to by Docker and Customer upon initiation of the TAM service.

C. TAM Service Hours.  The TAM Service is available during local business hours based on the physical location of the Docker TAM. For purposes of clarity, the Service (including the TAM Service) is separate and apart from Docker's Business Day or Business Critical support services which are sold separately and provided in accordance with the terms of a separate subscription agreement.

PAYMENT:  In consideration for the Technical Account Management service, Customer will pay Docker the fees set forth in the applicable Order Form. Docker will invoice Customer up front for the Service. Customer will pay all invoices issued by Docker in full within thirty (30) days of the date of each invoice, without setoff, counterclaim, or deduction of any kind.

SKU: CONS-DTAM-000001

 

DOCKER ENTERPRISE TECHNICAL ACCOUNT MANAGEMENT SERVICES

Technical Account Management services last for the term identified in the Order Form and provides Customer for enhanced ongoing support in addition to the standard Docker Commercial Support Subscription.

The Docker Enterprise Technical Account Managed Services is a remote service with a resource allocated at 50% of full time allocation. The TAM Service does not include support for any unit of software (such as engines, registries, etc.) for which Customer does not have an active paid product subscription and can only be combined with Business Day and Business Critical subscriptions. Customer receives access to a designated Docker Technical Account Manager to provide Customer with:

§  Architectural Guidance:  1) Solution Reviews, 2) Implementation guidance, 3) Lifecycle Planning.

§  Access and Advocacy:  1) Arrangement of Specialist Engagements, 2) Advocacy for product enhancements, and 3) Access to advanced betas and other special programs.

§  Strategic Support:  1) Oversight of support cases including quarterly service performance metrics, 2) Preventative notifications, and 3) Ongoing engagement via at least monthly conference calls.

A. TAM Regional Coverage. The TAM Service is limited to the following regions:   AMER (North and South America), EMEA (Europe, Middle East, Africa).  The specific supported region shall be mutually agreed upon by Docker and Customer upon initiation of the TAM Service. Each TAM is limited to covering a single region.

B. TAM Customer Team Coverage. The TAM Service is limited to a specific division, group, line of business or team within a Customer (e.g., research and development, support, system administration, etc.). The specific division, group, line of business or team will be identified and agreed to by Docker and Customer upon initiation of the TAM service.

C. TAM Service Hours.  The TAM Service is available during local business hours based on the physical location of the Docker TAM. For purposes of clarity, the Service (including the TAM Service) is separate and apart from Docker's Business Day or Business Critical support services which are sold separately and provided in accordance with the terms of a separate subscription agreement.

PAYMENT:  In consideration for the Technical Account Management service, Customer will pay Docker the fees set forth in the applicable Order Form. Docker will invoice Customer up front for the Service. Customer will pay all invoices issued by Docker in full within thirty (30) days of the date of each invoice, without setoff, counterclaim, or deduction of any kind.

SKU: CONS-ETAM-000001

Docker Training Services

THE FOLLOWING TERMS APPLY TO EVERY TRAINING COURSE DELIVERED BY DOCKER.

GENERAL TERMS

Overview and Duration.

Docker will provide Docker Training to Customer for the number of days identified per course in the course descriptions below. Training sessions will take place from 9:00 am to 5:00 pm local time every day with a lunch break.

Limitations:

To keep the quality of instruction high, Docker limits the maximum number of students to twenty (20).  If Customer requires more than 20 students in a training session, additional sessions or headcount should be purchased.

Assumptions

  • Delivery dates for the training session(s) and the location for the services will be determined by mutual agreement of the parties.

  • Docker is not responsible for provision of lunch for the students.

  • Customer is responsible to secure all Docker commercial product license subscriptions (not included in SOW).

  • The execution of this SOW shall be deemed pre-approval for the travel expenses incurred by Docker on this specific project.

  • This SOW for training services is not a part of maintenance and technical support services provided through any software license agreement between Customer and Docker.  

  • Any provided travel policies, working times, dress codes, and all other subsequent policies provided by Customer to Docker will be adhered to by the Docker employees delivering this service and only may be revised with the approval of Customer and Docker.

Location

Docker shall perform the training session on-site at the Customer’s location that meets the above agreed to criteria between the Customer and the Docker trainer.

Customer Responsibilities

All private on-site courses must be scheduled and confirmed a minimum of two weeks prior to delivery or as agreed by Docker.

Customer will meet with Docker prior to the training sessions to plan and prepare for delivery including:

  • Test of labs and classroom facilities

  • Test of internet policies and restrictions that may inhibit a successful class delivery

  • Provisions of names and emails of students to Docker for class preparation and records

  • Provide assurance of appropriate level of expertise on all non-Docker-supplied tools

Prerequisites

  • Customer will provide a training room to accommodate the students, with audio-visual capabilities and a white board.
  • Customer is responsible to provide and configure all systems required for the training services.
  • Each participant must complete the following prior to the training;
  • Docker ID account (https://cloud.docker.com/)

Course Updates

There are some cases where the course is improved and revised between the time when training is scheduled and when training is delivered.  This may result in some changes to topics. Docker will deliver the latest version of the course available at the time of delivery.

Payment

In consideration for the Docker Training, Customer will pay Docker the fees set forth in the applicable Order Form. Docker will invoice Customer up front for the Docker Training. Customer will pay all invoices issued by Docker in full within thirty (30) days of the date of each invoice, without setoff, counterclaim, or deduction of any kind.

Expenses

Docker will invoice separately for travel and other related expenses incurred while delivering Docker Training.

Internal Use

The training course and any materials are for internal use by Customer only. No portion of the training or materials may be recorded or distributed.

THIS MARKS THE END OF THE TERMS THAT APPLY TO EACH TRAINING COURSE. THE TERMS BELOW ONLY APPLY TO THE APPLICABLE COURSE AS IDENTIFIED IN THE APPLICABLE ORDERING DOCUMENT.  

DOCKER FUNDAMENTALS

Course Description

In the Docker Fundamentals training course students will learn the foundational concepts and practices of containerization on a single Docker node. They will also gain an understanding of basic container orchestration and how to scale Docker across multiple nodes in a simple swarm cluster. This course provides essential foundational knowledge for all other official Docker courses.

Course Outline

Day 1

  • The Docker Story
  • Introduction to Images
  • Creating Images
  • System Commands
  • Volumes
  • Plugins

Day 2

  • Docker Networking Basics
  • Docker Compose
  • Scaling out with Swarm Mode
  • Managing Secrets

SKU: TRNG-ONS-DFUN-00001

 

DOCKER FOR ENTERPRISE OPERATIONS

Course Description

Docker for Enterprise Operations is a role-based course designed for Docker Operations teams to accelerate their Docker journey in the enterprise. Students will learn the many advanced features of Docker EE and how to apply them at scale with enterprise workloads.

Course Outline


Day 1

  • Introduction to Docker Enterprise Edition
  • UCP Architecture
  • UCP Networking
  • UCP Role-based Access Control
  • Secrets Management
  • Logging
  • Monitoring and Recovery
  • UCP Health Check

Day 2

  • DTR Overview
  • DTR Organizations and Teams
  • Content Trust
  • Image Scanning
  • Repository Automation
  • Image Caching
  • DTR Troubleshooting
  • Designing a Docker Enterprise Edition Deployment

SKU: TRNG-ONS-DOPS-00001

 

DOCKER FOR ENTERPRISE DEVELOPERS

Course Description

Docker for Enterprise Developers is a role-based course designed for an organization’s Development and DevOps teams to accelerate their Docker journey in the enterprise. This course is meant for developers and DevOps teams that want to learn how to containerize and modernize legacy applications or build containerized applications from scratch that are secure, robust, highly available, resilient and self-healing. This course teaches all the necessary foundations to achieve this goal.

Course Outline

Day 1

  • Architecture of a Highly Distributed Application
  • Development Pipeline Overview
  • Developing Applications using Docker
  • Edit and Continue
  • Debugging
  • Docker Compose
  • Testing
  • Health Check
  • Defensive Programming
  • Logging and Error Handling
  • Docker Builder
  • Docker Secrets
  • Routing Mesh
  • HTTP Routing Mesh

Day 2

  • Continuous Integration and Delivery
  • UCP and DTR
  • Configuration Management
  • Tagging and Versioning
  • Content Trust
  • Image Scanning
  • Webhooks
  • Image Promotion

SKU: TRNG-ONS-DEVS-00001

 

DOCKER FUNDAMENTALS + ENTERPRISE OPERATIONS BUNDLE

Course Description

In the Docker Fundamentals training course students will learn the foundational concepts and practices of containerization on a single Docker node. They will also gain an understanding of basic container orchestration and how to scale Docker across multiple nodes in a simple swarm cluster. This course provides essential foundational knowledge for all other official Docker courses.

Docker for Enterprise Operations is a role-based course designed for Docker Operations teams to accelerate their Docker journey in the enterprise. Students will learn the many advanced features of Docker EE and how to apply them at scale with enterprise workloads.

Course Outline

Day 1

  • The Docker Story
  • Introduction to Images
  • Creating Images
  • System Commands
  • Volumes
  • Plugins

Day 2

  • Docker Networking Basics
  • Docker Compose
  • Scaling out with Swarm Mode
  • Managing Secrets

Day 3

  • Introduction to Docker Enterprise Edition
  • UCP Architecture
  • UCP Networking
  • UCP Role-based Access Control
  • Secrets Management
  • Logging
  • Monitoring and Recovery
  • UCP Health Check

Day 4

  • DTR Overview
  • DTR Organizations and Teams
  • Content Trust
  • Image Scanning
  • Repository Automation
  • Image Caching
  • DTR Troubleshooting
  • Designing a Docker Enterprise Edition Deployment

SKU: TRNG-ONS-FNDP-00001    

 

DOCKER FUNDAMENTALS + ENTERPRISE DEVELOPERS BUNDLE

Course Description

In the Docker Fundamentals training course students will learn the foundational concepts and practices of containerization on a single Docker node. They will also gain an understanding of basic container orchestration and how to scale Docker across multiple nodes in a simple swarm cluster. This course provides essential foundational knowledge for all other official Docker courses.

Docker for Enterprise Developers is a role-based course designed for an organization’s Development and DevOps teams to accelerate their Docker journey in the enterprise. This course is intended for developers and DevOps teams that want to learn how to containerize and modernize legacy applications or build containerized applications from scratch that are secure, robust, highly available, resilient, and self-healing. This course teaches all the necessary foundations to achieve this goal.

Course Outline

Day 1

  • The Docker Story
  • Introduction to Images
  • Creating Images
  • System Commands
  • Volumes
  • Plugins

Day 2

  • Docker Networking Basics
  • Docker Compose
  • Scaling out with Swarm Mode
  • Managing Secrets

Day 3

  • Architecture of a Highly Distributed Application
  • Development Pipeline Overview
  • Developing Applications using Docker
  • Edit and Continue
  • Debugging
  • Docker Compose
  • Testing
  • Health Check
  • Defensive Programming
  • Logging and Error Handling
  • Docker Builder
  • Docker Secrets
  • Routing Mesh
  • HTTP Routing Mesh

Day 4

  • Continuous Integration and Delivery
  • UCP and DTR
  • Configuration Management
  • Tagging and Versioning
  • Content Trust
  • Image Scanning
  • Webhooks
  • Image Promotion

SKU: TRNG-ONS-FNDV-00001

 

DOCKER SECURITY

Course Description

This advanced workshop style course will give your team a hands-on overview of important security features and best practices to protect your containerized services. Designed to be inclusive of multiple roles, this course is appropriate for all teams who are hands-on with Docker whether Developer, Operations, DevOps, or Architect. Completion of the Docker for Enterprise Operations course is strongly recommended prior to attending.

Course Outline

Day 1

  • Overview of Docker Security
  • Isolation: Kernel Namespaces and Control Groups
  • Intra-Platform Communication
  • Container Policy
  • Image Construction and Scanning
  • Content Trust
  • Capabilities
  • Seccomp
  • Linux Security Modules

SKU: TRNG-ONS-ESEC-00001    

 

Docker Troubleshooting and Support

Course Description

The Docker Troubleshooting and Support course is a role-based course designed for an organization’s support teams to troubleshoot the variety of issues that arise in their Docker journey. The course covers best practices to identify and remedy production issues as well as remedy resource problems and network- related issues.       

It is recommended to complete the Docker Fundamentals and the Docker for Enterprise Operations courses as prerequisite.            

Learning Objectives

By the end of the course successful learners will be able to:

Course Outline

Day 1

  • Welcome and Introduction

  • Docker Documentation, KBs, References Architectures

  • Setting up Troubleshooting Environments

  • Problem Solving Strategies

  • Analyzing the Support Dump

Day 2

  • Troubleshooting Resource Problems

  • Troubleshooting Network Problems

  • Troubleshooting UCP

  • Troubleshooting DTR

  • Various Tips and Tricks

  • Engaging Docker Support

SKU: TRNG-ONS-SPT-00001

 

Custom On-Site Training

Course Description

Custom On-Site Training based on pre-existing Docker Training Courses. Docker and Customer will meet to select a Course Outline based on pre-existing Docker Training Courses. Custom On-Site Training does not include development of custom training materials or other content specific to Customer’s environment.   

Course Outline

Course Outline selected based on pre-existing Docker Courses.
SKU: TRNG-ONS-CUST-0001

Docker Learning Credits

Course Description

The purchase of Docker Learning Credits provides Customer with an allotment of units (“Docker Learning Credits” / “DLCs”) redeemable for both Docker delivered and Docker Authorized Training Partner (DATP) delivered training services (“Services”) as set forth below.

Docker will provide Customer the allotment of DLCs set forth in the Order Form that incorporates these terms which are redeemable for certain Docker-delivered private on-site training courses as well as a limited subset of partner-delivered public open-enrollment training courses, as set forth below:

Delivered by

Delivery Method

Available Courses for Redemption

Docker

Private, on-site

https://success.docker.com/training/credits

Docker Authorized Training Partner

Public, open enrollment

https://success.docker.com/training/credits

To redeem DLCs, Customer must contact Docker at training@docker.com with the details of the redemption request. The Docker Learning Credit Redemption Agreement (“Redemption Agreement”) attached as Appendix A will then be filled out and presented to the Customer for signature. A Redemption Agreement must be executed for all DLC redemptions. Upon execution of the Redemption Agreement, Docker will deduct the number of DLCs redeemed against Customer’s overall balance of DLCs.

Assumptions

  • Any Docker delivered Services will be scheduled by mutual agreement of the parties after execution of this SOW.
  • Customer is responsible to provide and configure all hardware, software, and classroom facilities required for private on-site training and said hardware and software will be available on a timely basis for use by Docker throughout this project.
  • This SOW for services is not a part of maintenance and technical support services provided through any software services agreement between Customer and Docker.  
  • The execution of the Order Form incorporating these terms shall be deemed pre-approval for the travel expenses incurred by Docker in the course of any redemptions for private on-site training subject to any reasonable travel policies provided by Customer at redemption time.
  • Travel expenses of the Customer’s attendees associated with public open enrollment classes are the responsibility of the Customer.
  • Any provided travel policies, working times, dress codes, and all other subsequent policies provided by Customer to Docker will be adhered to by the Docker instructors delivering the Services and only may be revised with the approval of Customer and Docker.
  • Docker will provide any Docker Authorized Training Partners that are involved in the fulfillment of DLC redemptions with certain Customer information, including:
    • The full name and email address of the student(s) attending
    • Company name
    • Phone number
    • Mailing address

Consumption Rules

Customer will have a balance of DLCs subject to the following consumption rules:

  • Any DLCs not consumed within twelve (12) months from the Effective Date will expire.
  • Each individual DLC is equivalent to one United States Dollars ($1).
  • DLCs are not available for sale or resale to the United States Federal Government.
  • DLCs are non-refundable, non-transferable, and may not be redeemed for anything other than the Services listed in the table in Section 2.1 above.
  • Any discount, special offer, or coupon cannot be applied to DLC redemptions.
  • DLC redemptions are not refundable and the training to be provisioned as part of any DLC redemption is subject to the change and cancellation policies detailed at https://success.docker.com/training/credits.

Customer Responsibilities

  • Customer is responsible for ensuring it maintains appropriate backup, security and virus-checking procedures in place for any facilities Customer provides or which may be affected by Services and that any such data remains retrievable speedily and economically;
  • Customer is responsible for determining whether services meet Customer’s business requirements and comply with Customer’s applicable internal guidelines, long-term goals and any related agreements;
  • Customer is responsible for ensuring its specifications comply with applicable law;
  • Customer is responsible for obtaining any third party consents and cooperation necessary for the performance of services.
  • Customer is responsible for ensuring all DLC redemptions are conducted by authorized representatives of the Customer.

Payment

Docker shall invoice Customer upfront for DLCs. Customer shall pay invoices from Docker in accordance with the payment terms in the Master Services Agreement. Customer agrees to reimburse Docker employees' travel-related expenses associated with this SOW and any related Redemption Agreements.

Location

Any Docker-delivered on-site services shall be performed at a Customer location that meets mutually agreed to criteria between the Customer and the Docker.

SKU: TRNG-CRED-DLC-_______

EXHIBIT A
EXAMPLE LEARNING CREDIT REDEMPTION AGREEMENT

Customer confirms that the following training shall consume _______________________Docker Learning Credits (“DLCs”) as defined pursuant to the Docker Learning Credit Terms at https://www.docker.com/legal/docker-services-descriptions#/d_learning_credits as agreed to in the order dated _______________________. The remaining balance of DLCs after this redemption will be _______________________.

Redemption Date: _______________________

[ ] Private on-site class at the Customer’s location   OR [ ] Public open enrollment class

Course Name: ___________________________________________________________

Course Length: _______________________ Start Date: _______________________

Location: ______________________________________________________________________

______________________________________________________________________________

Docker Order #: _______________________

Attending Student(s):

Name: ______________________________________________ Email: ____________________________________________________

Name: ______________________________________________ Email: ____________________________________________________

Name: ______________________________________________ Email: ____________________________________________________

Name: ______________________________________________ Email: ____________________________________________________

Name: ______________________________________________Email: ____________________________________________________

Name: ______________________________________________ Email: ____________________________________________________

Name: ______________________________________________ Email: ____________________________________________________

Name: ______________________________________________ Email: ____________________________________________________

Name: ______________________________________________ Email: ____________________________________________________

Name: ______________________________________________ Email: ____________________________________________________

Name: ______________________________________________Email: ____________________________________________________

Name: ______________________________________________ Email: ____________________________________________________

Name: ______________________________________________ Email: ____________________________________________________

Name: ______________________________________________ Email: ____________________________________________________

Name: ______________________________________________ Email: ____________________________________________________

Name: ______________________________________________ Email: ____________________________________________________

Name: ______________________________________________Email: ____________________________________________________

Name: ______________________________________________ Email: ____________________________________________________

Name: ______________________________________________Email: ____________________________________________________

Name: ______________________________________________ Email: ____________________________________________________

 

I approve this Docker Learning Credit redemption and am authorized to do so.


Signed: ______________________________________________ Name: ______________________________________________

Docker Services Agreement

THIS DOCKER SERVICES AGREEMENT ("AGREEMENT") IS BY AND BETWEEN DOCKER, INC., LOCATED AT 144 TOWNSEND STREET, SAN FRANCISCO, CA 94107 ("DOCKER") AND THE INDIVIDUAL OR LEGAL ENTITY WHO HAS EXECUTED A STATEMENT OF WORK ("SOW") OR ORDER FORM (OR OTHER ORDERING OR PURCHASING DOCUMENT) REFERENCING THIS AGREEMENT OR IS USING THE APPLICABLE SERVICES MADE AVAILABLE BY DOCKER ("CUSTOMER") AND GOVERNS ALL USE BY CUSTOMER OF THE DOCKER SERVICES REFERENCED IN SUCH SOW OR ORDER FORM.

BY EXECUTING AN SOW OR ORDER FORM, CUSTOMER EXPRESSLY ACCEPTS AND AGREES TO THE TERMS OF THIS AGREEMENT. IF YOU ARE AN INDIVIDUAL AGREEING TO THE TERMS OF THIS AGREEMENT ON BEHALF OF AN ENTITY, SUCH AS YOUR EMPLOYER, YOU REPRESENT THAT YOU HAVE THE LEGAL AUTHORITY TO BIND THAT ENTITY AND "CUSTOMER" SHALL REFER HEREIN TO SUCH ENTITY. IF YOU DO NOT HAVE SUCH AUTHORITY, OR IF YOU DO NOT AGREE WITH THE TERMS OF THIS AGREEMENT, YOU MUST NOT EXECUTE THE SOW OR ORDER FORM AND YOU MAY NOT USE THE SERVICES (EACH AS DEFINED BELOW).

Docker and Customer hereby agree as follows:

  1. Service. Subject to the terms of this Agreement, Docker will deliver to the Customer the services set forth on Exhibit A attached hereto (the “Service”).
  2. Payment. In consideration for delivering the Service, Customer will pay Docker the fees set forth on the Statement of Work ("SOW") or Order Form (or other ordering or purchasing document) referencing this agreement. Unless otherwise specified in the SOW, Docker will invoice Customer in accordance with the terms above for the relevant services, unless otherwise specifically set forth in an SOW or Order Form. Customer will pay all invoices issued by Docker in full within thirty (30) days of the date of each invoice, without setoff, counterclaim, or deduction of any kind.
  3. Term and Termination. This Agreement shall go into effect as of the Effective Date and shall continue until terminated in accordance with the provisions herein (“Term”). Upon the failure to cure a breach within thirty (30) days of receipt of notice of breach, the non-breaching party may terminate this Agreement for cause. If this Agreement is terminated for any reason, Docker shall retain the fees for all work performed up to the point of termination.
  4. Intellectual Property. Docker and its licensors own and retain all right, title, and interest, including all intellectual property rights, in any material provided in the course of delivering the Service under this Agreement (“Docker Material”) including any improvements, modifications, and enhancements to it. Except for the rights expressly granted in this Agreement, Customer shall not acquire any other rights, express or implied, in or to the Docker Material, and all rights not expressly provided hereunder are reserved by Docker and its licensors.
  5. Disclaimer. The Service and any Docker material are provided “as-is.” Except to the extent prohibited by law, Docker and its affiliates make no representations or warranties of any kind, whether express, implied, statutory, or otherwise, with respect to the Service including any implied warranties of merchantability, satisfactory quality, fitness for a particular purpose, non-infringement, quiet enjoyment, any warranties that the Services will be error free or free of harmful components, and any warranties arising out of any course of dealing or usage of trade.
  6. LIMITATION OF LIABILITY. NEITHER PARTY, ITS SUBSIDIARIES AND AFFILIATES, AND ITS LICENSORS SHALL BE LIABLE TO THE OTHER PARTY FOR ANY INDIRECT, INCIDENTAL, SPECIAL CONSEQUENTIAL OR EXEMPLARY DAMAGES INCURRED BY SUCH PARTY UNDER THIS AGREEMENT, HOWEVER CAUSED AND UNDER ANY THEORY OF LIABILITY, INCLUDING, BUT NOT LIMITED TO, ANY LOSS OF PROFIT (WHETHER INCURRED DIRECTLY OR INDIRECTLY), ANY LOSS OF GOODWILL OR BUSINESS REPUTATION, ANY LOSS OF DATA SUFFERED, COST OF PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES, OR OTHER INTANGIBLE LOSS. THE FOREGOING LIMITATIONS SHALL APPLY WHETHER OR NOT A PARTY HAS BEEN ADVISED OF OR SHOULD HAVE BEEN AWARE OF THE POSSIBILITY OF ANY SUCH LOSSES ARISING. NOTWITHSTANDING THE FOREGOING, NOTHING HEREIN SHALL EXCLUDE OR LIMIT A PARTY’S LIABILITY FOR LOSSES WHICH MAY NOT BE LAWFULLY EXCLUDED OR LIMITED BY APPLICABLE LAW. DOCKER’S AGGREGATE LIABILITY ARISING WITH RESPECT TO THIS AGREEMENT SHALL NOT EXCEED THE AMOUNTS PAID BY CUSTOMER.
  7. General. Neither party may assign its rights or obligations under this Agreement without the prior consent of the other party except to an affiliate or a successor in interest. The parties are independent contractors, and nothing contained in this Agreement shall be construed to constitute the parties as partners, joint venturers, co-owners or otherwise as participants in a joint or common undertaking. This Agreement shall be governed by the laws of the State of California without reference to conflict of laws principles. Each party consents to the exclusive jurisdiction of courts of the County of San Francisco, California. Neither party shall export, directly or indirectly, any technical data acquired from the other party pursuant to this Agreement or any product utilizing any such data to any country for which the U.S. Government or any agency thereof at the time of export requires an export license or other government approval without first obtaining such license or approval. Neither party will reference the relationship with the other, including issuing formal press releases or other similar activities referencing the other party without the written consent of the other party.

Get started with Docker today.

Get started