Container Environments

Database Path on a Mounted Volume

The Sentry Native SDK uses a database path to store events and crash reports. When you are using a containerized environment, you may want to mount a volume to persist the database across container restarts to avoid losing this data.

Waiting for Crashpad to Finish

Starting with SDK version 0.8.3, the option crashpad_wait_for_upload allows the application (on Linux) to wait for the crashpad_handler to finish before a shutdown-after-crash.

In SDK versions older than 0.8.3, you could use a script similar to the example below to tie container shutdown to the crashpad_handler process:

#!/bin/bash

# ./execute-main-app

crashpad_timeout_s=10
crashpad_process_name=crashpad_handler
crashpad_pid=$(pgrep -n -f $crashpad_process_name)
if [ -n "$crashpad_pid" ]; then
    echo "Waiting for crashpad to finish..."
    timeout $crashpad_timeout_s tail --pid=$crashpad_pid -f /dev/null
    if [ $? -eq 124 ]; then
        echo "The crashpad process did not finish within $crashpad_timeout_s seconds"
    else
        echo "The crashpad process finished successfully"
    fi
fi