Currently it seems impossible to run MkDocs from Docker.

We don't want to impose the burden of configuring a Python environment to contributors to our documentation (our community consists mainly of JavaScript and/or C++ developers), so we use use a Docker container that packages MkDocs (for Material).

Unfortunately, after enabling strict mode we are now greeted with this error

docker run --rm -it -p 8000:8000 -v ${PWD}:/docs 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.

Aborted with 1 configuration warnings in 'strict' mode!

And the container fails to start. See also squidfunk/mkdocs-material#7197 and #2108

When I use

docker run --rm -it -p 8000:8000 -v ${PWD}:/docs squidfunk/mkdocs-material serve

The server running inside the Docker container cannot be accessed from outside Docker.