I want to set a development environment like on my production server so I setup Vagrant box with Ubuntu 16.04 server.
I added to vagrant file:
config.vm.network :private_network, ip: "192.168.22.10"
config.vm.network :forwarded_port, guest: 80, host: 8080
and I can see apache site on a browser when I type 192.168.22.10
So far so good. After installation it showed me to access via:
https://dev-stolmet.akcesoriameblowe-online.pl:10000 (or https://10.0.2.15:10000)
I also added to my hosts file in my host system: 192.168.22.10 dev-stolmet.akcesoriameblowe-online.pl
So I can access defauit apache site in a browser by using:
dev-stolmet.akcesoriameblowe-online.pl
I was able to launch Virtualing site by:
https://dev-stolmet.akcesoriameblowe-online.pl:10000/
However, after I logged in, I see this incompleted, whitish themed virtualmin's UI (as if theming was failing), the site tries to load the dashboard but eventually fails and shows connection lost and my viritual system is getting crazy (high CPU and HDD usage) to the point that vagrant is hardly responsive in terminal. I have to reboot the machine. Basically, it looks like virtualmin is crashing or preoccupying vagrant. The hint I have is when I try to exit vagrant in terminal and I get:
-bash: fork: Cannot allocate memory
So my theory is: virtualmin is too heavy for the standard vagrant box and simply is trying to expand swap file which makes the system unresponsive, which crashes virtualmint, because even if I let it run and calmed itself, virtualmin is no more (no connection), untill I reboot and the "fun" begins anew.
I cannot increase discs sizes (10GB dynamically allocated) in vbox GUI. Is there a way to modify them? Or maybe someone has an idea what is happening and it may not be the memory issue?
EDIT: I was able to increase memory from 1 to 2GB and it helped. I see post-install configuration, sometimes connection gets lost but in overall it works.