Skip to content
This repository has been archived by the owner on Dec 7, 2023. It is now read-only.

runtime: Handle error when container not found #809

Merged
merged 2 commits into from
Mar 15, 2021
Merged

runtime: Handle error when container not found #809

merged 2 commits into from
Mar 15, 2021

Commits on Mar 13, 2021

  1. rm: Handle error when container not found 

    When removing a VM with force, if the container runtime returns error
when it can't find the associated VM container, the force remove fails.
With this change, ignite will checks if the container runtime error is
about container not found and return without any error, no-op, letting
the force remove succeed.
The behavior remains the same for non-forced remove.
    @darkowlzz
    darkowlzz committed Mar 13, 2021
    Configuration menu
    Copy the full SHA
    40891c5 View commit details
    Browse the repository at this point in the history

  2. Add container not found check in stop & remove 

    Add error checks in StopContainer() and RemoveContainer() to return nil
when the container is not found. This helps avoid failure when VM stop
or remove is executed and the containers don't exist anymore, resulting
in no-op and a successful stop and remove execution.
    @darkowlzz
    darkowlzz committed Mar 13, 2021
    Configuration menu
    Copy the full SHA
    6de3da1 View commit details
    Browse the repository at this point in the history