'local result=$(cmd)' resets $? to 0 (the local builtin's own exit), so the
following checkSuccess always saw success regardless of cmd's real exit — the
mechanism that masked the de-sudo write failures. Split declaration from
assignment ('local result; result=$(cmd)') across all 235 active-code sites
(84 files) so the command's exit reaches checkSuccess. No behaviour change
beyond $? now being accurate (no set -e in runtime code; multi-line
assignments transform safely).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Signed-off-by: librelad <librelad@digitalangels.vip>
17 lines
462 B
Bash
Executable File
17 lines
462 B
Bash
Executable File
#!/bin/bash
|
|
|
|
dockerStartApp()
|
|
{
|
|
local app_name="$1"
|
|
|
|
if [[ -z "$app_name" ]]; then
|
|
isNotice "No app name provided. Unable to start containers."
|
|
fi
|
|
|
|
isNotice "Starting Docker containers for '$app_name'. Please wait..."
|
|
|
|
# Start containers in one go
|
|
local result; result=$(dockerCommandRun "docker ps -aqf name=$app_name | xargs -r docker start" >/dev/null 2>&1)
|
|
checkSuccess "Started Docker containers matching '$app_name'"
|
|
}
|