'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>
27 lines
736 B
Bash
Executable File
27 lines
736 B
Bash
Executable File
#!/bin/bash
|
|
|
|
dockerCheckIsRunningForUser()
|
|
{
|
|
local type="$1"
|
|
|
|
# Check if Docker is running for the specified user
|
|
if [[ $type == "rootless" ]]; then
|
|
local docker_command='docker ps 2>&1'
|
|
local result; result=$(dockerCommandRunInstallUser "$docker_command")
|
|
elif [[ $type == "rooted" ]]; then
|
|
local docker_command='docker ps 2>&1'
|
|
local result; result=$(eval "$docker_command")
|
|
else
|
|
echo "Invalid user type specified."
|
|
fi
|
|
|
|
# Check the result
|
|
if [[ $result =~ "Cannot connect to the Docker daemon" ]]; then
|
|
#echo "Docker is not running for the specified user."
|
|
:
|
|
else
|
|
#echo "Docker is running for the specified user."
|
|
:
|
|
fi
|
|
}
|