Running "mkdocs serve" through Docker results in "Connection reset by peer" #7197

$ docker run --rm -v .:/docs -p 8000:8000 squidfunk/mkdocs-material serve
INFO    -  Building documentation...
INFO    -  Cleaning site directory
INFO    -  Documentation built in 0.11 seconds
INFO    -  [12:44:48] Watching paths for changes: 'docs', 'mkdocs.yml'
INFO    -  [12:44:48] Serving on http://127.0.0.1:8000/
a subsequent curl does not work:
$ curl http://localhost:8000
curl: (56) Recv failure: Connection reset by peer
When i run it without the serve argument:
$ docker run --rm -v .:/docs -p 8000:8000 squidfunk/mkdocs-material
WARNING -  Config value 'dev_addr': The use of the IP address '0.0.0.0' suggests a production environment or the use of a proxy to connect to the MkDocs server. However, the MkDocs' server is intended for local development purposes only. Please use a third party production-ready server instead.
INFO    -  Building documentation...
INFO    -  Cleaning site directory
INFO    -  Documentation built in 0.11 seconds
INFO    -  [12:45:47] Watching paths for changes: 'docs', 'mkdocs.yml'
INFO    -  [12:45:47] Serving on http://0.0.0.0:8000/
everything is fine.
Please note the different IP address. It fails, when it binds to 127.0.0.1, but works, when it binds to 0.0.0.0:
$ docker run --rm -v .:/docs -p 8000:8000 squidfunk/mkdocs-material serve -a 0.0.0.0:8000
behaves exactly as leaving out the "serve" argument.
Related links
Reporting a bug
Issue search for "docker connection"
Reproduction
I have no idea what to put here, as this is an issue running through Docker, which happens with every project.

empty.zip
Steps to reproduce
Browser
No response
Before submitting
 I have read and followed the bug reporting guidelines.
 I have attached links to the documentation, and possibly related issues and discussions.
 I assure that I have removed all customizations before submitting this bug report.
 I have attached a .zip file with a minimal reproduction using the built-in info plugin.