> FWIW, when denying the request to wootric, the docker daemon crashes.
A yes, this about fits the standard of engineering I've come to expect from Docker.
Anyway, I couldn't find any references too "woocentric" anywhere in the code; looks like this part isn't open source? I did find this other issue: https://github.com/docker/for-win/issues/12718 with a comment from May 2022:
"At some point we found out that bugsnag was actually sending a «session creation» request of some sort when initialized, even if no crash was actually being reported. We believed we had fixed that, but I just checked with a MITM proxy and it appears to have regressed… There may be some other services doing something similar without us realizing (wootric, …).
We have created a ticket in our internal backlog to review all this."
Original issue reporter here. I can't believe how long this has been open and unaddressed. I haven't checked if it still does this for a while but I wouldn't be surprised if it does.
7 comments
[ 3.1 ms ] story [ 28.6 ms ] threadThey definitely have enough even with the people opted out.
A yes, this about fits the standard of engineering I've come to expect from Docker.
Anyway, I couldn't find any references too "woocentric" anywhere in the code; looks like this part isn't open source? I did find this other issue: https://github.com/docker/for-win/issues/12718 with a comment from May 2022:
"At some point we found out that bugsnag was actually sending a «session creation» request of some sort when initialized, even if no crash was actually being reported. We believed we had fixed that, but I just checked with a MITM proxy and it appears to have regressed… There may be some other services doing something similar without us realizing (wootric, …).
We have created a ticket in our internal backlog to review all this."