From e6e9c5abcd9dc91db716f918398af788cf4465ee Mon Sep 17 00:00:00 2001 From: TheSpad Date: Tue, 6 Feb 2024 21:49:24 +0000 Subject: [PATCH] Fix stupid error handling logic issues --- docker-mods.v3 | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/docker-mods.v3 b/docker-mods.v3 index a7c6a51..71df4f6 100755 --- a/docker-mods.v3 +++ b/docker-mods.v3 @@ -343,15 +343,18 @@ run_mods() { "registry-1.docker.io") AUTH_URL="https://auth.docker.io/token?service=registry.docker.io&scope=repository:${ENDPOINT}:pull";; *) AUTH_URL=$(get_auth_url "${MANIFEST_URL}" "${TAG}") esac - if [[ -z "${AUTH_URL}" ]]; then write_mod_error "Could not fetch auth URL from registry, skipping mod";fi + if [[ -z "${AUTH_URL}" ]]; then + write_mod_error "Could not fetch auth URL from registry for ${DOCKER_MOD}, skipping mod" + continue + fi # Kill off modification logic if any of the usernames are banned for BANNED in $(curl -s https://raw.githubusercontent.com/linuxserver/docker-mods/master/blacklist.txt); do if [[ "${BANNED,,}" == "${USERNAME,,}" ]]; then if [[ -z ${RUN_BANNED_MODS+x} ]]; then - write_mod_info "${DOCKER_MOD} is banned from use due to reported abuse aborting mod logic" - return + write_mod_info "${DOCKER_MOD} is banned from use due to reported abuse, skipping mod" + continue else - write_mod_info "You have chosen to run banned mods ${DOCKER_MOD} will be applied" + write_mod_info "You have chosen to run banned mods, ${DOCKER_MOD} will be applied" fi fi done