By any chance is this happening inside a script where docker compose down is immediately followed by docker compose up -d? If it’s the case this might help: https://forums.docker.com/t/error-starting-userland-proxy-listen-tcp4-0-0-0-0-bind-address-already-in-use/140275/14
You could check the docker compose github project, and see whether such an issue is already registered, or create one: