Skip to content
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: Continue deployment even if ContainerRemove call returns error #9561

Merged
merged 1 commit into from
Nov 15, 2024

Conversation

mnk
Copy link
Contributor

@mnk mnk commented Nov 9, 2024

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 fix: 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
11 checks passed
plumpy added a commit to plumpy/skaffold that referenced this pull request Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Skaffold fails to redeploy docker container with message: failed to remove old container
2 participants