Is Docker HIPAA Compliant? Engine, Docker Hub, and the Host That Signs the BAA (2026)

Last updated: October 20, 2026

Docker is not HIPAA compliant by itself, and no container tool can be. HIPAA regulates the groups that handle patient data, not the software they run. A Docker HIPAA compliant setup is a system. It needs a host that signs a Business Associate Agreement (BAA), a hardened Docker Engine, and an app with its own safeguards. The word "Docker" also names four products, and the answer differs for each. Docker Engine is software you run. Docker Hub is a hosted service with no public BAA. We sell HIPAA compliant Docker hosting, so weigh our advice accordingly.

TL;DR: Quick answer

• Docker, Inc. publishes no HIPAA or BAA statement on its trust, compliance, legal, or pricing pages, as of October 20, 2026. Keep PHI out of Docker Hub.

• Docker Engine 29.9.2, released October 20, 2026, still runs its daemon as root by default. User namespaces, log rotation, and signature checks are off.

• Docker Content Trust is retiring. Its Notary v1 service shuts down on December 8, 2026, so sign images with cosign.

• runc fixed three container-escape flaws, each rated 7.3, on November 5, 2025. Most 2026 Critical containerd flaws sit in the plugin Kubernetes uses, but the October 13, 2026 containerd image-pull fixes apply to Docker hosts.

• AWS lists more than 170 HIPAA eligible services (list updated October 15, 2026), including Amazon ECS and AWS Fargate. Google Cloud Run is on Google's covered list. Docker HIPAA compliant workloads can run on any of them.

• If you would rather not run the host, our HIPAA compliant Docker hosting runs on single-tenant AWS from $259 a month. We sign the BAA within 24 hours of signup.

Is Docker HIPAA compliant? The three-layer answer

A Docker HIPAA compliant system has three layers, and each needs an owner. The first is the contract. A vendor that stores or processes protected health information (PHI) for a covered entity is a business associate under 45 CFR § 160.103. Under 45 CFR § 164.308(b), it must sign a BAA first. The second layer is the host. It runs disk encryption, backups, and patching, plus the daemon, runtime, and log files. The third layer is your app and team. Most of the five technical safeguards in 45 CFR § 164.312 land in the app. Docker has no user accounts, no PHI audit trail, and no encryption of patient data. You also run a risk analysis under 45 CFR § 164.308(a)(1).

Docker Engine is software you run, so it cannot sign anything. Docker Hub could sign, but it publishes no BAA. So the Docker HIPAA compliant answer lands on the host that runs your containers. The same goes for containers that run AI agents or chatbots, as our guide to hosting AI workflows under a BAA explains.

Which Docker are you asking about?

Four products share the name, and the Docker HIPAA compliant answer differs for each.

This guide covers Docker HIPAA compliant use of Engine in production, plus Docker Hub. Desktop's Business features protect laptops, not servers.

What Docker Engine gives you for the HIPAA technical safeguards

Here is how Docker Engine maps to 45 CFR § 164.312. The last column is what a Docker HIPAA compliant host still needs.

dockerd is the Docker daemon, the background service that runs containers. docker events is a command that streams what the daemon does, but it saves nothing. auditd, the Linux audit service, fills that gap by recording who touched the daemon. Our entry on audit logging covers what a PHI audit trail must record.

Docker Engine also encrypts nothing at rest. Images, volumes, and logs sit in plain files under /var/lib/docker, Docker's data folder. So every Docker HIPAA compliant plan needs host disk encryption, as encryption at rest and in transit explains.

Does Docker, Inc. sign a BAA?

Not publicly. As of October 20, 2026, Docker's trust, compliance, legal, and pricing pages never mention HIPAA or a BAA. The compliance page says its SOC 2 Type 2 report covers Docker Desktop, Hub, Scout, Build Cloud, Testcontainers Cloud, Docker Hardened Images, and Offload. A SOC 2 report is an audit, not a BAA.

Docker Hub cannot hold an image with PHI, even in a private repo. A Docker HIPAA compliant image belongs in a registry under a BAA. Amazon ECR is on AWS's HIPAA eligible list, updated October 15, 2026. Google Artifact Registry is on Google Cloud's covered products list, checked October 20, 2026.

Docker Hub activity logs, on Team and Business plans, record registry admin work, not anyone viewing PHI. They do not meet 45 CFR § 164.312(b).

Which Docker defaults to change before a container touches PHI?

Change each of these defaults before a Docker HIPAA compliant host goes live.

daemon.json is the Docker daemon's settings file. Adding "userns-remap": "default" maps container root to a host user with no power. json-file is the default log driver, which writes all container output to a host file. Docker's docs recommend the local driver, which rotates logs by default. DOCKER_CONTENT_TRUST makes the client refuse unsigned images, but its Notary service ends December 8, 2026.

The Compose docs warn that secrets in environment variables mean you "risk unintentional information exposure". A .env file, the text file Compose reads variables from, carries the same risk. Self-hosted n8n is configured through environment variables too, often including the key that encrypts its stored credentials. Our guide to an n8n HIPAA compliant setup covers where that key belongs and the run data n8n saves by default.

Which Docker versions are safe to run?

A Docker HIPAA compliant host runs only the newest patched line. As of October 20, 2026, the newest Docker Engine is 29.9.2, released that day. It updates the Go runtime to reject certificate chains that include eight revoked eMudhra intermediate certificates (CVE-2026-111943). Registries whose chains rely on them need new certificates, or image pulls and pushes fail. Docker Desktop 4.96.0 shipped October 19, 2026, with Engine 29.9.1 and containerd 2.4.2. Engine 29.8.2, released September 30, 2026, fixed 3 Engine CVEs and 10 in BuildKit, Docker's image builder. One let a malicious DNS response make registry connections skip TLS checks, which could expose registry credentials or swap images. Engine 29.9.0, released October 8, 2026, fixed five more CVEs through a Go runtime update.

runc is the low-level tool that starts each container. On November 5, 2025, it fixed three container-escape flaws: CVE-2025-31133, CVE-2025-52565, and CVE-2025-52881. Each let a malicious image or container config break out to the host. A low-severity fix followed on June 13, 2026. Run runc 1.3.6, 1.4.3, or later.

containerd sits between Docker Engine and runc. Its 2026 Critical advisories are mostly in the CRI plugin, which Kubernetes uses and plain Docker Engine does not. Image pulls are another matter. On October 13, 2026, containerd published Moderate flaws that let a crafted image or registry crash containerd or fill the host disk. Run containerd 2.2.10, 2.3.7, or 2.4.2 or later, depending on your release line. Those versions also cover CVE-2026-53488, CVE-2026-53489, and the Critical CRI flaw published September 1, 2026. The runc advisory list showed nothing newer than June 13, 2026 when we checked on October 20, 2026.

Docker Engine 28.x had its last release on November 5, 2025. Docker's install docs say Docker doesn't provide support for Docker Engine; the Moby project maintainers and community do. The docs give no end-of-life dates for Engine versions. Treat 28.x as unsupported in your HIPAA risk analysis. A Docker HIPAA compliant host patches Engine, runc, and containerd together.

The 8 settings that make a Docker host HIPAA-ready

Apply these eight settings before a Docker HIPAA compliant host takes on PHI.

1. Run rootless, or remap users. Run dockerd-rootless-setuptool.sh install, Docker's setup script for a daemon without root. If that will not fit, set userns-remap.

2. Keep the daemon local. Leave it on /var/run/docker.sock, its local socket file. For remote access, use --tlsverify, which demands client certificates. Never mount docker.sock into a container.

3. Rotate or ship the logs. Use the local driver, or set max-size and max-file on json-file to cap file size and count. To ship logs, use awslogs (CloudWatch Logs) or gcplogs (Google Cloud Logging) under a BAA, with PHI redacted. Rotation caps files by size, not age, so decide how long to keep HIPAA logs first, then set retention in the log service to match.

4. Move secrets out of environment variables. Use Swarm secrets or the Compose secrets: key, which mounts each secret as a file under /run/secrets inside the container. For builds, use the Dockerfile option RUN --mount=type=secret, so secrets never land in a layer.

5. Encrypt disks and backups. Put /var/lib/docker on an encrypted EBS volume or LUKS, the standard Linux disk encryption. Back up volumes to encrypted storage under a BAA.

6. Pin and sign images. Pull images by digest, not tag. Sign your own with cosign, the Sigstore signing tool, and scan them.

7. Use a private registry under a BAA. Amazon ECR, Google Artifact Registry, or your own registry on a covered server.

8. Audit the host and patch on a schedule. Run docker-bench-security, Docker's free script that checks a host against the CIS Docker Benchmark v1.6.0. Add auditd rules for dockerd and docker.sock. Patch Engine, runc, and containerd on a set cadence.

Item 5 ties to HIPAA backup and disaster recovery. Items 2 and 8 are host work, covered in HIPAA compliant server. With all eight done, the Docker layer of a Docker HIPAA compliant stack is in place.

Where Docker deployments leak PHI

Each leak breaks a Docker HIPAA compliant setup, even with a signed BAA.

• Container logs. Apps that log request bodies write PHI into unrotated, unencrypted host files. docker logs, the command that prints a container's output, reads them back.

• Environment variables. docker inspect, which prints a container's settings, shows its environment to anyone with daemon access.

• Data baked into layers. Copying a folder with a database dump into an image ships that data with every push.

• Images on Docker Hub. A public repo can be pulled by anyone. A private one sits with a vendor that has no BAA.

• An exposed docker.sock. A container with the socket mounted controls the host and every volume on it.

• Unencrypted volumes and snapshots. Volumes are plain folders. Snapshots and tar backups copy that PHI unless disks and backup targets are covered.

Container-based CMS builds face the same leaks, as our Ghost CMS HIPAA compliant and Payload CMS HIPAA compliant guides show. Containerized databases need HIPAA compliant database hosting care too.

Compiled PHP extensions make a case for containers. Our guide to whether Phalcon HIPAA compliant apps are possible explains why: you build Phalcon into your image once, so every deploy runs the same version. A server that updates PHP but not the extension stays exposed.

Who signs the BAA for a Docker app, and what does it cost?

Your host does. Docker, Inc. does not, and Docker Engine cannot. We checked each platform's own pages on October 20, 2026.

We sell the last row, so weigh it as a disclosure. DigitalOcean lists Droplets, Kubernetes, Load Balancers, and Spaces Object Storage among its HIPAA eligible products. AWS App Runner is not on AWS's eligible list, so keep PHI containers off it. See is AWS HIPAA compliant for the AWS picture. Whichever row you choose, budget staff hours for the eight settings and the patching a Docker HIPAA compliant host needs. Ask each host which of them it handles.

If you would rather not run the host yourself

Most teams want to ship their app, not run the server under it. Our HIPAA compliant Docker hosting runs your containers on single-tenant AWS, on our Performance tier from $259 a month. Every plan includes encryption at rest and in transit, a web application firewall, CloudFront CDN, six-year audit logging, and tested encrypted backups. Storage runs on EBS with 7-day snapshot retention. We sign the BAA within 24 hours of signup, before patient data moves. Our BAA covers the servers and services we run. Your first month includes 4 hours of migration and configuration. Extra work after that is $175 an hour, quoted before work starts. Plans are monthly, with no long-term contract. We sell this, so weigh it as a disclosure.

Here is the honest inverse. If a platform engineer runs your containers on ECS or Fargate under AWS's BAA, that path works, and you do not need us. If a container never touches PHI, none of this applies, and it does not need to be Docker HIPAA compliant. For everyone else, our HIPAA compliant hosting plans are public. Know the limits first. Each plan is one server in one AWS availability zone, and a multi-zone design is quoted separately. Root access comes only through an Enterprise engagement. HIPAA Compliant Hosting does not hold SOC 2 or HITRUST certification. You can request a quote or tell us what your containers do.

Frequently asked questions

Is Docker HIPAA compliant out of the box?

No. Docker Engine runs as root, keeps logs unrotated and unencrypted, and leaves signature checks off by default. A Docker HIPAA compliant setup needs a host that signs a BAA, hardened daemon settings, and encrypted disks.

Does Docker, Inc. sign a BAA?

Not publicly. As of October 20, 2026, Docker's trust, compliance, legal, and pricing pages do not mention HIPAA or a BAA. A SOC 2 report is not a BAA.

Can I store images with PHI on Docker Hub?

No. Docker Hub has no public BAA, so even a private repository holding PHI is a disclosure to a vendor without one. Keep PHI out of images, and use a registry under a BAA, such as Amazon ECR.

Is AWS ECS or Fargate HIPAA eligible?

Yes. AWS lists 174 HIPAA eligible services as of its October 15, 2026 update, and Amazon ECS, AWS Fargate, Amazon EKS, and Amazon ECR are among them. Accept the AWS BAA first. Eligible does not mean compliant. AWS says customers must still configure each service to meet HIPAA. AWS App Runner is not on the list.

Can I run an EHR in a container?

Yes. OpenEMR publishes an official Docker image, so an electronic health record runs on a Docker host like any other app. The container changes nothing about who signs: your host signs for the server. Installing, patching and upgrading the EHR stays with you or a support partner, and hosting never certifies it. Size the host by users and document storage rather than record count. Our guide to HIPAA compliant EHR hosting sets that route against a vendor cloud EHR.

Docker or Kubernetes for HIPAA?

Either can work. Kubernetes talks to containerd directly, not to the Docker daemon. Managed Kubernetes, such as EKS or GKE, runs under the cloud's BAA. For one app, a Docker HIPAA compliant host is simpler to audit than a cluster.

Recap: Docker HIPAA compliant

To recap, Docker HIPAA compliant is a property of the system, not the software. Docker, Inc. offers no public BAA, so keep PHI off Docker Hub. Run Engine 29.9.2 or later with patched runc and containerd, apply the eight settings, and get a BAA from your host.

This article is general information, not legal advice. Docker's docs and release notes, runtime advisories, cloud HIPAA lists, and platform pages were checked on October 20, 2026. Confirm current terms with each vendor, consult qualified counsel, and base your safeguards on a documented risk analysis. We sell HIPAA compliant hosting. Reviewed October 2026.

Sources

• Docker, Inc.: Pricing, Trust, Compliance.

• Docker releases: Engine 29, Engine 28, Desktop.

• Docker support and licensing: Engine install and licensing, Release lifecycle.

• Docker security docs: Rootless mode, User namespaces, Daemon access.

• Docker signing and logs: Content trust, Logging, Hub activity logs.

• Docker secrets: Swarm secrets, Compose secrets.

• Runtime and audit: runc advisories, containerd advisories, Docker Bench for Security.

• Clouds: AWS eligible services, Google Cloud HIPAA, Azure HIPAA.

• Platforms: Fly.io, Railway, DigitalOcean.

• Render: HIPAA workspaces, Pricing.

• HIPAA rules: 45 CFR § 160.103, 45 CFR § 164.308, 45 CFR § 164.312.