Skip to content

fix: Continue deployment even if ContainerRemove call returns error#9561

Merged
mattsanta merged 1 commit into
GoogleContainerTools:mainfrom
mnk:main
Nov 15, 2024
Merged

fix: Continue deployment even if ContainerRemove call returns error#9561
mattsanta merged 1 commit into
GoogleContainerTools:mainfrom
mnk:main

Conversation

@mnk

@mnk mnk commented Nov 9, 2024

Copy link
Copy Markdown
Contributor

In some situations Podman will report that the previous container is no longer present: "no container with ID or name ..." This condition should not prevent redeployment to continue.

Fixes: #9560

Description
See issue linked above for description of the problem this PR is intended to solve.
The PR also replaces usage of deprecated type: ContainerRemoveOptions.

In some situations Podman will report that the previous container
is no longer present: "no container with ID or name ..."
This condition should not prevent redeployment to continue.

Fixes: GoogleContainerTools#9560
@mnk mnk changed the title Continue deployment even if ContainerRemove call returns error Nov 9, 2024
@mattsanta mattsanta self-assigned this Nov 15, 2024
@mattsanta mattsanta merged commit df305b3 into GoogleContainerTools:main Nov 15, 2024
plumpy added a commit to plumpy/skaffold that referenced this pull request Nov 20, 2024
@menahyouyeah menahyouyeah mentioned this pull request Mar 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

2 participants