I am trying to make my vagrant box accessible over internet for quick customer review. I tried to get it working over noip but somehow it did not work and I don't even know why. My networking knowledge is quite beginner level and now even more confused.
Do I have to use vagrants bridged network option to do that ?
How would you do that. Should be pretty common to allow access for that purpose
vagrant share is the feature you're looking
Vagrant Share allows you to share your Vagrant environment with anyone
in the world, enabling collaboration directly in your Vagrant
environment in almost any network environment with just a single
command: vagrant share.
Just make sure you dont tie your webserver to localhost or the hostname as vagrant will give you a temporary url to access the instance
Related
I run Memgraph Platform on my laptop inside Docker container. When I'm at the office my colleague can access it, but when I work from home he can not get to the database. I don't have fixed IP address, and my ISP doesn't allow me to do port forwarding and dynamic DNS also doesn't work for me. What can I do to make my database accessible to others?
Try to follow the advice given by #Martheen. I have experience with running Tailscale for this purpose and it works.
I don't know why you can't deploy it to some server (if there are regulation issues or company policies in question) but if it is not any of those maybe you could use Memgraph Cloud and host your data. That way you would be sure that everyone with the right credentials could access your data. But it all depends on your setup and usage scenario. Since you are using Docker I presume that you have all of your environment configured right the way that you want on your laptop.
Hi Guys I have a situation where I don't want use vagrant user or any other user for ssh. Whenever I do vagrant up the VM's boots and I get the below error for ssh. Its because of timeout as it is unable to find vagrant user. By default when we do vagrant up the vagrants checks for vm to boot and it does the same by sshing. Is there is way where I can ignore this bootstrap error or skip the ssh step? I did an extensive search and unable to find any documentation regarding the same. The reason I need this is because I have multiple VM which needs to be started one by one. I need to skip this error or ignore the below error so that all the VM's are started.
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within the
configured ("config.vm.boot_timeout" value) time period.
If you look above, you should be able to see the error(s) that Vagrant
had when attempting to connect to the machine. These errors are
usually good hints as to what may be wrong.
If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes. Verify
that authentication configurations are also setup properly, as well.
If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.
I have a vagrant machine and this vm runs a DNS server to resolve the internal domains of each micro-service instance running in a docker container inside the vagrant. Actually, after run vagrant up, I need to put the vagrant vm IP address in my network configuration to my computer resolve the development domain, so I can access the application, but the problem is that I work remotelly and frequently I need to connect in public hotspots that uses network authentication and if I have the vagrant DNS in my interface's configuration I could not connect to the hotspot without removing the vagrant IP, but I need to put it back after some minutes later to start working.
So, the question is, there is a way to configure an virtual interface or a VPN interface that points to the vagrant but does not block my network as I describe above ?
When I was using linux, I just put the vagrant IP in the resolv.conf and I had no headaches, but as MacOS does not have the resolv.conf like linux, I could not find a easy way to deal with theses problems.
I have 2 VM running, one is giving me a local server on an address like www.x.com (FREE BSD 64bit), which I can access from my browsers locally.
My question is, if I use another VM to test with windows and IE, how can I access my www.x.com given from my other running VM with the second VM? That means, from IE?
Is that possible?
Thanks a lot, this would help me a lot, I have to deploy to our testing servers everytime I want to test something on IE and is quite annoying!
Possible, of course. To connect to your VM both from host system and another VM you can set bridget networking for both VMs (BTW, maybe you already using network bridge). There are also other possibilities, but bridget network is easiest way, IMHO.
I've done some read-up on Vagrant with Chef-Server v/s Vagrant with Chef-solo and have found blogs talking about the usage of the same. I've failed to find anybody summarizing the advantages of either approach. So, here's my question.
I understand that Vagrant cannot spin up virtual machines on a remote machine. This means running "vagrant up" on a particular machine will spin up VMs on that machine alone.
First of all, is this understanding right?
If yes, what’s the point of using a chef server to provision the server?
I feel that if I’m using Vagrant, using chef solo is the way to go and chef
server isn’t adding any value.
Do you think I’m missing something?
Vagrant is used for spin up VMs and you can provision those VMs with the help of chef recipes or via any other provisioning method. https://docs.vagrantup.com/v2/provisioning/index.html
Now, Difference between Chef Server and Chef-Solo:
Chef Server works in Client Server Architecture. You can control or manage all your nodes (VMs launched by Vagrant) with the help of Chef Server. In a particular VM, you can search for other nodes with the help of Chef Server.
Chef-Solo works in Solo mode means, you can provision only single node and you can not get any information about the other nodes. However several techniques exists to overcome such situations like chef-solo-search.