yes that's correct I already did that individual commands are running in ssh, but not able run through vagrant external script provisioning
i got the above error, is it related guest addition or what is that X ? Thanks & Regards, Kathirvel G On Tue, May 5, 2020 at 10:07 AM Alvaro Miranda Aguilera <[email protected]> wrote: > You don't seems to have an X running. > > This usually happens if you run a graphical application or an application > that need graphics > > just ssh to the machine, copy and run the script to see if you see the > same error. > > if you hit the same error, the error is coming from the scripts and the > way is being run and not vagrant. > > Thanks > Alvaro > > On Mon, Apr 27, 2020 at 11:52 AM kathir <[email protected]> wrote: > >> Hi >> >> When i tried to use vagrant file provisioning using external shell >> script, i ended up to look into log file as it says >> >> Could not find the X.Org or XFree86 Window System, skipping >> >> Please suggest >> Thanks & Regards, >> Kathirvel G >> >> >> On Mon, Apr 27, 2020 at 10:00 AM Alvaro Miranda Aguilera < >> [email protected]> wrote: >> >>> so, make sure you can ping both IP from both host >>> >>> on machine1 >>> - ping local >>> - ping remote >>> >>> on machine2 >>> - ping local >>> - ping remote >>> >>> if one fails, then you should focus on that first. >>> >>> As you are using hyper-v, I can't help much, but basically you may want >>> to see way to give to the VMs an IP from your network. >>> >>> Alvaro. >>> >>> On Fri, Apr 24, 2020 at 3:10 PM DC <[email protected]> wrote: >>> >>>> I am using the latest vagrant version running on my windows 10 >>>> professional x64. I configured my Network device to share the connection >>>> with my internal virtual switch (HyperV). Everything seams okay and I can >>>> bring up my VM without any issues. I am using the following box >>>> (generic/ubuntu1804). >>>> >>>> The problem that I have is that once that my host gets the assigned the >>>> admin role, after run "docker swarm init", I tried to add the Hypervisor as >>>> a Worker node and I seems like is docker can not see it :-/. >>>> >>>> *These are the steps that I followed:* >>>> >>>> # Bring up w1 (My vagrantfile will handle the provider,etc) IP = >>>> 192.163.135.199 >>>> *vagrant up w1* >>>> >>>> # host machine >>>> *docker init swarm* >>>> *To add a worker to this swarm, run the following command:* >>>> >>>> *docker swarm join --token >>>> SWMTKN-1-36gi398mfzkq8q9f4qt6u5wll7xv88a4u0osv8rpofmmvknunn-91ogycjru6p29p44f7iam63il >>>> * >>>> 192.163.135.197*:2377* >>>> >>>> *To add a manager to this swarm, run 'docker swarm join-token manager' >>>> and follow the instructions.* >>>> >>>> # Switch to Worker >>>> *$env:DOCKER_HOST="192.163.135.199"* >>>> >>>> # I verified that docker can see this node >>>> >>>> *docker info* >>>> >>>> # docker shows Name: w1 :-) >>>> >>>> # Join the current node as worker >>>> *docker swarm join --token >>>> SWMTKN-1-36gi398mfzkq8q9f4qt6u5wll7xv88a4u0osv8rpofmmvknunn-91ogycjru6p29p44f7iam63il >>>> 192.163.135.197:2377 >>>> <http://192.163.135.197:2377>* >>>> *Error response from daemon: Timeout was reached before node joined. >>>> The attempt to join the swarm will continue in the background. Use the >>>> "docker info" command to see the current swarm status of your node.* >>>> >>>> *Troubleshooting:* >>>> >>>> I ping the VM and the host is able to see it, but if *I try to ping >>>> the host from the VM, it failed* :-/. I am guessing that it has to do >>>> with the way that I configured the internal virtual switch :-/. Any >>>> recommendation? >>>> >>>> >>>> -- >>>> This mailing list is governed under the HashiCorp Community Guidelines >>>> - https://www.hashicorp.com/community-guidelines.html. Behavior in >>>> violation of those guidelines may result in your removal from this mailing >>>> list. >>>> >>>> GitHub Issues: https://github.com/mitchellh/vagrant/issues >>>> IRC: #vagrant on Freenode >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "Vagrant" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/vagrant-up/aa877eb8-2fd8-4e9c-b9ec-f3b586794631%40googlegroups.com >>>> <https://groups.google.com/d/msgid/vagrant-up/aa877eb8-2fd8-4e9c-b9ec-f3b586794631%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> >>> >>> -- >>> Alvaro >>> >>> -- >>> This mailing list is governed under the HashiCorp Community Guidelines - >>> https://www.hashicorp.com/community-guidelines.html. Behavior in >>> violation of those guidelines may result in your removal from this mailing >>> list. >>> >>> GitHub Issues: https://github.com/mitchellh/vagrant/issues >>> IRC: #vagrant on Freenode >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "Vagrant" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/vagrant-up/CAHqq0exgOwL2qZgr6BuYGUixsPHeLs1h%3DwG7rbr9Y0Z-p2Vc%2BQ%40mail.gmail.com >>> <https://groups.google.com/d/msgid/vagrant-up/CAHqq0exgOwL2qZgr6BuYGUixsPHeLs1h%3DwG7rbr9Y0Z-p2Vc%2BQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- >> This mailing list is governed under the HashiCorp Community Guidelines - >> https://www.hashicorp.com/community-guidelines.html. Behavior in >> violation of those guidelines may result in your removal from this mailing >> list. >> >> GitHub Issues: https://github.com/mitchellh/vagrant/issues >> IRC: #vagrant on Freenode >> --- >> You received this message because you are subscribed to the Google Groups >> "Vagrant" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/vagrant-up/CADArzrt4X%2BTDST27tfMfLxc3uCF80TaUtZ9%2B7N6tn8Odndx-5A%40mail.gmail.com >> <https://groups.google.com/d/msgid/vagrant-up/CADArzrt4X%2BTDST27tfMfLxc3uCF80TaUtZ9%2B7N6tn8Odndx-5A%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > > > -- > Alvaro > > -- > This mailing list is governed under the HashiCorp Community Guidelines - > https://www.hashicorp.com/community-guidelines.html. Behavior in > violation of those guidelines may result in your removal from this mailing > list. > > GitHub Issues: https://github.com/mitchellh/vagrant/issues > IRC: #vagrant on Freenode > --- > You received this message because you are subscribed to the Google Groups > "Vagrant" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/vagrant-up/CAHqq0ezC4a6ZKjcfxku%2BgT74wwjn-8SXZ2vpvMYuSfToNYE%3Dgg%40mail.gmail.com > <https://groups.google.com/d/msgid/vagrant-up/CAHqq0ezC4a6ZKjcfxku%2BgT74wwjn-8SXZ2vpvMYuSfToNYE%3Dgg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CADArzrvq5OvM3YCvqkPWgZ5sLK5H8z3w60Nz%2B-ThFnLyt8gYuQ%40mail.gmail.com.
