pdoman stop/kill does not stop container
Bug #1801886 reported by
Rabi Mishra
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| paunch |
Invalid
|
Undecided
|
Unassigned | ||
| tripleo |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
With https:/
podman stop <container> and podman kill <container> restarts the container.
I know the expected way to start stop is to use systemd units for containers. But this is going to be different from the way things work with docker. Atleast we should document that in the debugging/
Revision history for this message
| Emilien Macchi (emilienm) wrote | #1 |
| Changed in tripleo: | |
| status: | New → Invalid |
| Changed in paunch: | |
| status: | New → Invalid |
To post a comment you must log in.
This is not a bug but how it works now. The deletion will be done in this patch: https:/
We didn't want to remove the container before all the upgrade process is finished, in case the operator needs to rollback. I'm closing this bug.
However, thanks for checking how it works, it's appreciated!