IMO: 1. We need to determine how long docker-worker will exist. a. if we replace it with generic-worker sooner, awesome, that will fix the issue. b. if docker-worker is longer-lived, then 2. we could craft a docker-worker release with this issue fixed, and create new AMIs. We can then roll out those AMIs to test workerTypes, and see what tasks break. Once we have a list, we should fix those, and roll out completely.
Bug 1512733 Comment 16 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
IMO:
1. We need to determine how long docker-worker will exist.
a. if we replace it with generic-worker sooner, awesome, that will fix the issue.
b. if docker-worker is longer-lived, then
2. we could craft a docker-worker release with this issue fixed, and create new AMIs. We can then roll out those AMIs to test workerTypes, and see what tasks break. Once we have a list, we should fix those, and roll out completely.