You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please note that the Vagrant issue tracker is reserved for bug reports and
enhancements. For general usage questions, please use the Vagrant mailing list: https://groups.google.com/forum/#!forum/vagrant-up. Thank you!
Vagrant version
Run vagrant -v to show the version. If you are not running the latest version
of Vagrant, please upgrade before submitting an issue.
Vagrant 1.9.3
Host operating system
This is the operating system that you run locally.
OSX and ubuntu and RHE
Guest operating system
This is the operating system you run in the virtual machine.
ubuntu and RHE
Please note, if you are using Homestead or a different Vagrantfile format, we
may be unable to assist with your issue. Try to reproduce the issue using a
vanilla Vagrantfile first.
Debug output
Provide a link to a GitHub Gist containing the complete debug output: https://www.vagrantup.com/docs/other/debugging.html. The debug output should
be very long. Do NOT paste the debug output in the issue, just paste the
link to the Gist.
Expected behavior
What should have happened?
config.vm.provision "shell_early", path: "echo "pre synced_folder run shell"
would offer the ability to run a process before any custom shares are loaded, ( not the vagrant ones)
Actual behavior
What actually happened?
synced_folders are ran , then shell provisioners , then other provisioners like puppet
Steps to reproduce
Setup an shell option
it will run post synced folder mount
this can fail as details don't exist on the base box
References
Are there any other GitHub issues (open or closed) that should be linked here?
For example:
Many git hub issues exist around needing apache on the box before the synced folders set this to apache.
The workarounds that exist are , add a shell provision to undertake the remount or bake in a user to the box before you use it.
Seems to have a shell_premount would be very useful, as this can be used to also bootstrap stuff into a box before mounting shares.
...
The text was updated successfully, but these errors were encountered:
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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 2, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Please note that the Vagrant issue tracker is reserved for bug reports and
enhancements. For general usage questions, please use the Vagrant mailing list:
https://groups.google.com/forum/#!forum/vagrant-up. Thank you!
Vagrant version
Run
vagrant -v
to show the version. If you are not running the latest versionof Vagrant, please upgrade before submitting an issue.
Vagrant 1.9.3
Host operating system
This is the operating system that you run locally.
OSX and ubuntu and RHE
Guest operating system
This is the operating system you run in the virtual machine.
ubuntu and RHE
Vagrantfile
Please note, if you are using Homestead or a different Vagrantfile format, we
may be unable to assist with your issue. Try to reproduce the issue using a
vanilla Vagrantfile first.
Debug output
Provide a link to a GitHub Gist containing the complete debug output:
https://www.vagrantup.com/docs/other/debugging.html. The debug output should
be very long. Do NOT paste the debug output in the issue, just paste the
link to the Gist.
Expected behavior
What should have happened?
config.vm.provision "shell_early", path: "echo "pre synced_folder run shell"
would offer the ability to run a process before any custom shares are loaded, ( not the vagrant ones)
Actual behavior
What actually happened?
synced_folders are ran , then shell provisioners , then other provisioners like puppet
Steps to reproduce
References
Are there any other GitHub issues (open or closed) that should be linked here?
For example:
The workarounds that exist are , add a shell provision to undertake the remount or bake in a user to the box before you use it.
Seems to have a shell_premount would be very useful, as this can be used to also bootstrap stuff into a box before mounting shares.
The text was updated successfully, but these errors were encountered: