Troubleshooting local rendering with Docker

If you run into problems, here are some helpful hints on how to solve them.

Remember, you can always ask questions in the #typo3-documentation channel on Slack! Register for slack and join the channel, if you have not done so already.

Problems with source < (docker run ...

source <(docker run --rm t3docs/render-documentation show-shell-commands)
dockrun_t3rd makehtml

If these commands do not work on your platform, try this instead:

mkdir -p ~/bin
docker run --rm t3docs/render-documentation show-shell-commands > ~/bin/t3docs
source ~/bin/t3docs

Sample output without errors

When you run render, you should see some output. If everything works correctly, the final output should look like this:


We saw these exitcodes (code, count):
   "0": 86
exiting with exitcode 0


Relevant is the exitcode 0. It indicates that everything executed smoothly.

Errors that break the rendering

If there are errors which break the rendering, you may see something like:

 We saw these exitcodes (code, count):
   "0": 53,
   "3": 1,
   "22": 7
exiting with exitcode 0

Do not let the message "exiting with exitcode 0" mislead you. You've definitely got a problem that needs to be taken care of.


If the rendering is not executed correctly, the files in Documentation-GENERATED-temp will still contain the last rendered results (which are now no longer up to date) !

Scroll back in your terminal to see where the errors occurred:

   exitcode: 22

   exitcode: 22

   exitcode: 22

   exitcode: 22

Everything with exitcode != 0 is relevant. Here, we see a problem with the requirements. This is usually caused by an incorrect path for including a file.

Remember, every file includes Includes.rst.txt at the top. Check your latest changes.

.. include:: /Includes.rst.txt

Correct the path, so it will point to the existing Includes.rst.txt (which should be located in the directory Documentation.


There may be problems which will not break the rendering but which should be taken care of. Warnings are listed in the file Documentation-GENERATED-temp/Result/project/0.0.0/_buildinfo/warnings.txt

Incremental Rendering

After you make changes, you can initiate rendering again.

This will cause .rst files, that has been changed, to be rendered again.

If the menu (toctree) has been changed, the menu may not be correctly displayed for unchanged files because they will not be rendered again.

If you need a complete rendering, delete the Documentation-GENERATED-temp folder and render again, for example:

rm -rf Documentation-GENERATED-temp

Get detailed information

If you create a directory tmp-GENERATED-temp before you start the rendering, the toolchain will not remove this directory when it is done. Usually it cleans up after itself and this directory will be created and then removed.

The directory contains some additional information for the individual scripts that have been run. In case of cryptic error messages which you have trouble interpreting, you may check these files for more information.

Look for files with ending err.txt that are not empty.

Example output:


Traceback (most recent call last):
  File "/usr/local/lib/python2.7/site-packages/sphinx/", line 303, in main
    args.warningiserror, args.tags, args.verbosity,
  File "/usr/local/lib/python2.7/site-packages/sphinx/", line 191, in __init__
  File "/usr/local/lib/python2.7/site-packages/sphinx/", line 411, in setup_extension
    self.registry.load_extension(self, extname)
  File "/usr/local/lib/python2.7/site-packages/sphinx/", line 318, in load_extension
    raise ExtensionError(__('Could not import extension %s') % extname, err)
ExtensionError: Could not import extension sphinxcontrib.googlechart (exception: cannot import name Directive)

Extension error:
Could not import extension sphinxcontrib.googlechart (exception: cannot import name Directive)