PeerOS vagrant image failing installation on CentOS

[marcoarthur]

Subutai user on public slack, reported us problems on installation of PeerOs using instructions on https://docs.subutai.io/Products/PeerOS/03_Run_PeerOS_with_Vagrant.html

He got stuck on:

default: subutai is installed
   default: Container storage already mounted.
   default: Provisioning management capabilities (converting RH into peer)
   default: This might take a little time ...
   default: time="2018-07-02 18:07:28" level=info msg="Importing management"

Info about his system:

uname -a
Linux 3.10.0-862.3.3.el7.x86_64 #1 SMP Fri Jun 15 04:15:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
cat /proc/cpuinfo
processor    : 0
vendor_id    : GenuineIntel
cpu family    : 6
model        : 6
model name    : QEMU Virtual CPU version 2.0.0
stepping    : 3
microcode    : 0x1
cpu MHz        : 2099.998
cache size    : 4096 KB
physical id    : 0
siblings    : 1
core id        : 0
cpu cores    : 1
apicid        : 0
initial apicid    : 0
fpu        : yes
fpu_exception    : yes
cpuid level    : 4
wp        : yes
flags        : fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pse36 clflush mmx fxsr sse sse2 syscall nx lm rep_good nopl eagerfpu pni vmx cx16 x2apic popcnt hypervisor lahf_lm tpr_shadow vnmi flexpriority ept vpid
bogomips    : 4199.99
clflush size    : 64
cache_alignment    : 64
address sizes    : 40 bits physical, 48 bits virtual
power management:

free -h
             total        used        free      shared  buff/cache   available
Mem:           7.6G        3.8G        283M         41M        3.5G        3.3G
Swap:          511M          0B        511M

vagrant version
Installed Version: 2.1.2
Latest Version: 2.1.2

[etursunbaev]

@marcoarthur @lbthomsen @Dilshat Let's close this issue till we will reproduce We didn't face such issue It is mostly network issue

[etursunbaev]

btw what user in Slack? It would be nice if we can get him back

[etursunbaev]

it is macari user and the problem was in CentOS as I understood

[etursunbaev]

Let's close @Dilshat ?