Issue

While building the published Releases updates (2.13.0 & 2.13.1) image, the inserted docker dependencies version hash for pip and setuptools in Dockerfile did not match what was being dowloaded, thus leading to error in ScanApi's DockerHub image deployment:

ERROR: failed to solve: process "/bin/sh -c python -m pip install --no-cache-dir pip==26.0.1     --hash=sha256:bdb1b08f4274833d62c1aa29e20907365a2ceb950410df15fc9521bad440122b     setuptools==82.0.1     --hash=sha256:a59e362652f08dcd477c78bb6e7bd9d80a7995bc73ce773050228a348ce2e5bb" did not complete successfully: exit code: 2`

As a temporary workaround the Docker image was uploaded manually to DockerHub without dependency hash version check during dependency packages installations. This causes the Docker image not to be in sync with GitHub (atleast in Dockerfile). This also doesn't fix the Image build problem while the Dockerfile remains with the outdated hashes and if the user builds it locally after cloning from github.

TODOs:

Optionally we need either to remove the outdated check in GitHub or preferably discuss the restablishment of DockerHub images build with dependecies hash version check.

This is a known source of image build failures when package maintainers release updates and can be solved through setting up automatic integration of ScanAPI's GitHub repo with it's DockerHub repo, and with Github actions for auto PRs (and/or pre commit hooks) using a support file requirements.txt for storing the dynamically updated dependency hashes.