33 lines
1.5 KiB
Markdown
33 lines
1.5 KiB
Markdown
---
|
|
layout: "docs"
|
|
page_title: "Debugging Packer"
|
|
description: |-
|
|
Packer strives to be stable and bug-free, but issues inevitably arise where certain things may not work entirely correctly, or may not appear to work correctly. In these cases, it is sometimes helpful to see more details about what Packer is actually doing.
|
|
---
|
|
|
|
# Debugging Packer
|
|
|
|
Packer strives to be stable and bug-free, but issues inevitably arise where
|
|
certain things may not work entirely correctly, or may not appear to work
|
|
correctly. In these cases, it is sometimes helpful to see more details about
|
|
what Packer is actually doing.
|
|
|
|
Packer has detailed logs which can be enabled by setting the `PACKER_LOG`
|
|
environmental variable to any value. This will cause detailed logs to appear
|
|
on stderr. The logs contain log messages from Packer as well as any plugins
|
|
that are being used. Log messages from plugins are prefixed by their application
|
|
name.
|
|
|
|
Note that because Packer is highly parallelized, log messages sometimes
|
|
appear out of order, especially with respect to plugins. In this case,
|
|
it is important to pay attention to the timestamp of the log messages
|
|
to determine order.
|
|
|
|
In addition to simply enabling the log, you can set `PACKER_LOG_PATH` in order
|
|
to force the log to always go to a specific file when logging is enabled.
|
|
Note that even when `PACKER_LOG_PATH` is set, `PACKER_LOG` must be set in
|
|
order for any logging to be enabled.
|
|
|
|
If you find a bug with Packer, please include the detailed log by using
|
|
a service such as [gist](http://gist.github.com).
|