Skip to content

Add note on Podman image removal behavior #3039

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Sep 19, 2025
Merged

Add note on Podman image removal behavior #3039

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
af49df0
Add note on Podman image removal behavior
hubbleview Sep 19, 2025
b7716a1
Merge branch 'main' into hubbleview-patch-2
kilfoyle Sep 19, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion ...-manage/deploy/cloud-enterprise/fresh-installation-of-ece-using-podman-hosts.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,4 +76,6 @@ This section provides guidelines and recommendations to install ECE using a Podm

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


::::{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.
::::
Loading