Description

We use sentry.io since a few days and everything works very good. Thank you for your great product. Due to this comment (#534 (comment)) we thought it might be a good idea to also use crashpad on Linux and therefore also in our Docker'ed Linux builds to keep things streamlined between all platforms. Unfortunately crashpad doesn't play well with docker, because after our main process (PID 1) crashes Docker will immediately stop the container. This seem to happen before crashpad is able to send out the report. Also there seems to be no mechanism to send the report later on after Docker restarted the Container (like breakpad does by default)

Is my assumption right? What would be your advise for this situation?

Also if you want to make crashpad the default on Linux i would suggest to document this small stumbling block which we were surprised by, but seems logic after reading the differences between crashpad/breakpad.

We now stick to breakpad which is working as expected.

When does the problem happen

• After capturing a hard crash

Environment

• OS: Ubuntu 20.04 (running in Docker)
• Compiler: GCC 9.x
• Sentry 0.4.9

Steps To Reproduce

Start any sentry native (w/crashbad packend) application inside docker as the main process, let it crash and there won't be any crash report uploads to sentry.io, because the container will automatically terminate.