RUN command no longer working after upgrade to version Docker version 24.0.6, build ed223bc

Hi,

I have been using docker for several years in a project with multiple images, but today I am facing a problem that block everything. Whatever I try, any RUN command, on different containers fails with the same error, whatever the RUN is executing.

I have the following Dockerfile

FROM python:3.8.18-bookworm
ENV PYTHONUNBUFFERED=1
ADD ./root /
ADD . /srv/
RUN ["/bin/bash", "-c", "setup.sh"]
EXPOSE 80
ENTRYPOINT ["container-entrypoint"]

the contents of the setup file are:

#!/bin/bash

ls

setup.sh is made available in the ADD line I have ./root/usr/bin/setup.sh

Whatever I try, any RUN command, on differnt containers fails with the same error:

 => ERROR [6/6] RUN ["/bin/bash", "-c", "setup.sh"]                                                                                                                                                                         0.0s
------
 > [6/6] RUN ["/bin/bash", "-c", "setup.sh"]:
------
Dockerfile:7
--------------------
   5 |     ADD ./root/usr/bin/setup.sh /usr/bin/setup.sh
   6 |     ADD . /srv/
   7 | >>> RUN ["/bin/bash", "-c", "setup.sh"]
   8 |     EXPOSE 80
   9 |     ENTRYPOINT ["container-entrypoint"]
--------------------
ERROR: failed to solve: process "/bin/bash -c setup.sh" did not complete successfully: failed to create endpoint ly7oblb0h607n72ma65uct6ek on network bridge: network c335481dc4e95101fc70bd05f985eab3e9a844e35fa75abe40f0088ce4f359ed does not exist

I have tried with centos7, ubuntu and other images, all fail on RUN.
Removing the RUN allows the image to be build without any issues.

The RUN issues still remains.

I can reinstall it 2, 3 times per day and then it stops.
But after a build fails due to some error, somewhere, the RUN error comes back.

I can’t reinstall 2, 3 per day, that is unworkable.

I am on ubuntu20, plenty of diskspace, plenty of build, the error that comes back all the time is:

did not complete successfully: failed to create endpoint ####hash#### on network bridge: network ###hash#### does not exist

Any have an idea what this might be?