Post-processor compression results in crash
- Dominant language
- Go
- Stars
- 15.8k
- Forks
- 3.3k
- PR merge metrics
- PR metrics pending
Description
#### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
When filing a bug, please include the following headings if possible. Any
example text in this template can be deleted.
#### Overview of the Issue
When using a post-processor to compress the final output image, packer crashes. This issue has cropped up only recently in the past few months on projects that built successfully before.
#### Reproduction Steps
Use a post-processor that compresses to a .gz file:
```
"post-processors": [
[
{
"compression_level": 6,
"format": ".gz",
"keep_input_artifact": true,
"output": "build/artifact.raw.gz",
"type": "compress"
}
]
],
```
an example of a project that has this issue: https://github.com/Logicwax/airgap
### Packer version
From ` 1.6.6 [go1.18.1 linux amd64]`
### Operating system and Environment details
Ubuntu 22.04, kernel 5.19.0-38-generic, intel i7.
### Log Fragments and crash.log files
https://gist.github.com/Logicwax/d36c764df5f356dc3b83572e9bd0c261
Contributor guide
Research direction
Start by reproducing the crash with the supplied compress post-processor configuration on Packer 1.6.6 and inspect the linked crash log and example project. Trace the post-processor compression entry point and verify that producing the .gz artifact completes without a crash, including the keep_input_artifact case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100