Tag: Container Crash
Failures causing container crashes or unexpected terminations.
| ID | Title | Description | Category | Technology | Tags |
|---|---|---|---|---|---|
| CRE-2025-0099 High Impact: 8/10 Mitigation: 7/10 | Redpanda Crash Due to Memory Exhaustion and Startup Failures | Redpanda streaming platform crashes due to a combination of system-level failures including permission denied errors for performance monitoring subsystems, missing critical configuration files, and memory allocation failures. | Data Streaming Platforms | redpanda | RedpandaContainer CrashMemory ExhaustionConfiguration FailureStreaming PlatformKafka CompatiblePermission DeniedSIGKILL |
| CRE-2025-0130 High Impact: 9/10 Mitigation: 3/10 | Supabase Self-Hosted: Postgres Container Fails to Start Due to Port Conflict | Detects when Supabase self-hosted Postgres container fails to start because another service is already using port 5432. This is a common issue during initial setup or when multiple Postgres instances are running on the same host. The failure prevents the entire Supabase stack from starting properly. | Database Problems | supabase | SupabasePostgreSQLPort BindingConfigurationStartup FailureSelf-HostedContainer CrashPublic |