-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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.
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
Fix image prune --filter cmd behavior #10390
Fix image prune --filter cmd behavior #10390
Conversation
/approve |
@jmguzik Still working ont his? |
Yes, but not enough time this week. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Drop-by-comment: please update the commit message to describe which issue it's fixing.
There is no particular issue. I just found the error, not reported it as an issue, instead opened a PR. |
c74d3a7
to
6e9528c
Compare
The challenge I have as a reader/reviewer of the commit message is that it mentions to fix something but it doesn't state what the problem actually was. |
6e9528c
to
e909a69
Compare
Added commit description with further info about the problem. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks
Image prune --filter is fully implemented in the api, http api yet not connected with the cli execution. User trying to use filters does not see the effect. This commit adds glue code to enable possiblity of using --filter in prune in the cli execution. Signed-off-by: Jakub Guzik <jakubmguzik@gmail.com>
e909a69
to
a5ad36c
Compare
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jmguzik, rhatdan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold cancel |
With the undercloud using ephemeral Heat, there will be images for ephemeral Heat in the local container storage that do not have any associated containers. Podman purge would delete these images, and they then wouldn't be available for overcloud commands. Instead, skip running the podman purge tasks on the Undercloud. This means that the local container image storage will grow over time. Given the reduced number of services on the undercloud, the storage usage is not as bad as it was previously. However, operators will need to be aware. While "podman image prune" does have a --filter option to preserve images, it does not work in the version of podman in container-tools:3.0. When the needed patch[1] is available, the podman purge tasks can be re-enabled, which would address the issue of growing local storage. [1] containers/podman@a5ad36c [2] containers/podman#10390 Change-Id: Ibd2200aa912960b267a9975571e05665a29e40f0 Signed-off-by: James Slagle <jslagle@redhat.com>
* Update tripleo-heat-templates from branch 'master' to c4aa1e3464c6a332edcf1a1abe08047f0350efa6 - Merge "Skip podman purge on Undercloud" - Skip podman purge on Undercloud With the undercloud using ephemeral Heat, there will be images for ephemeral Heat in the local container storage that do not have any associated containers. Podman purge would delete these images, and they then wouldn't be available for overcloud commands. Instead, skip running the podman purge tasks on the Undercloud. This means that the local container image storage will grow over time. Given the reduced number of services on the undercloud, the storage usage is not as bad as it was previously. However, operators will need to be aware. While "podman image prune" does have a --filter option to preserve images, it does not work in the version of podman in container-tools:3.0. When the needed patch[1] is available, the podman purge tasks can be re-enabled, which would address the issue of growing local storage. [1] containers/podman@a5ad36c [2] containers/podman#10390 Change-Id: Ibd2200aa912960b267a9975571e05665a29e40f0 Signed-off-by: James Slagle <jslagle@redhat.com>
With the undercloud using ephemeral Heat, there will be images for ephemeral Heat in the local container storage that do not have any associated containers. Podman purge would delete these images, and they then wouldn't be available for overcloud commands. Instead, skip running the podman purge tasks on the Undercloud. This means that the local container image storage will grow over time. Given the reduced number of services on the undercloud, the storage usage is not as bad as it was previously. However, operators will need to be aware. While "podman image prune" does have a --filter option to preserve images, it does not work in the version of podman in container-tools:3.0. When the needed patch[1] is available, the podman purge tasks can be re-enabled, which would address the issue of growing local storage. [1] containers/podman@a5ad36c [2] containers/podman#10390 Change-Id: Ibd2200aa912960b267a9975571e05665a29e40f0 Signed-off-by: James Slagle <jslagle@redhat.com> (cherry picked from commit 7eb280a)
Glue code added to push filters to the prune image engine method.