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

Enhancement Request: Configure Temp-Doirectory for Cloud-Init ISO #13519

Open
Zahtu opened this issue Oct 28, 2024 · 0 comments
Open

Enhancement Request: Configure Temp-Doirectory for Cloud-Init ISO #13519

Zahtu opened this issue Oct 28, 2024 · 0 comments

Comments

@Zahtu
Copy link

Zahtu commented Oct 28, 2024

Is your feature request related to a problem? Please describe.
Using Vagrant in a WSL - VirtualBox Setup throws errors in provisioning the machine when using the cloud-init feature,
as the host machine (where virtualbox is installed) can not find the compiled cloud-image iso, which is positioned in the local tmp-directory (wsl /tmp/)

Describe the solution you'd like
Having an Option to configure the temporary Directory where the cloud-init iso is compiled to would give anyone the flexibility to set up a path, whicht is usable by the provisioner.
From my point of View, this option should influence https://github.com/hashicorp/vagrant/blob/main/lib/vagrant/action/builtin/cloud_init_setup.rb#L95 Dir.mktmpdir second argument tmpdir can be configured to setup the iso in the requested path.

Additional context
Using vagrant in a WSL-Setup with the provider located on the host-machine results in an error, when using cloud-init action from vagrant:
grafik

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

1 participant