I am wanting to tinker around with Mail-in-a-Box. I want to be able to change stuff up, and deploy it quickly. I followed the instructions here: https://github.com/mail-in-a-box/mailinabox/blob/master/CONTRIBUTING.md
and it appears that it did create a virtualbox machine, but I don’t understand how it works, and how to access it. Any pointers?
Here is the log of it: https://paste.ubuntu.com/p/nPsxwVyXCs/
Just do vagrant ssh (from the same dir you ran vagrant up) and this will log you in to the virtual machine. Your dir containing the mailinabox code will be mounted under /vagrant.
I don’t see the /vagrant mount on the guest operating system. Does mail-in-a-Box even install on this, or is this SSH issue affecting the install of Mail-in-a-Box?
Could it be that it does not like the IP address of 192.168.50.4. Apparently, when I do vagrant ssh, it gets me into the box, and when I do ifconfig, it is assigned the IP address of 10.0.2.15. How do I change it, because it seemed to still be having issues when I changed Vagrantfile in Mail-in-a-Box to the IP address 10.0.2.15. I wasn’t sure if there were more things I should configure to make sure I completely change the IP address.
So it appears that the ifupdown Ubuntu package previously came with Ubuntu 14.04, and is no longer included in the Ubuntu 18.04 LTS system by default (see https://github.com/cilium/cilium/issues/1918 ). This is the error:
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
ifdown -a; ifup -a; ifup -a --allow=hotplug
Stdout from the command:
Stderr from the command:
mesg: ttyname failed: Inappropriate ioctl for device
bash: line 2: ifdown: command not found
bash: line 2: ifup: command not found
bash: line 2: ifup: command not found
After I get into the system using vagrant ssh and doing sudo apt-get install ifupdown, shutting down the machine and doing vagrant up --provision, it gives me another error:
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
/sbin/ifdown eth1 2> /dev/null
Stdout from the command:
Stderr from the command:
mesg: ttyname failed: Inappropriate ioctl for device
So it appears this is also a problem, due to the fact that Ubuntu switched to systemd, because of “Predictable Network Interface naming”, since Ubuntu 15.04 (see: https://askubuntu.com/questions/704361/why-is-my-network-interface-named-enp0s25-instead-of-eth0 and Predictable Network Interface naming ).
Is there any way to fix this, so I can smooth the process of developing and testing Mail-in-a-Box? @JoshData?
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.