Skip to content

Commit a368c62

Browse files
hubbleviewkilfoyle
andauthored
Add note on Podman image removal behavior (#3039)
Clarify the behavior of image removal in Podman compared to Docker. 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. Co-authored-by: David Kilfoyle <[email protected]>
1 parent 3149398 commit a368c62

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

deploy-manage/deploy/cloud-enterprise/fresh-installation-of-ece-using-podman-hosts.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,4 +76,6 @@ This section provides guidelines and recommendations to install ECE using a Podm
7676

7777
To add a new allocator, use `--roles "allocator"`. To add a new coordinator, director, proxy, and allocator, use `--roles "allocator,coordinator,director,proxy"`
7878

79-
79+
::::{note}
80+
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.
81+
::::

0 commit comments

Comments
 (0)