Комментарии:
Geil, darauf habe ich gewartet. Danke dafür. :)
Tolles Video und wie immer eine tolle Erklärung.
Weiter so!
lols i digg the 'itprofessional' chilling up there
ОтветитьHi
Which keybord you are using?
Christian, I have watched your Vagrant and Ansible separate videos, and I have watched this one. What is Kitchen? How does it fit into Vagrant/Ansible ecostructure? Someone had installed Gitlab private repository on my laptop using vvagrant/ansible/kitchen and I was trying to "map" various files I am seeing against your videos. I understand now that I could have installed Gitlab using Ansible playbook directly. But I guess Kitchen "recipes" make it easier? THey are pre-packaged? THanks
ОтветитьThis is best example I understood so far. Keep it up.
ОтветитьHi guys, I'm having problems when I run "Vagrant up", the following error appears:
An error occurred while executing a PowerShell script. This error
is shown below. Please read the error message and see if this is
a configuration error with your system. If it is not, then please
report a bug.
Script: check_hyperv_access.ps1
Error:
Get-ACL : Falha do método com código de erro inesperado 1.
No \\wsl$\Ubuntu-20.04\opt\vagrant\embedded\gems\2.2.14\gems\vagrant-2.2.14\plugins\providers\hyperv\scripts\utils\Vagr
antVM\VagrantVM.psm1:731 caractere:12
+ $acl = Get-ACL -Path $Path
+ ~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Get-Acl], InvalidOperationException
+ FullyQualifiedErrorId : System.InvalidOperationException,Microsoft.PowerShell.Commands.GetAclCommand
Why not run both vagrant and ansible on a linux host with kvm as the hypervisor? Feels sort of contrived to run it in WSL no ?
ОтветитьNice video, and your channel is great overall too.
ОтветитьThanks .. great video
ОтветитьIts more effective if you add the variables as follows:
export VAGRANT_WSL_ENABLE_WINDOWS_ACCESS=1
export PATH=$PATH:/mnt/c/Windows/System32
export PATH="$PATH:/mnt/c/ProgramData/Microsoft/Windows/Hyper-V"
export VAGRANT_DEFAULT_PROVIDER=hyperv
Very cool indeed
Ответить😍❣️
ОтветитьI added the Vagrant env variables to .bashrc, I have Vagrant installed on Windows host, but I still get the cmd.exe error. I sourced the .bashrc file and then logged off and back in, but still no luck. Ideas?
ОтветитьAMD processors are capable of nested virtualizations. Is this a limitation of Windows? I use a 1950x with multiple nested virtualizations.
Ответитьthanks
a lot <3
I am getting the below error, any idea how to fix this ?
/opt/vagrant/embedded/gems/2.2.18/gems/vagrant-2.2.18/lib/vagrant/util/subprocess.rb:160:in `rescue in execute': Permission denied - /mnt/c/Windows/system32/powershell
You are a great guy
ОтветитьIs it posible to do this Vagrant to a remote server?
Like when i sit on my linux laptop and have a Win server in the rack?
Time for a new video? ;)
so freaking cool!
ОтветитьI really need some help, I've searched all over internet and haven't foun a clue:
When i do vagrant up my it stops at SSH authentification. it simply doesn't want to work from there. Any solution?
Hey, thanks for the good job. I would like to see more on vagrant. Using vagrant as your lab for testing ansible simulation and stuffs like that.
ОтветитьThank you
Ответитьhow about provisioning centos 07 server??
ОтветитьEasy to understand, very laconic and nice timbre of the voice. Thank you, good sir.
Ответить