From 4ed7acb4c1e09c37d216b5566b4851b5f523041e Mon Sep 17 00:00:00 2001
From: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com>
Date: Thu, 26 Sep 2024 14:59:41 -0400
Subject: [PATCH] Add restriction about containerized agent on Windows (#1351)

(cherry picked from commit 86de30ad7c09b89b50d1f8fc2a0d6f20794d0c7a)
---
 .../elastic-agent/elastic-agent-container.asciidoc              | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/en/ingest-management/elastic-agent/elastic-agent-container.asciidoc b/docs/en/ingest-management/elastic-agent/elastic-agent-container.asciidoc
index 4051151a9..88d6d4f84 100644
--- a/docs/en/ingest-management/elastic-agent/elastic-agent-container.asciidoc
+++ b/docs/en/ingest-management/elastic-agent/elastic-agent-container.asciidoc
@@ -3,6 +3,8 @@
 
 You can run {agent} inside a container -- either with {fleet-server} or standalone. Docker images for all versions of {agent} are available from the https://www.docker.elastic.co/r/elastic-agent/elastic-agent[Elastic Docker registry]. If you are running in Kubernetes, refer to {eck-ref}/k8s-elastic-agent.html[run {agent} on ECK].
 
+Note that running {elastic-agent} in a container is supported only in Linux environments. For this reason we don't currently provide {agent} container images for Windows.
+
 Considerations:
 
 * When {agent} runs inside a container, it cannot be upgraded through {fleet} as it expects that the container itself is upgraded.