Skip to content

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
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