From 31aad4dc0805dcaf6bf3eca3cfc48bd0a79b1d2c Mon Sep 17 00:00:00 2001
From: Susie Wen <35361142+hubbleview@users.noreply.github.com>
Date: Thu, 18 Sep 2025 17:17:04 -0700
Subject: [PATCH] Clarify image removal process for Podman vs Docker

Added note about Podman image removal behavior compared to Docker.
---
 .../deploy/cloud-enterprise/migrate-ece-to-podman-hosts.md    | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/deploy-manage/deploy/cloud-enterprise/migrate-ece-to-podman-hosts.md b/deploy-manage/deploy/cloud-enterprise/migrate-ece-to-podman-hosts.md
index a69b4b4132..1cee5751a0 100644
--- a/deploy-manage/deploy/cloud-enterprise/migrate-ece-to-podman-hosts.md
+++ b/deploy-manage/deploy/cloud-enterprise/migrate-ece-to-podman-hosts.md
@@ -521,3 +521,7 @@ Using Docker or Podman as container runtime is a configuration local to the host
     5. Remove the Docker allocator by following the [Delete Hosts](../../maintenance/ece/delete-ece-hosts.md) guidelines.
 
     As an alternative, use the [Delete Runner](https://www.elastic.co/docs/api/doc/cloud-enterprise/operation/operation-delete-runner) API.
+
+::::{note}
+When using Podman, removing an image with the `--force` (`-f`) option not only deletes the image reference but also removes any containers that depend on that image. This behavior differs from Docker, where forced image removal does not automatically remove running or stopped containers. Therefore, avoid using the `--force` (`-f`) option with the `docker rmi` command.
+::::