MkDocs 1.1.1 breaks development server in Docker image
See original GitHub issueDescription
When I try to run my Dockerfile to serve the mkdocs site locally, I get an error about the dev-addr
Expected behavior
I expect the mkdocs site to successfully load locally at http://0.0.0.0:8000/
Actual behavior
mkdocs gives this error:
INFO - Building documentation...
ERROR - Config value: 'dev_addr'. Error: The MkDocs' server is intended for development purposes only. Therefore, '0.0.0.0' is not a supported IP address. Please use a third party production-ready server instead.
Aborted with 1 Configuration Errors!
Steps to reproduce the bug
docker run --it -p 8000:8000 image-id
Package versions
- Python:
python 3.6
- MkDocs:
latest version on github
(I clone the mkdocs-material in my Dockerfile)
Project configuration
# Project information
site_name: Site Name
site_description: Site Description
site_author: Author
site_url: ""
# Repository
repo_name: test/test
repo_url: https://github.com/test/test
edit_uri: ""
# Copyright
copyright: "Copyright"
# Configuration
theme:
name: null
custom_dir: material
# 404 page
static_templates:
- 404.html
# Don't include MkDocs' JavaScript
include_search_page: false
search_index_only: true
# Default values, taken from mkdocs_theme.yml
language: en
features:
- tabs
- instant
palette:
primary: blue
accent: blue
font:
text: Roboto
code: Roboto Mono
icon:
logo: logo
favicon: assets/images/favicon.png
# Customization
extra:
social:
- icon: logo
link: https://www.test.com/
# Extensions
markdown_extensions:
- markdown.extensions.admonition
- markdown.extensions.attr_list
- markdown.extensions.codehilite:
guess_lang: false
- markdown.extensions.def_list
- markdown.extensions.footnotes
- markdown.extensions.meta
- markdown.extensions.toc:
permalink: true
- pymdownx.arithmatex
- pymdownx.betterem:
smart_enable: all
- pymdownx.caret
- pymdownx.critic
- pymdownx.details
- pymdownx.emoji:
emoji_index: !!python/name:materialx.emoji.twemoji
emoji_generator: !!python/name:materialx.emoji.to_svg
# - pymdownx.highlight:
# linenums_style: pymdownx-inline
- pymdownx.inlinehilite
- pymdownx.keys
- pymdownx.magiclink:
repo_url_shorthand: true
user: squidfunk
repo: mkdocs-material
- pymdownx.mark
- pymdownx.smartsymbols
- pymdownx.snippets:
check_paths: true
- pymdownx.superfences
- pymdownx.tabbed
- pymdownx.tasklist:
custom_checkbox: true
- pymdownx.tilde
#yamllint disable rule:line-length
nav:
- Introduction:
- test: test.md
System information
- OS: Mac
- Browser: Google Chrome
Issue Analytics
- State:
- Created 3 years ago
- Comments:17 (10 by maintainers)
Top Results From Across the Web
Release Notes - MkDocs
To not make a breaking change, there's no change to how this property is used, but now you should: Use File.src_uri instead of...
Read more >How To Install MkDocs on Linux Server and Docker - LetsCloud
In the folder where the Dockerfile resides, run the command below to build the image: You can replace *letscloud* with your own preferred...
Read more >Material for MkDocs - GitHub
The official Docker image is a great way to get up and running in a few ... In order to start development on...
Read more >Read the Docs Documentation
The Docker image used for building the docs. Image names refer to the operating system Read the Docs uses to build.
Read more >Release Notes - 咕的gitbook
mkdocs serve now uses a new underlying server + file watcher ... from the mkdocs theme, the theme developer may need to update...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
We’re running in strict mode, meaning it’s an error. May want to call out that it’s no longer possible to use the flag in the latest version.
On Fri, Jun 26, 2020, 9:42 AM Martin Donath notifications@github.com wrote:
@squidfunk Just want to say thanks so much for your advocacy on the mkdocs issue thread. It was nice to see a rational and compassionate approach. Looking forward to finding a solution as we also run in strict mode.