Seen a few instances where the container stop/start for plex_extra_tasks seems to happen too quickly after container creation/start and the stop attempt hangs and does not complete causing the playbook to exit.
Some ideas:
Create container in stopped state if there is a need to run the extra tasks
Add a delay to ensure the container has adequate time to start and complete tasks (DB migrations, etc)
Change order to setup plugins between container removal and creation
Seen a few instances where the container stop/start for
plex_extra_tasks
seems to happen too quickly after container creation/start and the stop attempt hangs and does not complete causing the playbook to exit.Some ideas: