From e5335fd74c7ed6fe0fa55bf33afbdab23ed687f1 Mon Sep 17 00:00:00 2001 From: Matthew Heon Date: Wed, 5 Dec 2018 09:25:44 -0500 Subject: Remove --sync flag from `podman rm` Per discussion with Dan, it would be better to automatically handle potential runtime errors by automatically syncing if they occur. Retaining the flag for `ps` makes sense, as we won't even be calling the OCI runtime and as such won't see errors if the state desyncs, but rm can be handled automatically. The automatic desync handling code will take some additional work so we'll land this as-is (sync on ps is enough to solve most desync issues). Signed-off-by: Matthew Heon --- docs/podman-rm.1.md | 7 ------- 1 file changed, 7 deletions(-) (limited to 'docs') diff --git a/docs/podman-rm.1.md b/docs/podman-rm.1.md index 57274c523..56664a8c1 100644 --- a/docs/podman-rm.1.md +++ b/docs/podman-rm.1.md @@ -24,13 +24,6 @@ Remove all containers. Can be used in conjunction with -f as well. Instead of providing the container name or ID, use the last created container. If you use methods other than Podman to run containers such as CRI-O, the last started container could be from either of those methods. -**--sync** - -Force a sync of container state with the OCI runtime before attempting to remove the container. -In some cases, a container's state in the runtime can become out of sync with Podman's state, -which can cause Podman to refuse to remove containers because it believes they are still running. -A sync will resolve this issue. - **--volumes, -v** Remove the volumes associated with the container. (Not yet implemented) -- cgit v1.2.3-54-g00ecf