# Cis Docker 2.19

> Ensure that experimental features are not implemented in production

- Skill: `cyberstrikeus/cis-docker-2-19` (Agent Skill)
- Install (CLI): `npx skillmds@latest add cyberstrikeus/cis-docker-2-19`
- Raw SKILL.md: https://api.skillmd.com/api/skills/cyberstrikeus/cis-docker-2-19/raw
- Safety review: PASS (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: cyberstrikeus (https://skillmd.com/u/cyberstrikeus)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/cyberstrikeus/cis-docker-2-19

---


# Ensure that experimental features are not implemented in production (Manual)

## Profile Applicability

• Level 1 - Docker - Linux

## Description

Experimental features should not be enabled in production.

## Rationale

"Experimental" is currently a runtime Docker daemon flag rather than being a feature of a separate build. Passing `--experimental` as a runtime flag to the docker daemon activates experimental features. Whilst "Experimental" is considered a stable release, it has a number of features which may not have been fully tested and do not guarantee API stability.

## Impact

None

## Audit Procedure

You should run the command below and ensure that the `Experimental` property is set to `false` in the Server section.

```bash
docker version --format '{{ .Server.Experimental }}'
```

## Remediation

You should not pass `--experimental` as a runtime parameter to the Docker daemon on production systems.

## Default Value

By default, experimental features are not activated in the Docker daemon.

## References

1. https://docs.docker.com/engine/reference/commandline/dockerd/

## CIS Controls

No CIS Controls mapping provided in the benchmark for this control.