search

kumahq / kuma-demo

A demo app to illustrate the capabilities and advantages of Kuma. 🐻
https://kuma.io/
Apache License 2.0
58 stars 54 forks source link

When running vagrant up deployment errors out #143

Closed squashedlime closed 2 years ago

squashedlime commented 2 years ago

What happened?

MacOS - 12.2.1 Virtual box - 6.1.32 VB extensions - 6.1.32 Vagrant - 2.2..19

So I was trying to spin up the kuma-demo but I just error out after creating the first VM. There seems no way to ssh to the VM either. Here is the output from my attempt.

How do I get the VM to run without this erroring out?

Bringing machine 'kuma-control-plane' up with 'virtualbox' provider...
Bringing machine 'redis' up with 'virtualbox' provider...
Bringing machine 'postgresql' up with 'virtualbox' provider...
Bringing machine 'metrics' up with 'virtualbox' provider...
Bringing machine 'backend' up with 'virtualbox' provider...
Bringing machine 'backend-v1' up with 'virtualbox' provider...
Bringing machine 'frontend' up with 'virtualbox' provider...
Bringing machine 'kong' up with 'virtualbox' provider...
==> kuma-control-plane: Checking if box 'ubuntu/trusty64' version '20190514.0.0' is up to date...
==> kuma-control-plane: Clearing any previously set forwarded ports...
==> kuma-control-plane: Clearing any previously set network interfaces...
==> kuma-control-plane: Preparing network interfaces based on configuration...
    kuma-control-plane: Adapter 1: nat
    kuma-control-plane: Adapter 2: hostonly
==> kuma-control-plane: Forwarding ports...
    kuma-control-plane: 22 (guest) => 2222 (host) (adapter 1)
==> kuma-control-plane: Running 'pre-boot' VM customizations...
==> kuma-control-plane: Booting VM...
==> kuma-control-plane: Waiting for machine to boot. This may take a few minutes...
    kuma-control-plane: SSH address: 127.0.0.1:2222
    kuma-control-plane: SSH username: vagrant
    kuma-control-plane: SSH auth method: private key
==> kuma-control-plane: Machine booted and ready!
[kuma-control-plane] A Virtualbox Guest Additions installation was found but no tools to rebuild or start them.
 * Stopping VirtualBox Additions
   ...done.
Reading package lists...
Building dependency tree...
Reading state information...
The following packages were automatically installed and are no longer required:
  acl at-spi2-core colord dconf-gsettings-backend dconf-service fontconfig
  fontconfig-config fonts-dejavu-core hicolor-icon-theme libasound2
  libasound2-data libatk-bridge2.0-0 libatk1.0-0 libatk1.0-data libatspi2.0-0
  libavahi-client3 libavahi-common-data libavahi-common3 libcairo-gobject2
  libcairo2 libcanberra-gtk3-0 libcanberra-gtk3-module libcanberra0 libcolord1
  libcolorhug1 libcups2 libdatrie1 libdconf1 libdrm-intel1 libdrm-nouveau2
  libdrm-radeon1 libexif12 libfontconfig1 libfontenc1 libgd3
  libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libgl1-mesa-dri libgl1-mesa-glx
  libglapi-mesa libgphoto2-6 libgphoto2-l10n libgphoto2-port10 libgraphite2-3
  libgtk-3-0 libgtk-3-bin libgtk-3-common libgudev-1.0-0 libgusb2
  libharfbuzz0b libice6 libieee1284-3 libjasper1 libjbig0 libjpeg-turbo8
  libjpeg8 liblcms2-2 libllvm3.4 libltdl7 libnotify-bin libnotify4 libogg0
  libpango-1.0-0 libpangocairo-1.0-0 libpangoft2-1.0-0 libpciaccess0
  libpixman-1-0 libsane libsane-common libsm6 libtdb1 libthai-data libthai0
  libtiff5 libtxc-dxtn-s2tc0 libv4l-0 libv4lconvert0 libvorbis0a
  libvorbisfile3 libvpx1 libwayland-client0 libwayland-cursor0 libx11-xcb1
  libxaw7 libxcb-dri2-0 libxcb-dri3-0 libxcb-glx0 libxcb-present0
  libxcb-render0 libxcb-shm0 libxcb-sync1 libxcomposite1 libxcursor1
  libxdamage1 libxfixes3 libxfont1 libxi6 libxinerama1 libxkbcommon0
  libxkbfile1 libxmu6 libxpm4 libxrandr2 libxrender1 libxshmfence1 libxt6
  libxtst6 libxxf86vm1 notification-daemon sound-theme-freedesktop x11-common
  x11-xkb-utils xfonts-base xfonts-encodings xfonts-utils xserver-common
  xserver-xorg-core
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
  virtualbox-guest-dkms* virtualbox-guest-utils* virtualbox-guest-x11*
0 upgraded, 0 newly installed, 3 to remove and 1 not upgraded.
After this operation, 12.2 MB disk space will be freed.
(Reading database ... 69698 files and directories currently installed.)
Removing virtualbox-guest-dkms (4.3.40-dfsg-0ubuntu14.04.1) ...

-------- Uninstall Beginning --------
Module:  virtualbox-guest
Version: 4.3.40
Kernel:  3.13.0-170-generic (x86_64)
-------------------------------------

Status: Before uninstall, this module version was ACTIVE on this kernel.

vboxguest.ko:
 - Uninstallation
   - Deleting from: /lib/modules/3.13.0-170-generic/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

vboxsf.ko:
 - Uninstallation
   - Deleting from: /lib/modules/3.13.0-170-generic/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

vboxvideo.ko:
 - Uninstallation
   - Deleting from: /lib/modules/3.13.0-170-generic/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

depmod.....

DKMS: uninstall completed.

------------------------------
Deleting module version: 4.3.40
completely from the DKMS tree.
------------------------------
Done.
Removing virtualbox-guest-x11 (4.3.40-dfsg-0ubuntu14.04.1) ...
Purging configuration files for virtualbox-guest-x11 (4.3.40-dfsg-0ubuntu14.04.1) ...
Removing virtualbox-guest-utils (4.3.40-dfsg-0ubuntu14.04.1) ...
Purging configuration files for virtualbox-guest-utils (4.3.40-dfsg-0ubuntu14.04.1) ...
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Processing triggers for libc-bin (2.19-0ubuntu6.15) ...
Reading package lists...
Building dependency tree...
Reading state information...
dkms is already the newest version.
linux-headers-3.13.0-170-generic is already the newest version.
The following packages were automatically installed and are no longer required:
  acl at-spi2-core colord dconf-gsettings-backend dconf-service fontconfig
  fontconfig-config fonts-dejavu-core hicolor-icon-theme libasound2
  libasound2-data libatk-bridge2.0-0 libatk1.0-0 libatk1.0-data libatspi2.0-0
  libavahi-client3 libavahi-common-data libavahi-common3 libcairo-gobject2
  libcairo2 libcanberra-gtk3-0 libcanberra-gtk3-module libcanberra0 libcolord1
  libcolorhug1 libcups2 libdatrie1 libdconf1 libdrm-intel1 libdrm-nouveau2
  libdrm-radeon1 libexif12 libfontconfig1 libfontenc1 libgd3
  libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libgl1-mesa-dri libgl1-mesa-glx
  libglapi-mesa libgphoto2-6 libgphoto2-l10n libgphoto2-port10 libgraphite2-3
  libgtk-3-0 libgtk-3-bin libgtk-3-common libgudev-1.0-0 libgusb2
  libharfbuzz0b libice6 libieee1284-3 libjasper1 libjbig0 libjpeg-turbo8
  libjpeg8 liblcms2-2 libllvm3.4 libltdl7 libnotify-bin libnotify4 libogg0
  libpango-1.0-0 libpangocairo-1.0-0 libpangoft2-1.0-0 libpciaccess0
  libpixman-1-0 libsane libsane-common libsm6 libtdb1 libthai-data libthai0
  libtiff5 libtxc-dxtn-s2tc0 libv4l-0 libv4lconvert0 libvorbis0a
  libvorbisfile3 libvpx1 libwayland-client0 libwayland-cursor0 libx11-xcb1
  libxaw7 libxcb-dri2-0 libxcb-dri3-0 libxcb-glx0 libxcb-present0
  libxcb-render0 libxcb-shm0 libxcb-sync1 libxcomposite1 libxcursor1
  libxdamage1 libxfixes3 libxfont1 libxi6 libxinerama1 libxkbcommon0
  libxkbfile1 libxmu6 libxpm4 libxrandr2 libxrender1 libxshmfence1 libxt6
  libxtst6 libxxf86vm1 notification-daemon sound-theme-freedesktop x11-common
  x11-xkb-utils xfonts-base xfonts-encodings xfonts-utils xserver-common
  xserver-xorg-core
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Copy iso file /Applications/VirtualBox.app/Contents/MacOS/VBoxGuestAdditions.iso into the box /tmp/VBoxGuestAdditions.iso
Mounting Virtualbox Guest Additions ISO to: /mnt
mount: block device /tmp/VBoxGuestAdditions.iso is write-protected, mounting read-only
Installing Virtualbox Guest Additions 6.1.32 - guest version is 4.3.40
Verifying archive integrity... All good.
Uncompressing VirtualBox 6.1.32 Guest Additions for Linux........
VirtualBox Guest Additions installer
Copying additional installer modules ...
Installing additional modules ...
VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel
modules.  This may take a while.
VirtualBox Guest Additions: To build modules for other installed kernels, run
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup <version>
VirtualBox Guest Additions: or
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup all
VirtualBox Guest Additions: Building the modules for kernel 3.13.0-170-generic.
 Adding system startup for /etc/init.d/vboxadd ...
   /etc/rc0.d/K90vboxadd -> ../init.d/vboxadd
   /etc/rc1.d/K90vboxadd -> ../init.d/vboxadd
   /etc/rc6.d/K90vboxadd -> ../init.d/vboxadd
   /etc/rc2.d/S10vboxadd -> ../init.d/vboxadd
   /etc/rc3.d/S10vboxadd -> ../init.d/vboxadd
   /etc/rc4.d/S10vboxadd -> ../init.d/vboxadd
   /etc/rc5.d/S10vboxadd -> ../init.d/vboxadd
 Adding system startup for /etc/init.d/vboxadd-service ...
   /etc/rc0.d/K65vboxadd-service -> ../init.d/vboxadd-service
   /etc/rc1.d/K65vboxadd-service -> ../init.d/vboxadd-service
   /etc/rc6.d/K65vboxadd-service -> ../init.d/vboxadd-service
   /etc/rc2.d/S35vboxadd-service -> ../init.d/vboxadd-service
   /etc/rc3.d/S35vboxadd-service -> ../init.d/vboxadd-service
   /etc/rc4.d/S35vboxadd-service -> ../init.d/vboxadd-service
   /etc/rc5.d/S35vboxadd-service -> ../init.d/vboxadd-service
Building the VirtualBox Guest Additions kernel modules.  This may take a while.
To build modules for other installed kernels, run
  /sbin/rcvboxadd quicksetup <version>
or
  /sbin/rcvboxadd quicksetup all
Running kernel modules will not be replaced until the system is restarted
vboxadd-service.sh: Starting VirtualBox Guest Addition service.
VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel
modules.  This may take a while.
VirtualBox Guest Additions: To build modules for other installed kernels, run
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup <version>
VirtualBox Guest Additions: or
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup all
VirtualBox Guest Additions: Running kernel modules will not be replaced until
the system is restarted
Unmounting Virtualbox Guest Additions ISO from: /mnt
==> kuma-control-plane: Checking for guest additions in VM...
==> kuma-control-plane: Setting hostname...
==> kuma-control-plane: Configuring and enabling network interfaces...
==> kuma-control-plane: Mounting shared folders...
    kuma-control-plane: /vagrant => /Users/jasmor/Documents/Code/temp/kuma-demo/vagrant
==> kuma-control-plane: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> kuma-control-plane: flag to force provisioning. Provisioners marked to run always will still run.
==> kuma-control-plane: Running provisioner: await_kuma-cp (shell)...
    kuma-control-plane: Running: /var/folders/4t/q11wg0bd25l9sx4pmn3h4z700000gp/T/vagrant-shell20220223-10584-j65kyu.sh
    kuma-control-plane: try #1:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #2:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #3:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #4:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #5:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #6:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #7:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #8:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #9:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #10:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #11:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #12:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #13:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #14:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #15:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #16:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #17:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #18:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #19:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #20:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #21:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #22:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #23:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
    kuma-control-plane: try #24:
    kuma-control-plane: curl: (7) Failed to connect to localhost port 5681: Connection refused
^C==> kuma-control-plane: Waiting for cleanup before exiting...

The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
lahabana commented 2 years ago

Currently the vagrant demo is not really supported anymore. We're thinking about what could be done to improve this but it's not decided yet. Do you need help running something on Universal?

github-actions[bot] commented 2 years ago

Automatically closing the issue due to having one of the "closed state label".