Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 25.5

Docker Desktop Pro / Team / Business

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	Docker Desktop is an application for use on Mac, Linux, or Windows environment. This technology gives users the ability to build, share, and run containerized applications and microservices. Docker Desktop provides a straightforward GUI (Graphical User Interface) that allows users to manage their containers, applications, and images directly from their machines. This entry covers the paid editions: Pro, Teams, and Business. The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g., VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e., SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at: https://dvagov.sharepoint.com/sites/OITECSO
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information System Security Officer (ISSO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v25.5
Decision Date:	05/20/2025 at 19:03:19 UTC
Introduced By:	TRM Request
Vendor Name:	Docker, Inc.

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

You must be logged into the RSAA website prior to clicking the Attestation URLs or the URLs won't open.

Major versions and minor versions of that Major released on or after 09/14/2022 are NOT EXEMPT. Major Versions released before 09/14/2022 are EXEMPT as well as minor versions of that Major regardless of release date.

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
4.x (Windows)	08/31/2021
4.x (Mac & Linux)	08/31/2021

Current Decision Matrix (05/08/2025)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information System Security Officer (ISSO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VAIT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported.

Legend:

White	Authorized: The technology/standard has been authorized for use.
Yellow	Authorized w/ Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Authorized w/ Constraints (POA&M): This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Authorized w/ Constraints (DIVEST): VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unauthorized may be found on the Decision tab for the specific entry.
Black	Unauthorized: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Authorized w/ Constraints (PLANNING/EVALUATION): The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology authorized with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology authorized with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

Any major.minor version that is not listed in the VA Decision Matrix is considered Authorized w/ Constraints (POA&M).

<Past

CY2024

CY2025

CY2026

Future>

Release

4.x (Windows)

Unapproved

Authorized w/ Constraints (POA&M)

4.x (Mac & Linux)

Unapproved

Approved w/Constraints
[1, 2, 3, 4, 5, 6]

Authorized w/ Constraints
[1, 2, 3, 4, 5, 6]

Authorized w/ Constraints
[2, 3, 4, 5, 6, 7, 8, 9, 10]

Note:

At the time of writing, version 4.41.2 is the most current version, released 05/06/2025.
The Microsoft version is not authorized for use.

Decision Constraints


[1]	This technology is unapproved to be used with Windows Operating Systems (OS) Users must not utilize Windows Subsystem for Linux (WSL), as it is at the time of writing, unapproved in the TRM. Users must not utilize Hyper-V, as it is at the time of writing, unapproved in the TRM. Users must ensure that VMware vSphere is implemented with VA-authorized baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’) Moby framework is a dependency of Docker Desktop and has not be evaluated by the TRM. Per the Security Assessment Review (SAR), users must abide by the following constraints: For full support and functionality of the application, Docker Desktop should only be installed on physical systems. To mitigate, the ISSO shall educate and prohibit users from using the integrated cloud service capability until the VA Cloud Security Requirements have been met and the affected A&A package has been appropriately updated. To mitigate, System Administrators shall uncheck the option under Docker Desktop > General > Send usage statistics. Maintenance and support will be provided for the Open Source Software used within Docker Desktop v4.x as per the application’s lifecycle. To mitigate, the administrator shall control the versioning of Docker Desktop v4.x software and not allow users to install unapproved versions. To disable, Settings > uncheck “Automatically check for updates” To mitigate, these technologies may not be utilitzed in VA unless the projects wishing to use them have obtained an authorized POA&M.

[2]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500.

[3]	Users should check with their supervisor, Information System Security Officer (ISSO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not authorized and the user should take the proper steps to decline those installations.

[4]	Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities.

[5]	This technology has received one or more VA security bulletins that provide specific guidance on vulnerability patching and mitigation. It is the responsibility of VA system owners to ensure that the appropriate mitigations are taken to address all known and future discovered vulnerabilities with this product. See the Reference tab for more information on security bulletins related to this product.

[6]	The Federal Information Processing standards (FIPS) 140-2 certification status of this technology was not able to be verified. This technology will require a 3rd party FIPS 140-2 or 140-3 certified solution for any data containing PHI/PII or VA sensitive information, where applicable. More information regarding the Cryptographic Module Validation Program (CMVP) can be found on the NIST website.

[7]	Users must not utilize Hyper-V Server (Stand-alone Edition), as it, at the time of writing, requires a POA&M. This technology should not be used with Open Java Development Kit (OpenJDK) as it requires a POA&M. There are other authorized java environments available. See Category tab for details. Users must not utilize Windows Subsystem for Linux (WSL), as it, at the time of writing, requires a POA&M. Users must ensure that VMware vSphere and My Structured Query Language (MySQL) Database - Commercial Editions are implemented with VA-authorized baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’) Moby framework is a dependency of Docker Desktop and has not be evaluated by the TRM. Per the Security Assessment Review (SAR), users must abide by the following constraints: “Nested virtualization scenarios, such as running Docker Desktop on a VMWare or Parallels instance might work, but there are no guarantees. Docker Desktop is not supported in nested virtualization scenarios.” As the ESECVS test environment is entirely comprised of a VMware infrastructure, although engineers were able to install Docker Desktop on the test virtual machine, they were not able to successfully launch the application. To mitigate, for full support and functionality of the application, Docker Desktop should only be installed on physical systems. Docker Desktop v4.x utilizes commercial cloud computing services. To mitigate, the ISSO shall educate and prohibit users from using the integrated cloud service capability until the VA Cloud Security Requirements have been met and the affected A&A package has been appropriately updated. A vulnerability exists because Docker Desktop v4.x includes a Software Improvement Program which automatically sends various types of information back to the Vendor. To mitigate, System Administrators shall uncheck the option under Docker Desktop > General > Send usage statistics. A vulnerability exists because Docker Desktop v4.x is Open Source Software (OSS). OSS may be used if there is adequate maintenance and support. As a condition of certification, Sponsor/Software admin personnel shall maintain and monitor the distribution of Docker Desktop v4.x software. The software shall be physically stored in Sponsor/Software admin software library for quality control. A vulnerability exists because Docker Desktop v4.x provides automatic/user configurable checks for updates. To mitigate, the administrator shall control the versioning of Docker Desktop v4.x software and not allow users to install unapproved versions. To disable, Settings > uncheck “Automatically check for updates”. A vulnerability exists because Docker Desktop v4.x uses WSL2 (Windows Subsystem for Linux) and Hyper-V. WSL2 and Hyper-V are Unapproved on the VA Technical Reference Model (TRM). To mitigate, these technologies may not be utilitzed in VA unless the projects wishing to use them have obtained an approved POA&M.

[8]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 or its successor to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 or 140-3 compliant full disk encryption (FOE) must be implemented on the storage device where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). By September 22, 2026, all FIPS 140-2 certificate validations will be placed on the Historical List, please refer to FIPS Transition Effort for further guidance and timeline of changes.

[9]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request, visit the Product Marketplace. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[10]	If this product uses a MySQL database, the product must be configured with a commercial edition of the MySQL Database, which currently has TRM constraints limiting its use for intranet and non-sensitive data only due to its many known security issues. If a commercial edition of MySQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High-Risk system. See MySQL Database – Commercial Edition TRM entry for more details.

Technology Components

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.

Name	Description
Docker Buildx Build	The docker build command builds Docker images from a Dockerfile and a `context`. A build`s context is the set of files located in the specified PATH or URL. The build process can refer to any of the files in the context.
Docker Command Line (CLI)	The base commands for the Docker.
Docker Compose	One can use the compose subcommand, docker compose [-f ...] [options] [COMMAND] [ARGS...], to build and manage multiple services in Docker containers.
Docker Kubernetes	Kubernetes is an open source orchestration system for automating the management, placement, scaling and routing of containers.


Application Technology Application and Web Server Software	Application Server Software

General Analysis

Adoption Benefits

This technology is available at no cost through open-source licensing and supports VA`s open source initiative.
This technology has a comprehensive set of documentation.
This technology utilizes built-in Authentication and Authorization (A&A) capabilities.
This technology may improve productivity for specific staff whose responsibilities include container creation and management.
This technology is compatible with multiple other Technical Reference Model (TRM) technologies and standards used by the organization.

Adoption Risks

This technology can integrate with and alter database technologies.
This product can be configured with a MySQL Commercial Edition Database, which currently has TRM constraints limiting its use to Red Hat Enterprise Linux (RHEL) only due to its many known security issues on other platforms.
As open-source software, this product may be left without clearly defined support options which may result in suboptimal enterprise level support.
There are Threat & Assessment Analysis Portal (TAAP) bulletins associated with this technology.
The potential exists to store Personally Identifiable Information (PII), Protected Health Information (PHI) and/or VA Sensitive data and proper security standards must be followed in these cases.
Due to the rapid release schedule of this technology, the VA may be unable to update to the most recent patch and may require a deployment model requiring the use of specific versions.
There is no indication based on either the vendor documentation or the Cryptographic Module Validation Program (CMVP) that this technology is Federal Information Processing Standard (FIPS) 140-2 compliant.
There are known Common Vulnerabilities and Exposures (CVEs) associated with this technology. Please see https://nvd.NIST.gov/vuln/search for more details.
This technology can potentially use Hyper-V Server (Stand-alone Edition) which requires a POA&M for use on the VA network.
This technology can potentially use Open Java Development Kit (OpenJDK), a protocol which requires a POA&M for use on the VA network.
This technology can potentially use Windows Subsystem for Linux (WSL) which requires a POA&M for use on the VA network.
IPR/SAR Adoption Risk - Docker Desktop v4.x utilizes commercial cloud computing services. To mitigate, the ISSO shall educate and prohibit users from using the integrated cloud service capability until the VA Cloud Security Requirements have been met and the affected A&A package has been appropriately updated.
IPR/SAR Adoption Risk - A vulnerability exists because Docker Desktop v4.x includes a Software Improvement Program which automatically sends various types of information back to the Vendor. To mitigate, System Administrators shall uncheck the option under Docker Desktop > General > Send usage statistics.
IPR/SAR Adoption Risk - A vulnerability exists because Docker Desktop v4.x is Open Source Software (OSS). OSS may be used if there is adequate maintenance and support. As a condition of certification, Sponsor/Software admin personnel shall maintain and monitor the distribution of Docker Desktop v4.x software. The software shall be physically stored in Sponsor/Software admin software library for quality control.
IPR/SAR Adoption Risk - A vulnerability exists because Docker Desktop v4.x provides automatic/user configurable checks for updates. To mitigate, the administrator shall control the versioning of Docker Desktop v4.x software and not allow users to install unapproved versions. To disable, Settings > uncheck “Automatically check for updates”.
IPR/SAR Adoption Risk - A vulnerability exists because Docker Desktop v4.x uses WSL2 (Windows Subsystem for Linux) and Hyper-V. WSL2 and Hyper-V are Unapproved on the VA Technical Reference Model (TRM). To mitigate, these technologies may not be utilitzed in VA unless the projects wishing to use them have obtained an approved POA&M.
IPR/SAR Adoption Risk - “Nested virtualization scenarios, such as running Docker Desktop on a VMWare or Parallels instance might work, but there are no guarantees. Docker Desktop is not supported in nested virtualization scenarios.” As the ESECVS test environment is entirely comprised of a VMware infrastructure, although engineers were able to install Docker Desktop on the test virtual machine, they were not able to successfully launch the application. To mitigate, for full support and functionality of the application, Docker Desktop should only be installed on physical systems.

Architectural Benefits

This technology is compatible with virtual machines, therefore consistent with the enterprise Server Virtualize First Policy (VAIQ 7266972 08-27-2012).
This technology is portable as it runs on multiple TRM-authorized operating systems.

Architectural Risks

Moby framework is a dependency of Docker Desktop and has not be evaluated by the TRM.
This technology includes cloud-based functionality which has potential information security risks.
This technology does not use a VA-preferred database to store data.

- The information contained on this page is accurate as of the Decision Date (05/20/2025 at 19:03:19 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 25.5

General Information

Vendor Release Information

Current Decision Matrix (05/08/2025)

Decision Constraints

References

Technology Components

VA Categories

View the VA Categorization Framework

Open Source

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 25.5

General Information

Vendor Release Information

Current Decision Matrix (05/08/2025)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES

VA Categories

View the VA Categorization Framework