gvisor boot error (3)

Status: fixed on 2018/12/14 04:14
Fix commit: 1775a0e11e56 container.Destroy should clean up container metadata even if other cleanups fail
First crash: 2816d, last: 2815d
▶ ▼ Similar bugs (3)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
gvisor gvisor boot error (4) -1 5 2811d 2724d 0/26 auto-closed as invalid on 2019/06/16 09:52
gvisor gvisor boot error -1 1911 2893d 2970d 0/26 fixed on 2018/10/15 18:31
gvisor gvisor boot error (2) -1 4 2817d 2865d 0/26 closed as invalid on 2018/12/12 10:27

Sample crash report:
FATAL ERROR: error running container: error creating container: error creating control server socket for sandbox NAME: aW1214 03:56:55.635604   49169 x:0] FATAL ERROR: error running container: error creating container: error creating control server socket for sandbox "ci-gvisor-ptrace-proxy-sandbox-race-test-1": address already in use
error running container: error creating container: error creating control server socket for sandbox "ci-gvisor-ptrace-proxy-sandbox-race-test-1": address already in use

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2018/12/14 03:57 https://gvisor.googlesource.com/gvisor master 5301cbf8430e fe7127be .config console log report ci-gvisor-ptrace-proxy-sandbox-race
2018/12/13 21:13 https://gvisor.googlesource.com/gvisor master 6253d32cc932 dd2fb82f .config console log report ci-gvisor-ptrace-proxy-sandbox-race
2018/12/13 09:00 https://gvisor.googlesource.com/gvisor master f484b6d4c2f1 f3d9d594 .config console log report ci-gvisor-ptrace-proxy-sandbox-race
2018/12/12 22:15 https://gvisor.googlesource.com/gvisor master f93c288dd708 02613a41 .config console log report ci-gvisor-ptrace-proxy-sandbox-race
* Struck through repros no longer work on HEAD.