Closed yousefamar closed 7 years ago
It seems that this happens in dev mode only when a container ends unnaturally by crashing rather than exiting. The workaround is to manually rm -rf slaStore/stadatastore.db
but there may be a way to handle that and remove the SLA automatically as normal.
When removing a container through the dashboard, the previously made SLA remains, so the next time it's launched, and the user goes through the SLA flow again, the new one can't be saved because "it violates the unique constraint". (Alternatively, the old one could be automatically replaced).