-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Packer failed to run target: googlecloud #13069
Comments
Hi @yaronkaikov thanks for reaching out. I'll pull down the latest Packer Docker full image, which contains all the plugins installed to ensure we can build properly. I'm not sure what is packager, are you using the Packer Docker images we release or is this a custom container? I would check that the user running Packer has access to the plugin directory To help me better understand what might be happening here could you set the PACKER_LOG=1 environment variable when executing the container to capture the plugin loading output. The logs will provide information on what plugins have been discovered, loaded, and registered with Packer.
|
here is the output running from our image (it seems ok)
Running those commands indeed show some errors (although it also in AWS which we manage to build):
I will work on it to see if i can get it working. |
@nywilken Sorry the reason for those errors is that we are using parameters and when I was running it I didn't provide them. once i provide them i get
|
@yaronkaikov no worries, thank you for the quick follow-up. I'm glad you were able to get this squared away. I appreciate you opening an issue to start. Packer 1.11.0 changed how Packer works with plugins so it is great to know if folks run into any issues. Keep building and don't hesitate to reach out if you run into any issue that seems like a bug. I'm going to close this issue. But if anything should change drop me a comment and I will gladly reopen it. |
@nywilken I meant that the configuration is valid, but the failure remains the same :-( |
@nywilken some more information i got from the log
Why is it looking under |
Oh, i am passing this with my container, i will check it then , and update |
Hi @yaronkaikov apologies I thought it was resolved since the configuration validated properly. The plugins are loaded during validate hence why I thought it was resolved. But it looks like you figure it out now. Please let me know if you need more help and if I should reopen this issue. |
@nywilken Just a quick update, managed to solve it by adding |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
When filing a bug, please include the following headings if possible. Any
example text in this template can be deleted.
Overview of the Issue
Trying to build a custom
googlecompute
target after upgrading packager fromv1.9.4-1
tov1.11.0-1
and it failed with the following error:We are using a docker image to run
packer
and we have all plugins installedReproduction Steps
Steps to reproduce this issue
Packer version
Packer v1.11.0
Simplified Packer Template
Operating system and Environment details
OS, Architecture, and any other information you can provide about the
environment.
Log Fragments and crash.log files
Include appropriate log fragments. If the log is longer than a few dozen lines,
please include the URL to the gist of the log or
use the Github detailed format instead of posting it directly in the issue.
Set the env var
PACKER_LOG=1
for maximum log detail.The text was updated successfully, but these errors were encountered: