Revise tests. Use docker-compose.yml where possible

test/docker_tests/configurations/mount-tests/docker-compose.mount-test.active_config_mounted.yml

@@ -1,3 +1,7 @@
+# Expected outcome: Container starts successfully with proper nginx config mount
+# - SYSTEM_SERVICES_ACTIVE_CONFIG shows as writable and mounted
+# - No configuration warnings for nginx config path
+# - Custom PORT configuration should work when nginx config is writable
 services:
   netalertx:
     network_mode: host

test/docker_tests/configurations/mount-tests/docker-compose.mount-test.active_config_no-mount.yml

@@ -1,3 +1,7 @@
+# Expected outcome: Container shows warning about missing nginx config mount
+# - SYSTEM_SERVICES_ACTIVE_CONFIG shows as not mounted
+# - Warning message about nginx configuration mount being missing
+# - Custom PORT configuration may not work properly
 services:
   netalertx:
     network_mode: host

test/docker_tests/configurations/mount-tests/docker-compose.mount-test.active_config_ramdisk.yml

@@ -1,3 +1,7 @@
+# Expected outcome: Container shows performance warning for nginx config on RAM disk
+# - SYSTEM_SERVICES_ACTIVE_CONFIG shows as mounted on tmpfs (RAM disk)
+# - Performance issue warning since nginx config should be persistent
+# - Custom PORT configuration may have performance implications
 services:
   netalertx:
     network_mode: host

test/docker_tests/configurations/mount-tests/docker-compose.mount-test.active_config_unwritable.yml

@@ -1,3 +1,7 @@
+# Expected outcome: Container fails to start due to unwritable nginx config partition
+# - SYSTEM_SERVICES_ACTIVE_CONFIG shows as mounted but unwritable (❌ in Writeable column)
+# - 35-nginx-config.sh detects permission error and exits with code 1
+# - Container startup fails because nginx configuration cannot be written for custom ports
 services:
   netalertx:
     network_mode: host

test/docker_tests/configurations/mount-tests/docker-compose.mount-test.api_mounted.yml

@@ -1,3 +1,7 @@
+# Expected outcome: Container starts successfully with proper API mount
+# - NETALERTX_API shows as writable and mounted
+# - No configuration warnings for API path
+# - API data persistence works correctly
 services:
   netalertx:
     network_mode: host

test/docker_tests/configurations/mount-tests/docker-compose.mount-test.api_no-mount.yml

@@ -1,3 +1,7 @@
+# Expected outcome: Container shows mount error for API directory
+# - NETALERTX_API shows as not mounted
+# - Mount error since API directory should be mounted for proper operation
+# - API functionality may be limited
 services:
   netalertx:
     network_mode: host

test/docker_tests/configurations/mount-tests/docker-compose.mount-test.api_ramdisk.yml

@@ -1,3 +1,7 @@
+# Expected outcome: Container shows performance warning for API on RAM disk
+# - NETALERTX_API shows as mounted on tmpfs (RAM disk)
+# - Performance issue warning since API data should be on persistent storage
+# - API data will be lost on container restart
 services:
   netalertx:
     network_mode: host

test/docker_tests/configurations/mount-tests/docker-compose.mount-test.api_unwritable.yml

@@ -1,3 +1,7 @@
+# Expected outcome: Container fails to start due to unwritable API partition
+# - NETALERTX_API shows as mounted but unwritable (❌ in Writeable column)
+# - API directory must be writable for proper operation
+# - Container startup fails because API functionality cannot work without write access
 services:
   netalertx:
     network_mode: host

test/docker_tests/configurations/mount-tests/docker-compose.mount-test.config_mounted.yml

@@ -1,3 +1,7 @@
+# Expected outcome: Container starts successfully with proper config mount
+# - NETALERTX_CONFIG shows as writable and mounted
+# - No configuration warnings for config path
+# - Configuration persistence works correctly
 services:
   netalertx:
     network_mode: host

test/docker_tests/configurations/mount-tests/docker-compose.mount-test.config_no-mount.yml

@@ -1,3 +1,7 @@
+# Expected outcome: Container shows mount error for config directory
+# - NETALERTX_CONFIG shows as not mounted
+# - Mount error since config directory should be mounted for proper operation
+# - Configuration may not persist across restarts
 services:
   netalertx:
     network_mode: host

test/docker_tests/configurations/mount-tests/docker-compose.mount-test.config_ramdisk.yml

@@ -1,3 +1,7 @@
+# Expected outcome: Container shows dataloss risk warning for config on RAM disk
+# - NETALERTX_CONFIG shows as mounted on tmpfs (RAM disk)
+# - Dataloss risk warning since config data should be persistent
+# - Configuration will be lost on container restart
 services:
   netalertx:
     network_mode: host

test/docker_tests/configurations/mount-tests/docker-compose.mount-test.config_unwritable.yml

@@ -1,3 +1,7 @@
+# Expected outcome: Container fails to start due to unwritable config partition
+# - NETALERTX_CONFIG shows as mounted but unwritable (❌ in Writeable column)
+# - 30-writable-config.sh detects permission error and exits with code 1
+# - Container startup fails because config files cannot be written to
 services:
   netalertx:
     network_mode: host

test/docker_tests/configurations/mount-tests/docker-compose.mount-test.db_mounted.yml

@@ -1,3 +1,7 @@
+# Expected outcome: Container starts successfully with proper database mount
+# - NETALERTX_DB shows as writable and mounted
+# - No configuration warnings for database path
+# - Database persistence works correctly
 services:
   netalertx:
     network_mode: host

test/docker_tests/configurations/mount-tests/docker-compose.mount-test.db_no-mount.yml

@@ -1,3 +1,7 @@
+# Expected outcome: Container shows mount error warning but continues running
+# - NETALERTX_DB shows as not mounted (❌ in Mount column) but path gets created
+# - Warning message displayed about configuration issues
+# - Container continues because database directory can be created in writable filesystem
 services:
   netalertx:
     network_mode: host

test/docker_tests/configurations/mount-tests/docker-compose.mount-test.db_ramdisk.yml

@@ -1,3 +1,7 @@
+# Expected outcome: Container shows dataloss risk warning for database on RAM disk
+# - NETALERTX_DB shows as mounted on tmpfs (RAM disk)
+# - Dataloss risk warning since database should be persistent
+# - Database will be lost on container restart
 services:
   netalertx:
     network_mode: host

test/docker_tests/configurations/mount-tests/docker-compose.mount-test.db_unwritable.yml

@@ -1,3 +1,7 @@
+# Expected outcome: Container fails to start due to unwritable database partition
+# - NETALERTX_DB shows as mounted but unwritable (❌ in Writeable column)
+# - 30-writable-config.sh detects permission error and exits with code 1
+# - Container startup fails because database files cannot be written to
 services:
   netalertx:
     network_mode: host

test/docker_tests/configurations/mount-tests/docker-compose.mount-test.log_mounted.yml

@@ -1,3 +1,7 @@
+# Expected outcome: Container starts successfully with proper log mount
+# - NETALERTX_LOG shows as mounted and writable
+# - No mount warnings since logs can be non-persistent
+# - Container starts normally with logging enabled
 services:
   netalertx:
     network_mode: host

test/docker_tests/configurations/mount-tests/docker-compose.mount-test.log_no-mount.yml

@@ -1,3 +1,7 @@
+# Expected outcome: Container shows mount error warning but continues running
+# - NETALERTX_LOG shows as not mounted (❌ in Mount column)
+# - Warning message displayed about configuration issues
+# - Container continues to run despite the mount error
 services:
   netalertx:
     network_mode: host

test/docker_tests/configurations/mount-tests/docker-compose.mount-test.log_ramdisk.yml

@@ -1,3 +1,7 @@
+# Expected outcome: Container shows dataloss risk warning for logs on RAM disk
+# - NETALERTX_LOG shows as mounted on tmpfs (RAM disk)
+# - Dataloss risk warning since logs may be lost on restart
+# - Container starts but logs may not persist
 services:
   netalertx:
     network_mode: host

test/docker_tests/configurations/mount-tests/docker-compose.mount-test.log_unwritable.yml

@@ -1,3 +1,7 @@
+# Expected outcome: Container fails to start due to unwritable log partition
+# - NETALERTX_LOG shows as mounted but unwritable (❌ in Writeable column)
+# - 25-mandatory-folders.sh cannot create required log files and fails
+# - Container startup fails because logging infrastructure cannot be initialized
 services:
   netalertx:
     network_mode: host

test/docker_tests/configurations/mount-tests/docker-compose.mount-test.run_mounted.yml

@@ -1,3 +1,7 @@
+# Expected outcome: Container starts successfully with proper run mount
+# - NETALERTX_RUN shows as mounted and writable
+# - No mount warnings since run directory can be non-persistent
+# - Container starts normally with runtime files enabled
 services:
   netalertx:
     network_mode: host

test/docker_tests/configurations/mount-tests/docker-compose.mount-test.run_no-mount.yml

@@ -1,3 +1,7 @@
+# Expected outcome: Container shows mount error warning but continues running
+# - NETALERTX_RUN shows as not mounted (❌ in Mount column)
+# - Warning message displayed about configuration issues
+# - Container continues to run despite the mount error
 services:
   netalertx:
     network_mode: host

test/docker_tests/configurations/mount-tests/docker-compose.mount-test.run_ramdisk.yml

@@ -1,3 +1,7 @@
+# Expected outcome: Container shows dataloss risk warning for run on RAM disk
+# - NETALERTX_RUN shows as mounted on tmpfs (RAM disk)
+# - Dataloss risk warning since runtime files may be lost on restart
+# - Container starts but runtime state may not persist
 services:
   netalertx:
     network_mode: host

test/docker_tests/configurations/mount-tests/docker-compose.mount-test.run_unwritable.yml

@@ -1,3 +1,7 @@
+# Expected outcome: Container fails to start due to unwritable run partition
+# - NETALERTX_RUN shows as mounted but unwritable (❌ in Writeable column)
+# - 25-mandatory-folders.sh cannot create required runtime files and fails
+# - Container startup fails because runtime infrastructure cannot be initialized
 services:
   netalertx:
     network_mode: host