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

"Failed to pull" error when template does not already exist on the node running packer #161

Closed
tejassharma96 opened this issue Aug 28, 2023 · 2 comments
Assignees

Comments

@tejassharma96
Copy link

Currently when we run a veertu-anka-vm-clone provisioner with just a template name but no tag, if the template is not already pulled on the node it spits out the following:

==> veertu-anka-vm-clone.anka-macos-from-source: Pulling source VM m1-macos-13.5-pm with tag latest from Anka Registry
2023/08/28 14:25:22 packer-plugin-veertu-anka_v3.2.0_x5.0_darwin_arm64 plugin: 2023/08/28 14:25:22 Executing anka --machine-readable registry pull --tag latest m1-macos-13.5-pm
==> veertu-anka-vm-clone.anka-macos-from-source: failed to pull vm m1-macos-13.5-pm with tag latest from registry (make sure to add it as the default: https://docs.veertu.com/anka/intel/command-line-reference/#registry-add)

it is trying to pull the vm with the literal tag "latest". I believe it should instead leave off the tag argument if one is not supplied, which will automatically pull the actual latest version of that template.

@NorseGaud NorseGaud self-assigned this Aug 28, 2023
@NorseGaud
Copy link
Member

Yep, looks like it's hard coded to latest. Easy fix. will work on a release ASAP

NorseGaud added a commit that referenced this issue Aug 29, 2023
NorseGaud added a commit that referenced this issue Aug 29, 2023
@NorseGaud
Copy link
Member

NorseGaud commented Aug 29, 2023

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants