Skip to content
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

MacOS will stop the plugins install command with showing "packer-plugin-qemu_v1.1.1_x5.0_darwin_arm64" can’t be opened because Apple cannot check it for malicious software. #190

Open
burxtx opened this issue Feb 15, 2025 · 0 comments
Labels

Comments

@burxtx
Copy link

burxtx commented Feb 15, 2025

When filing a bug, please include the following headings if possible. Any
example text in this template can be deleted.

Overview of the Issue

I was manually installing the qemu plugin from local file, on M1 Mac Ventura,

./packer plugins install --path ../packer-plugin-qemu_v1.1.1_x5.0_darwin_arm64/packer-plugin-qemu_v1.1.1_x5.0_darwin_arm64 github.com/hashicorp/qemu

then MacOS will stop the plugins install command with showing:
"packer-plugin-qemu_v1.1.1_x5.0_darwin_arm64" can’t be opened because Apple cannot check it for malicious software. This software needs to be updated. Contact the developer for more information.

Reproduction Steps

Steps to reproduce this issue

Plugin and Packer version

From packer version 1.12.0 darwin arm64, qemu plugin version v1.1.1_x5.0_darwin_arm64

Simplified Packer Buildfile

If the file 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.

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.

@burxtx burxtx added the bug label Feb 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant