Add Container Environments page

Author: JoshuaMoelans

docs/platforms/native/advanced-usage/container-environments/index.mdx

@@ -0,0 +1,32 @@
+---
+title: Container Environments
+description: "How to use the Sentry Native SDK in container environments."
+sidebar_order: 2000
+---
+
+## Database-path on a mounted volume
+The Sentry Native SDK uses a [database path](https://docs.sentry.io/platforms/native/configuration/options/#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
+Since SDK version [0.8.3](https://github.com/getsentry/sentry-native/releases/tag/0.8.3) the [option `crashpad_wait_for_upload`](https://docs.sentry.io/platforms/native/configuration/options/#crashpad-wait-for-upload) enables waiting for the `crashpad_handler` (on Linux) to finish its work before a shutdown-after-crash.
+
+
+In SDK versions before 0.8.3, one could use a script similar to the example below to tie container shutdown to the `crashpad_handler` process.
+```bash
+#!/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
+```