Closed linkdd closed 5 months ago
I believe this feature should be done on the plugin.
We should not be able to use an image for a container as long as imageID is not set.
Another use case: I am an impatient child who is clicking frenetically the "Recreate" button 🤣
If you consider #54, it is possible that many quick updates (done via CI or via an Ansible playbook that do not care about checking the journal entries to wait for things) would queue many actions at once. With a queue, everything will be done smoothly, without a queue all hell breaks loose.
Actual Behavior
While a container is being created, clicking on the "Start" will results in an error:
Desired Behavior
Actions performed on a container should be queued. This means that clicking on the "Start" button should wait for the container to be created before actually starting the container.