You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
race condition where both try to spawn and 1 fails because the other got there first...(and the failing one should have done docker-exec instead of docker-run). would need mutex/semaphore but not sure we can give a damn.
equally it can happen that 2nd container sees that docker-run is already started and then tries docker-exec but the started one gets killed by the destructor.sh before docker-exec kicks in. Do we care and mutex it?
The text was updated successfully, but these errors were encountered:
race condition where both try to spawn and 1 fails because the other got there first...(and the failing one should have done docker-exec instead of docker-run). would need mutex/semaphore but not sure we can give a damn.
equally it can happen that 2nd container sees that docker-run is already started and then tries docker-exec but the started one gets killed by the destructor.sh before docker-exec kicks in. Do we care and mutex it?
The text was updated successfully, but these errors were encountered: