This repository has been archived by the owner on Mar 8, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 176
vsphere-iso requires that iso_paths datastore is the same as the VM datastore #322
Comments
@NathanDotTo Hey Nathan thanks for pointing out man 👍 , 😃 but as you said I guess I had discarded the implementation at that time because of this but I hope this helps other peeps if someone is still running with the issue. |
Please report the issue to the official Packer repository. Plugin moved there over a year ago. |
Please provide a link for where you want me to report this issue.
… On 4 Sep 2021, at 22:36, Vladislav Rassokhin ***@***.***> wrote:
Please report the issue to the official Packer repository. Plugin moved there over a year ago.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#322 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADGFXFTQO53456NKCKVDL2LUAJ7OTANCNFSM5BCGUT3A>.
Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I came across this helpful fix whilst searching for a cause for my issues.
In a similar exercise with Terraform, I am creating a VM where the VM datastore and the ISOs datastore are distinct, for the sake of tidiness if nothing else.
In the Terraform case, this separation of datastores is fine.
In the Packer case, it is not, but it should be.
This is the correct answer here, but this is also wrong. There is no reason to assume that the ISO files should be in the same datastore as the VM. It should be possible to have distinct datastores.
Originally posted by @NathanDotTo in #228 (comment)
The text was updated successfully, but these errors were encountered: