> Then I am running the docker image roundup-app using:
>   docker run -it -v $PWD:/mnt roundup-app shell
> where PWD is the root of the mercurial checkout repo.
> At the shell I type:
>  cd /mnt
>  python -m pip install -r test/requirements.txt
>  python -m pytest test
> and all tests pass.
> = 1407 passed, 956 skipped, 4 xfailed, 26 subtests passed in 419.84s
(0:06:59) =

What I did in a hg clone is:
```
docker build -t roundup-local -f scripts/Docker/Dockerfile .
docker container run --rm -it -v .:/mnt roundup-local shell
cd /mnt
python -m pip install -r test/requirements.txt
python -m pytest test
```

hg diff says:
```
hg diff
diff -r ed1e6e000097 scripts/Docker/Dockerfile
--- a/scripts/Docker/Dockerfile Sat Sep 12 21:29:03 2026 +0000
+++ b/scripts/Docker/Dockerfile Thu Sep 17 10:49:01 2026 +0200
@@ -128,6 +128,7 @@
 #   modules not installed in the base library.
 # ignore warnings from pip to use virtualenv
 COPY scripts/Docker/requirements.txt .
+RUN pip install --no-cache-dir setuptools && pip install --no-cache-dir --no-build-isolation gpg
 RUN pip install --no-cache-dir -r requirements.txt
 
 # copy the elements of the release directory to the docker image
```

However I am getting the following result:
```
=========================== 18 failed, 1390 passed, 992 skipped, 4 xfailed, 3 warnings, 26 subtests passed in 615.44s (0:10:15) ============================
```

> How you are stopping the build at stage 1 so you can get a shell?
When I did that I had the original Dockerfile cut after the install requirements bit where it tried to install gpg, to debug the issue. As such I had a container like that around.

> What is the reason you are not using the stage 2 production image?
I am now. When I didn't it was just easier to get into an interactive shell that way.

> Can you paste the full errors not just the truncated summary error
messages.

See the attachment for a full output of a run.