Changing image-files for web-warden results in Error when building

Hello all,
I´m trying to build web-warden on my own, since I´m loking for customisation by changing images and so on..
After altering the images in bw_web_builds/resources/src/images even by changing one number/line in some of the .svg images, I´m getting the following output when compiling with make container as well as make container-extract:
ERROR: failed to solve: process "/bin/sh -c ./scripts/build_web_vault.sh" did not complete successfully: exit code: 1 make: *** [Makefile:63: container] Error 1

I tried everything. Can anyone of you may help?
Any output or debug from the container would be helpful.
When information is missing, let me know.

Greets,
BadCoder

Edit:
Some more output from my console

docker build -t bw_web_vault .
[+] Building 275.0s (17/22)                                                                      docker:default
 => [internal] load build definition from Dockerfile                                                       0.0s
 => => transferring dockerfile: 2.26kB                                                                     0.0s
 => resolve image config for docker-image://docker.io/docker/dockerfile:1                                  1.3s
 => CACHED docker-image://docker.io/docker/dockerfile:1@sha256:4c68376a702446fc3c79af22de146a148bc3367e73  0.0s
 => [internal] load metadata for docker.io/library/node:20-bookworm                                        0.7s
 => [internal] load .dockerignore                                                                          0.0s
 => => transferring context: 306B                                                                          0.0s
 => [internal] load build context                                                                          0.0s
 => => transferring context: 8.54kB                                                                        0.0s
 => [build  1/14] FROM docker.io/library/node:20-bookworm@sha256:735b1ba7e4550c415f98568efbf527e3f75828ac  0.0s
 => CACHED [build  2/14] RUN node --version && npm --version                                               0.0s
 => CACHED [build  3/14] RUN mkdir /bw_web_builds                                                          0.0s
 => CACHED [build  4/14] WORKDIR /bw_web_builds                                                            0.0s
 => CACHED [build  5/14] COPY patches ./patches                                                            0.0s
 => [build  6/14] COPY resources ./resources                                                               0.1s
 => [build  7/14] COPY scripts ./scripts                                                                   0.1s
 => [build  8/14] COPY .build_env* ./                                                                      0.1s
 => [build  9/14] RUN ./scripts/checkout_web_vault.sh                                                      4.4s
 => [build 10/14] RUN ./scripts/patch_web_vault.sh                                                         0.6s
 => ERROR [build 11/14] RUN ./scripts/build_web_vault.sh                                                 267.3s
------
 > [build 11/14] RUN ./scripts/build_web_vault.sh:
0.672 v20.19.0
0.829 10.8.2
0.833 /bw_web_builds/bw_clients /bw_web_builds
3.078 npm warn skipping integrity check for git dependency ssh://git@github.com/electron/node-gyp.git
10.80 npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
12.33 npm warn deprecated domexception@4.0.0: Use your platform's native DOMException instead
12.51 npm warn deprecated popper.js@1.16.1: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1
13.01 npm warn deprecated critters@0.0.24: Ownership of Critters has moved to the Nuxt team, who will be maintaining the project going forward. If you'd like to keep using Critters, please switch to the actively-maintained fork at https://github.com/danielroe/beasties
13.38 npm warn deprecated boolean@3.2.0: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
13.87 npm warn deprecated abab@2.0.6: Use your platform's native atob() and btoa() methods instead
16.20 npm warn deprecated @npmcli/move-file@2.0.1: This functionality has been moved to @npmcli/fs
17.15 npm warn deprecated @humanwhocodes/config-array@0.11.14: Use @eslint/config-array instead
17.15 npm warn deprecated @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
18.37 npm warn deprecated @babel/plugin-proposal-export-namespace-from@7.18.9: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-export-namespace-from instead.
19.94 npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
21.06 npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
21.48 npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
22.15 npm warn deprecated rimraf@2.7.1: Rimraf versions prior to v4 are no longer supported
22.15 npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
23.27 npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
23.56 npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
23.97 npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
24.00 npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
24.73 npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
24.80 npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
24.80 npm warn deprecated glob@8.1.0: Glob versions prior to v9 are no longer supported
24.98 npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
25.62 npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
25.62 npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
25.76 npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
26.23 npm warn deprecated glob@8.1.0: Glob versions prior to v9 are no longer supported
26.31 npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
28.28 npm warn deprecated eslint@8.57.0: This version is no longer supported. Please see https://eslint.org/version-support for other options.
33.61 npm warn deprecated vis@4.21.0: Please consider using https://github.com/visjs
49.88
49.88 > @bitwarden/clients@0.0.0 postinstall
49.88 > patch-package
49.88
49.99 patch-package 8.0.0
49.99 Applying patches...
50.00 argon2-browser@1.18.0 ✔
50.00
50.00 > @bitwarden/clients@0.0.0 prepare
50.00 > husky
50.00
50.07
50.07 added 2366 packages, and audited 2385 packages in 49s
50.07
50.07 438 packages are looking for funding
50.07   run `npm fund` for details
50.13
50.13 14 vulnerabilities (11 moderate, 2 high, 1 critical)
50.13
50.13 To address issues that do not require attention, run:
50.13   npm audit fix
50.13
50.13 To address all issues (including breaking changes), run:
50.13   npm audit fix --force
50.13
50.13 Run `npm audit` for details.
50.13 npm notice
50.13 npm notice New major version of npm available! 10.8.2 -> 11.2.0
50.13 npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.2.0
50.13 npm notice To update run: npm install -g npm@11.2.0
50.13 npm notice
50.15 /bw_web_builds/bw_clients/apps/web /bw_web_builds/bw_clients /bw_web_builds
50.31
50.31 > @bitwarden/web-vault@2025.1.1 dist:oss:selfhost
50.31 > npm run build:oss:selfhost:prod
50.31
50.45
50.45 > @bitwarden/web-vault@2025.1.1 build:oss:selfhost:prod
50.45 > cross-env ENV=selfhosted NODE_ENV=production npm run build:oss
50.45
50.62
50.62 > @bitwarden/web-vault@2025.1.1 build:oss
50.62 > cross-env NODE_OPTIONS="--max-old-space-size=8192" webpack
50.62
50.97 ==================================================
50.97 envConfig
50.97 {
50.97   "urls": {},
50.97   "dev": {
50.97     "port": 8081,
50.97     "allowedHosts": "auto",
50.97     "proxyApi": "http://localhost:4001",
50.97     "proxyIdentity": "http://localhost:33657",
50.97     "proxyEvents": "http://localhost:46274",
50.97     "proxyNotifications": "http://localhost:61841"
50.97   },
50.97   "flags": {
50.97     "sdk": true
50.97   },
50.97   "devFlags": {}
50.97 }
50.97 ==================================================
91.81 [BABEL] Note: The code generator has deoptimised the styling of /bw_web_builds/bw_clients/node_modules/@angular/core/fesm2022/core.mjs as it exceeds the max of 500KB.
130.1 [BABEL] Note: The code generator has deoptimised the styling of /bw_web_builds/bw_clients/node_modules/@bitwarden/sdk-internal/bitwarden_wasm_internal_bg.wasm.js as it exceeds the max of 500KB.
159.3 [BABEL] Note: The code generator has deoptimised the styling of /bw_web_builds/bw_clients/node_modules/zxcvbn/lib/frequency_lists.js as it exceeds the max of 500KB.
266.4 npm error Lifecycle script `build:oss` failed with error:
266.4 npm error code 1
266.4 npm error path /bw_web_builds/bw_clients/apps/web
266.4 npm error workspace @bitwarden/web-vault@2025.1.1
266.4 npm error location /bw_web_builds/bw_clients/apps/web
266.4 npm error command failed
266.4 npm error command sh -c cross-env NODE_OPTIONS="--max-old-space-size=8192" webpack
266.8 npm error Lifecycle script `build:oss:selfhost:prod` failed with error:
266.8 npm error code 1
266.8 npm error path /bw_web_builds/bw_clients/apps/web
266.8 npm error workspace @bitwarden/web-vault@2025.1.1
266.8 npm error location /bw_web_builds/bw_clients/apps/web
266.8 npm error command failed
266.8 npm error command sh -c cross-env ENV=selfhosted NODE_ENV=production npm run build:oss
267.0 npm error Lifecycle script `dist:oss:selfhost` failed with error:
267.0 npm error code 1
267.0 npm error path /bw_web_builds/bw_clients/apps/web
267.0 npm error workspace @bitwarden/web-vault@2025.1.1
267.0 npm error location /bw_web_builds/bw_clients/apps/web
267.0 npm error command failed
267.1 npm error command sh -c npm run build:oss:selfhost:prod
------
Dockerfile:43
--------------------
  41 |     RUN ./scripts/checkout_web_vault.sh
  42 |     RUN ./scripts/patch_web_vault.sh
  43 | >>> RUN ./scripts/build_web_vault.sh
  44 |     RUN mv "${VAULT_FOLDER}/apps/web/build" ./web-vault
  45 |
--------------------
ERROR: failed to solve: process "/bin/sh -c ./scripts/build_web_vault.sh" did not complete successfully: exit code: 1
make: *** [Makefile:63: container] Error 1