Swarm VM Build Chat

Download as txt, pdf, or txt
Download as txt, pdf, or txt
You are on page 1of 22

Azharudeen AshrafAli5:16 PM

I dont have access to Docker Swarm book


can you provide
Sathiyaraj Sridhar5:17 PM
Those who are using Winsows run it on the Git Bash.
John Sundarraj5:17 PM
sudo git clone https://github.com/sloopstash/kickstart-swarm.git /opt/kickstart-
swarm
sudo chown -R $USER:$USER /opt/kickstart-swarm
karthik s5:18 PM
yes
Bharath Sathyan5:18 PM
yes
Rajkumar R T5:18 PM
yes
sathyaraj k5:18 PM
yes
Sathishkumar M5:18 PM
yes
Balakrishna G5:18 PM
yes
Sathiyaraj Sridhar5:18 PM
For windows user, don't run as sudo.
vamsi krishna5:20 PM
Before running in windows... do we need to exit VM ?
debi5:21 PM
root@linux:~# git clone https://github.com/sloopstash/kickstart-flask.git
/opt/kickstart-docker/app
fatal: destination path '/opt/kickstart-docker/app' already exists and is not an
empty directory.
root@linux:~#
getting error
Sathiyaraj Sridhar5:21 PM
Don't run vagrant VM. You guys have to clone it on Git Bash.
RamSenthil Kumar5:22 PM
Is it right?
vagrant@sloopstash-ubuntu-desktop:/opt/kickstart-swarm$ ls
LICENSE nginx README.md redis script stack supervisor vagrant
vagrant@sloopstash-ubuntu-desktop:/opt/kickstart-swarm$
Kavi Arasu5:22 PM
am not able see docker swarm in evernote
Balakrishna G5:22 PM
there is no sudo
sudo at beginning need to be added?
You5:27 PM
i can not share the book
lokesh kannan5:27 PM
check in shared with me
kishore v5:28 PM
yes
Mathivanan5:28 PM
yes
Kalaiarasan Kirubanandam5:28 PM
yes
Rajkumar R T5:28 PM
yes
vamsi krishna5:28 PM
Yes
Sunil Munusamy5:28 PM
yes
Tajdeen Abdulla5:28 PM
yes
Dhivyashree M5:28 PM
yes
Azharudeen AshrafAli5:28 PM
s working
Sadhana D5:31 PM
I am getting no bash: sudo: command not found
Dharmaraj
You5:31 PM
debdash@N-20S1PF22AQV2 MINGW64 ~
$ sudo apt install git
bash: sudo: command not found
getting this error in windows
sathyaraj k5:31 PM
inprogress
Sadhana D5:32 PM
Okay
Balakrishna G5:32 PM
under kickstart-swarm path?
You5:32 PM
windows not working
Balakrishna G5:32 PM
we have to install?
Sadhana D5:32 PM
from windows
RamSenthil Kumar5:32 PM
after git bash clone??
what we need to do john??
Sadhana D5:32 PM
Sorry now it cloned
Sathishkumar M5:33 PM
msk@msk-HP-EliteBook-Folio-9480m:/opt/kickstart-swarm$ sudo apt install gcc make
perl
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to
correct the problem.
John Sundarraj5:34 PM
sudo dpkg --configure -a
Balakrishna G5:34 PM
Do we have to install under kickstart-swarm?
ok
You5:35 PM
debdash@N-20S1PF22AQV2 MINGW64 ~
$ git clone https://github.com/sloopstash/kickstart-swarm.git /opt/kickstart-swarm
Cloning into 'C:/Program Files/Git/opt/kickstart-swarm'...
remote: Enumerating objects: 53, done.
remote: Counting objects: 100% (53/53), done.
remote: Compressing objects: 100% (31/31), done.
remote: Total 53 (delta 17), reused 49 (delta 13), pack-reused 0
Unpacking objects: 100% (53/53), 25.84 KiB | 144.00 KiB/s, done.

debdash@N-20S1PF22AQV2 MINGW64 ~
$ chown -R $USER:$USER /opt
i did it in windows
is it correct
Vishal S5:35 PM
after cloning how git bash will look in windows any one can share?
Kolli Santhosh5:35 PM
Sathiyaraj, i am not able see to swarm book in evernote,
Muthu Kumaran5:35 PM
virtualbox --help
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (5.4.0-70-generic) or it failed to
load. Please recompile the kernel module and install it by

sudo /sbin/vboxconfig

You will not be able to start VMs until this problem is fixed.
/usr/lib/virtualbox/VirtualBox: error while loading shared libraries:
libQt5Core.so.5: cannot open shared object file: No such file or directory
Sadhana D5:36 PM
$ apt install gcc make perl
bash: apt: command not found
Sathiyaraj Sridhar5:36 PM
@Kolli Santhosh: Please check properly, We shared it.
Prakash K5:36 PM
git clone https://github.com/sloopstash/kickstart-swarm.git /opt/kickstart-swarm
fatal: could not create leading directories of 'C:/Program Files/Git/opt/kickstart-
swarm': Permission denied
error in windows
Sunil Munusamy5:37 PM
virtualbox --help
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (4.18.0-15-generic) or it failed to
load. Please recompile the kernel module and install it by

sudo /sbin/vboxconfig

You will not be able to start VMs until this problem is fixed.
/usr/lib/virtualbox/VirtualBox: error while loading shared libraries:
libQt5OpenGL.so.5: cannot open shared object file: No such file or directory
Aanchal Mathew5:37 PM
$ vagrant --version
Vagrant 2.2.9
is this right
Sadhana D5:37 PM
Okay
Sunil Munusamy5:37 PM
gettinng the error
Azharudeen AshrafAli5:37 PM
@Koli Santhosh - in left pane, click on Shared With Me icon, from there you can
access the swarm book
Dhivyashree M5:37 PM
vagrant gives the same output as yours
kishore v5:38 PM
I can see vagrant
Dhivyashree M5:38 PM
but virtual box throws error
archana sekar5:38 PM
am not able to see
Mathivanan5:38 PM
yes
vinitha Ragamsetty5:38 PM
i can see
You5:38 PM
windows how can we see
Pethu Raj5:38 PM
Virtual img download is in progress
Dhivyashree M5:38 PM
virtualbox --help
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (5.4.0-65-generic) or it failed to
load. Please recompile the kernel module and install it by

sudo /sbin/vboxconfig

You will not be able to start VMs until this problem is fixed.
Jaicy Vignesh5:38 PM
Its throwing error for windows host machine
Dhivyashree M5:38 PM
ok John
sudha TM5:38 PM
not able to get the output
Jaicy Vignesh5:39 PM
Vignesh@DESKTOP-17F6HDN MINGW64 ~
$ apt install git
bash: apt: command not found
Sunil Munusamy5:39 PM
virtualbox --help
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (4.18.0-15-generic) or it failed to
load. Please recompile the kernel module and install it by

sudo /sbin/vboxconfig

You will not be able to start VMs until this problem is fixed.
/usr/lib/virtualbox/VirtualBox: error while loading shared libraries:
libQt5OpenGL.so.5: cannot open shared object file: No such file or directory
Dhivyashree M5:39 PM
ok
Sunil Munusamy5:39 PM
getting this error
John Sundarraj5:39 PM
sudo /sbin/vboxconfig
Sunil Munusamy5:39 PM
ok
Balakrishna G5:39 PM
bala@personal-laptop:/opt/kickstart-swarm$ virtualbox --help
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (5.4.0-70-generic) or it failed to
load. Please recompile the kernel module and install it by

sudo /sbin/vboxconfig

You will not be able to start VMs until this problem is fixed.
/usr/lib/virtualbox/VirtualBox: error while loading shared libraries:
libQt5PrintSupport.so.5: cannot open shar
Dhivyashree M5:40 PM
sudo /sbin/vboxconfig
sudo: /sbin/vboxconfig: command not found
kishore v5:40 PM
even im getting same error : /sbin/vboxconfig: command not found
Pethu Raj5:41 PM
virtualbox-6.1_6.1.2-135662~Ubuntu~bionic_amd64.deb - download in progress (with
ubuntu host)
Kolli Santhosh5:41 PM
Thanks Azharudeen AshrafAli
Sathiyaraj Sridhar5:43 PM
Disable Secure Boot & Enable Virtualization
Please make sure that you disable Secure Boot from your machine BIOS setup. If
there is Virtualization Technologies option available on BIOS settings, then please
enable it to avoid unwanted issues when building VM's. Entering the BIOS setup menu
depends upon your machine model, so please search the internet to find ways to
configure these on your machine BIOS. This has to be done in all sort of host
machines whether Linux or Windows.
Dhivyashree M5:45 PM
@Sathya - Could you please help ow it has to be done in ubuntu OS
Sathiyaraj Sridhar5:46 PM
Poweroff -> Go to BIOS setup (F2) -> Disable Secure Boot & Enable Virtualization.
Mathivanan5:47 PM
mathivanan@linux-pc:~$ virtualbox --help
Oracle VM VirtualBox VM Selector v6.1.2
(C) 2005-2020 Oracle Corporation
All rights reserved.

No special options.

If you are looking for --startvm and related options, you need to use VirtualBoxVM.
mathivanan@linux-pc:~$ vagrant --version
Vagrant 2.2.7
sudha TM5:48 PM
$ vagrant --version

Vagrant 2.2.9

is this the expected output?


Mathivanan5:48 PM
yes
Sadhana D5:48 PM
vagrant --version
Vagrant 2.2.10
Manimegalai Devaraj5:49 PM
$vagrant --version
Vagrant 2.2.9
Saju Krishnan5:49 PM
SONY@SONY-VAIO MINGW64 ~
$ git clone https://github.com/sloopstash/kickstart-swarm.git /opt/kickstart-swarm
Cloning into 'C:/Program Files/Git/opt/kickstart-swarm'...
remote: Enumerating objects: 53, done.
remote: Counting objects: 100% (53/53), done.
remote: Compressing objects: 100% (31/31), done.
remote: Total 53 (delta 17), reused 49 (delta 13), pack-reused 0
Unpacking objects: 100% (53/53), 25.84 KiB | 9.00 KiB/s, done.
$ vagrant --version
Vagrant 2.2.9
Saju Krishnan5:51 PM
ok
sure
Prakash K5:52 PM
Vagrant 2.2.9
Arunkumar Ponnurangam5:53 PM
Vagrant 2.2.14
Azharudeen AshrafAli5:53 PM
$ vagrant --version
Vagrant 2.2.9
Sathishkumar M5:53 PM
Get:15 http://in.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libc6-dev
amd64 2.27-3ubuntu1.4 [2,585 kB]

Err:14 http://security.ubuntu.com/ubuntu bionic-updates/main amd64 linux-libc-dev


amd64 4.15.0-139.143

404 Not Found [IP: 2403:8940:3:1::f 80]


Get:16 http://in.archive.ubuntu.com/ubuntu bionic/main amd64 make amd64 4.1-
9.1ubuntu1 [154 kB]
Mathivanan5:53 PM
mathivanan@linux-pc:~$ vagrant --version
Vagrant 2.2.7
Singaravel M5:53 PM

v6.1.18
Vagrant 2.2.14
Rajkumar R T5:54 PM
Vagrant 2.2.14
lokesh kannan5:54 PM

Vagrant 2.2.9
$ virtualbox --help
bash: virtualbox: command not found
John Sundarraj5:54 PM
Put virtualbox version also
Vishal S5:54 PM
Vagrant 2.2.9
Mathivanan5:54 PM
virtualbox --help v6.1.2
Prasanna5:54 PM
virtual box downloading still , i use linux host
BANDITA GARNAIK5:54 PM
vagrant 2.2.9
santhosh mani5:54 PM
Vagrant 2.2.9
Sadhana D5:54 PM
$ virtualbox --help
bash: virtualbox: command not found
vamsi krishna5:54 PM
Vagrant 2.2.9
sathyaraj k5:54 PM
Vagrant 2.2.7
Oracle VM VirtualBox VM Selector v6.1.2
archana sekar5:54 PM
Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a
solution).
sudha TM5:55 PM
only vagrant version am getting. For virtual box getting like below : $ virtualbox
--help
bash: virtualbox: command not found
Jaicy Vignesh5:55 PM
bash: virtualbox: command not found
Sathishkumar M5:55 PM
Hi john. i am getting error in below command
sudo apt install gcc make perl
Saju Krishnan5:55 PM
virtualbox --help
bash: virtualbox: command not found
Karthik Sivashankar5:55 PM
yes
Tajdeen Abdulla5:55 PM
Vagrant 2.2.14
Karthik Sivashankar5:55 PM
i am getting
Vagrant 2.2.9
Sadhana D5:56 PM
$ vagrant --version
Vagrant 2.2.10

Devendra kumar5:56 PM
Vagrant 2.2.9
Jaicy Vignesh5:56 PM
$ apt install gcc make perl
bash: apt: command not found
Kalaiarasan Kirubanandam5:56 PM
Vagrant 2.2.9
vaithiy anathan5:56 PM
Vagrant 2.2.9 (Using Windows as host)
Kavi Arasu5:56 PM
Vagrant 2.2.7
v
John Sundarraj5:57 PM
SHUT DOWN ALL VMS - BOTH WINDOWS and UBUNTU HOST users
Kavi Arasu5:57 PM
Oracle VM VirtualBox VM Selector v6.1.2
kishore v5:57 PM
John im still facing this issue for virtual box
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (5.4.0-70-generic) or it failed to
load. Please recompile the kernel module and install it by

sudo /sbin/vboxconfig
Raghavendran Annamalai5:58 PM
Vagrant 2.2.7
Oracle VM VirtualBox VM Selector v6.1.2
Sunil Munusamy6:00 PM
same for me John
ganesh6:00 PM
ganesh@ganesh-ThinkPad-T440p:~$ sudo apt install
./Downloads/vagrant_2.2.7_x86_64.deb
Reading package lists... Error!
E: Sub-process Popen returned an error code (2)
E: Encountered a section with no Package: header
E: Problem with MergeList /home/ganesh/Downloads/vagrant_2.2.7_x86_64.deb
E: The package lists or status file could not be parsed or opened.
ganesh@ganesh-ThinkPad-T440p:~$ clear

ganesh@ganesh-ThinkPad-T440p:~$
ok john
Sadhana D6:03 PM
please share your screen
Vishal S6:03 PM
john share your screen
kishore v6:04 PM
It has installed now,Oracle VM VirtualBox VM Selector v6.1.2
John Sundarraj6:04 PM
cd /opt/kickstart-swarm
Prasanna6:07 PM
linux host user :
virtualbox --help
Oracle VM VirtualBox VM Selector v6.1.2
vagrant --version
Vagrant 2.2.7
Singaravel M6:08 PM
The checksum of the downloaded box did not match the expected
value
Sadhana D6:09 PM
both are running in same time
Mathivanan6:12 PM
After running the command for the third time it got completed -- linux host user
Rajkumar R T6:14 PM
completed - Windows, able to see two new vm's in virtual box
Suresh Alex A6:15 PM
John, for Linux where to start the installation
Ubunut
ubuntu*
John Sundarraj6:15 PM
Boot Sarm nodes
Suresh Alex A6:15 PM
ok thanks
John Sundarraj6:15 PM
*Swarm
kishore v6:18 PM
Hi John, error is thrown on worker swarm
The checksum of the downloaded box did not match the expected
value. Please verify that you have the proper URL setup and that
you're downloading the proper file.
Muthu Kumaran6:18 PM
Hi John.. I am able to see the virtual box version after booting from bios
whats the next
ok thanks
You6:19 PM
i could not see new vm in vm box in windows
command successful
Aanchal Mathew6:20 PM
@Sathya : should we run script/vagrant/sloopstash-swm-wkr/up in opt /kickstart
swarm directory
Sathiyaraj Sridhar6:20 PM
Yes
Aanchal Mathew6:20 PM
ok
Dhivyashree M6:21 PM
virtualbox --help
Oracle VM VirtualBox VM Selector v6.1.2
(C) 2005-2020 Oracle Corporation
All rights reserved.

No special options.

If you are looking for --startvm and related options, you need to use VirtualBoxVM.
sudha TM6:21 PM
i can see sloopstash-swm-mgr: Complete! and
sloopstash-swm-wkr: Complete!
Dhivyashree M6:21 PM
This is correct?
Arunkumar Ponnurangam6:21 PM
Windows machine: Both swarm master and worker installation failed :
The checksum of the downloaded box did not match the expected
(Vagrant::Errors::BoxChecksumMismatch)
Dhivyashree M6:22 PM
@Sathya - Is this fine? What should I do next
Kavi Arasu6:22 PM
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

umount /mnt

Stdout from the command:

Stderr from the command:

umount: /mnt: not mounted


Sathiyaraj Sridhar6:22 PM
@Dhivyashreee: That is fine.
Suresh Alex A6:22 PM
sudo script/vagrant/sloopstash-swm-mgr/up
script/vagrant/sloopstash-swm-mgr/up: line 3: vagrant: command not found
Sathiyaraj Sridhar6:23 PM
@Arunkumar Ponnurangam: Please share your screeen afther this.
@Suresh Alex A: you have to install vagrant .
Sathiyaraj Sridhar6:24 PM
Please check the preface note.
lokesh kannan6:25 PM
both vm got installed and running @john
parallel running gets error.
Kavi Arasu6:25 PM
Complete!
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: mirror.vanehost.com
* extras: mirror.vanehost.com
* updates: mirror.vanehost.com
No package kernel-devel-3.10.0-1127.el7.x86_64 available.
Error: Nothing to do
Unmounting Virtualbox Guest Additions ISO from: /mnt
umount: /mnt: not mounted
==> sloopstash-swm-mgr: Checking for guest additions in VM...
sloopstash-swm-mgr: No guest additions were detected on the base box for this
VM! Guest
sloopstas
Is this fine?
John Sundarraj6:27 PM
sudo vagrant plugin install vagrant-vbguest
@kavi u havent installed this
please install
Badrinarayanan Rajagopalan6:27 PM
Successfully installed both Manager and Worked node.

Able to SSH successfully to both.

Mine is Direct Linux Host


Kavi Arasu6:27 PM
okay john
Aanchal Mathew6:28 PM
sloopstash-swm-mgr: Complete!
sloopstash-swm-wkr: Complete!
vamsi krishna6:28 PM
both worker and manager got installed successful on my windows machine.
Muthu Kumaran6:29 PM
==> sloopstash-swm-mgr: Booting VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "fd484f4c-5df0-4fa7-9459-69baf61ca80e", "--type", "headless"]

Stderr: VBoxManage: error: VT-x is not available (VERR_VMX_NO_VMX)


VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component
ConsoleWrap, interface IConsole

Jaicy Vignesh6:29 PM
sloopstash-swm-mgr: Complete!
John Sundarraj6:29 PM
@jaicy then build wkr
Devendra kumar6:30 PM
Installed both VM on my windows machine
Jaicy Vignesh6:30 PM
yes ji..going on
Mathivanan6:30 PM
completed both mgr and wkr swarm nodes... ssh also successfully established
Sathishkumar M6:30 PM
Hi sathya. i am using ubuntu host. facing issue in sudo apt install gcc make perl
command itself.
After this operation, 75.5 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Ign:1 http://in.archive.ubuntu.com/ubuntu bionic-updates/main amd64 linux-libc-dev
amd64 4.15.0-139.143
Err:1 http://security.ubuntu.com/ubuntu bionic-updates/main amd64 linux-libc-dev
amd64 4.15.0-139.143
404 Not Found [IP: 2403:8940:3:1::f 80]
E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/l/linux/linux-libc-
dev_4.15.0-139.143_amd64.deb 404 Not Found [IP: 2403:8940:3:1::f
santhosh mani6:31 PM
Manager and worker is running in virtual box in windows machine
Jaicy Vignesh6:32 PM
sloopstash-swm-wkr: Complete!
Sathiyaraj Sridhar6:32 PM
@Sathishkuma: Can you able run sudo apt update?
sudo script/vagrant/sloopstash-swm-mgr/halt
sudo script/vagrant/sloopstash-swm-wkr/halt
You6:33 PM
still showing pause
Sathiyaraj Sridhar6:33 PM
For windows user, don't use sudo.
John Sundarraj6:34 PM
sudo script/vagrant/sloopstash-swm-mgr/halt
sudo script/vagrant/sloopstash-swm-wkr/halt
Aiswarriya Kannan6:34 PM
running fine
You6:34 PM
$ script/vagrant/sloopstash-swm-mgr/destroy
An action 'destroy' was attempted on the machine 'sloopstash-swm-mgr',
but another process is already executing an action on the machine.
Vagrant locks each machine for access by only one process at a time.
Please wait until the other Vagrant process finishes modifying this
machine, then try again.

If you believe this message is in error, please check the process


listing for any "ruby" or "vagrant" processes and kill them. Then
Mathivanan6:34 PM
VM's powered off
RamSenthil Kumar6:35 PM
yes i am
Rajkumar R T6:35 PM
yes
Arunkumar Nagaraj6:35 PM
yes
Bharath Sathyan6:35 PM
Yes
BANDITA GARNAIK6:35 PM
yes
harvind kumar6:35 PM
yes
lokesh kannan6:35 PM
yes
Devendra kumar6:35 PM
yes
Aanchal Mathew6:35 PM
done
Nagaraju Pasam6:35 PM
yes
Raghavendran Annamalai6:35 PM
inprogress
Muthu Kumaran6:35 PM
No
Vishal S6:35 PM
yes
Ganesan Dhandapani6:35 PM
Yes able to see it.
Aiswarriya Kannan6:35 PM
yes
Sathiyaraj Sridhar6:35 PM
@debi: Run destroy command again.
Kalaiarasan Kirubanandam6:35 PM
still now, installing...
santhosh mani6:35 PM
powerd off..
Muthu Kumaran6:35 PM
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "fd484f4c-5df0-4fa7-9459-69baf61ca80e", "--type", "headless"]

Stderr: VBoxManage: error: VT-x is not available (VERR_VMX_NO_VMX)


VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component
ConsoleWrap, interface IConsole

Dhivyashree M6:35 PM
received this error while building vms
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
umount /mnt

Stdout from the command:

Stderr from the command:

umount: /mnt: not mounted


Jaicy Vignesh6:36 PM
done
its powered off
Muthu Kumaran6:36 PM
i enabled
Manimegalai Devaraj6:36 PM
able to halt
Dhivyashree M6:36 PM
however ssh is working
dhivyashree@dhivyashree-desktop:/opt/kickstart-swarm$ sudo
script/vagrant/sloopstash-swm-mgr/ssh
[vagrant@localhost ~]$ exit
logout
Connection to 127.0.0.1 closed.
Muthu Kumaran6:36 PM
Yes John.. I enabled
Dhivyashree M6:36 PM
This is fine?
Muthu Kumaran6:36 PM
my mike has problem
yes i did
Sathiyaraj Sridhar6:36 PM
@Muthukumarn -> Disable secure boot and enable Virtualization Technology (VT)
Muthu Kumaran6:36 PM
yes
John Sundarraj6:37 PM
script/vagrant/sloopstash-swm-mgr/destroy
Sunil Munusamy6:37 PM
same error for me like Muthu
Muthu Kumaran6:37 PM
Sure
John Sundarraj6:37 PM
sudo script/vagrant/sloopstash-swm-wkr/destroy
vaithiy anathan6:38 PM
I succesfully build both server ,but i am using halt command getting the below
error message
Vagrant failed to initialize at a very early stage:

The version of powershell currently installed on this host is less than


the required minimum version. Please upgrade the installed version of
powershell to the minimum required version and run the command again.
Kalaiarasan Kirubanandam6:40 PM
getting an error ==> sloopstash-swm-mgr: VM not created. Moving on...
Jaicy Vignesh6:41 PM
$ script/vagrant/sloopstash-swm-wkr/ssh
[vagrant@sloopstash-swm-wkr ~]$ exit
logout
Connection to 127.0.0.1 closed.
$ script/vagrant/sloopstash-swm-mgr/ssh
[vagrant@sloopstash-swm-mgr ~]$ exit
logout
Connection to 127.0.0.1 closed.
Its done
?
Sathiyaraj Sridhar6:42 PM
@Jaicy: yes, Its done.
Jaicy Vignesh6:42 PM
ok sathya
thanks
Muthu Kumaran6:42 PM
i halted and ran up..
muthu@muthu:/opt/kickstart-swarm$ sudo script/vagrant/sloopstash-swm-mgr/up
Bringing machine 'sloopstash-swm-mgr' up with 'virtualbox' provider...
==> sloopstash-swm-mgr: Importing base box 'centos/7'...
==> sloopstash-swm-mgr: Matching MAC address for NAT networking...
==> sloopstash-swm-mgr: Setting the name of the VM: sloopstash-swm-mgr
==> sloopstash-swm-mgr: Clearing any previously set network interfaces...
==> sloopstash-swm-mgr: Preparing network interfaces based on configuration...
s
same error
==> sloopstash-swm-mgr: Booting VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "8b7ecdc1-b9a5-479b-a2f0-d4a10f1a1fac", "--type", "headless"]

Stderr: VBoxManage: error: VT-x is not available (VERR_VMX_NO_VMX)


VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component
ConsoleWrap, interface IConsole
Sathiyaraj Sridhar6:44 PM
@Muthu Kumaran: What is your system configuration.
Did you enable virtualization tecchnology on the BIOS setup.
vamsi krishna6:44 PM
able to up and halted.
John Sundarraj6:44 PM
sudo script/vagrant/sloopstash-swm-mgr/halt
sudo script/vagrant/sloopstash-swm-wkr/halt
Muthu Kumaran6:45 PM
@sathyaraj.. Yes i did that
vinitha Ragamsetty6:45 PM
im able to run up and halt
Muthu Kumaran6:45 PM
virtualization tecnology is enabled
You6:45 PM
both vm build successful
Muthu Kumaran6:45 PM
Ubuntu
i will capture the screen and paste
thanks
Sathiyaraj Sridhar6:46 PM
ok
Suresh Alex A6:46 PM
(base) suresh@suresh-HP-Z2-Tower-G4-Workstation:~$ sudo apt install
~/Downloads/virtualbox-6.1_6.1.2-135662~Ubuntu~bionic_amd64.deb
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'virtualbox-6.1' instead of '/home/suresh/Downloads/virtualbox-
6.1_6.1.2-135662~Ubuntu~bionic_amd64.deb'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that
can I go to the next version ?
Sathiyaraj Sridhar6:48 PM
@Suresh Alex: please share your screen after sathiyaraj is completed.
Suresh Alex A6:48 PM
sure
Suresh Alex A6:49 PM
sure
Suresh Alex A6:50 PM
host machine
Sathiyaraj Sridhar6:52 PM
sudo apt install -f
@Suresh Alaex: run sudo apt install -f
Sathiyaraj Sridhar6:56 PM
@suresh alex: sudo apt-get install libvpx5
Suresh Alex A6:58 PM
sure sathiyaraj
having issue in mic so little bit delay , sorry about it
Sathiyaraj Sridhar7:01 PM
Thats fine.
Sathiyaraj Sridhar7:02 PM
sudo vagrant plugin install vagrant-vbguest
Shivakanth Chandrasekaran7:04 PM
Both swam mgr and swarm wkr completed in window git bash
may i know next what i have to do
Prasanna7:05 PM
linux user, getting error in building worker vm, mgr sucessful
You7:06 PM
how to move out from ssh
Tajdeen Abdulla7:07 PM
John: I am getting below error

The checksum of the downloaded box did not match the expected
value. Please verify that you have the proper URL setup and that
you're downloading the proper file.
Sadhana D7:08 PM
both mgr and wkr are able to up/halt/up
Sathiyaraj Sridhar7:10 PM
@Dharmaraj: up and halt
Prasanna7:11 PM
The virtual machine 'sloopstash-swm-wkr' has terminated unexpectedly during startup
with exit code 1 (0x1)
John Sundarraj7:13 PM
I'll comeback in 10 mins..then we'll start Swarm architecture
vamsi krishna7:16 PM
Hi Sathya... disabling secure boot is not mandatory for windows machine right ?
Pethu Raj7:16 PM
sudo vagrant plugin install vagrant-vbguest
Sathiyaraj Sridhar7:22 PM
@Vamsi: Windows users already done .
Sathiyaraj Sridhar7:24 PM
Those who built swarm manager and worker VM, halt that VM properly by run following
commands.
$ sudo script/vagrant/sloopstash-swm-mgr/halt
$ sudo script/vagrant/sloopstash-swm-wkr/halt
Azharudeen AshrafAli7:26 PM
load balancing
Kalaiarasan Kirubanandam7:52 PM
john voice is breaking..
are you facing the same issue?
Dhivyashree M7:53 PM
its good .. please chck your side
vaithiy anathan7:53 PM
no kalai
Kalaiarasan Kirubanandam7:53 PM
thanks...
Sathiyaraj Sridhar7:55 PM
# 1 Tab
$ cd /opt/kickstart-swarm
$ script/vagrant/sloopstash-swm-mgr/up
$ script/vagrant/sloopstash-swm-mgr/ssh

# 2 Tab
$ cd /opt/kickstart-swarm
$ script/vagrant/sloopstash-swm-wkr/up
$ script/vagrant/sloopstash-swm-wkr/ssh
Singaravel M7:57 PM
LC_CTYPE: cannot change locale (UTF-8): No such file or directory
Sathiyaraj Sridhar7:57 PM
cat /etc/os-release
John Sundarraj7:57 PM
cat /etc/os-release
sudha TM7:58 PM
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

Jaicy Vignesh7:58 PM
yes
vamsi krishna7:58 PM
yes
BANDITA GARNAIK7:58 PM
yes
Devendra kumar7:58 PM
yes
RamSenthil Kumar7:58 PM
yes
Raghavendran Annamalai7:58 PM
yes
Kalaiarasan Kirubanandam7:58 PM
yes
Singaravel M7:58 PM
yes
santhosh mani7:58 PM
yes.
Sunil Munusamy7:58 PM
yes
Arunkumar Nagaraj7:58 PM
yes
You7:58 PM
yes
Shivakanth Chandrasekaran7:58 PM
yes
Mathivanan7:58 PM
yes
Saju Krishnan7:59 PM
Server Up is taking time for me
Raghavendran Annamalai7:59 PM
@jhon i a, seeing same as both worked and manager [vagrant@localhost ~]$ cat
/etc/os-release
**am
Sadhana D8:02 PM
yes
John Sundarraj8:04 PM
sudo yum install yum-utils device-mapper-persistent-data lvm2
You8:04 PM
need to install in manager or worker
Sathiyaraj Sridhar8:05 PM
@Debi: both node
Sadhana D8:05 PM
done in both
You8:05 PM
[vagrant@sloopstash-swm-wkr ~]$ yum install yum-utils device-mapper-persistent-data
lvm2
Loaded plugins: fastestmirror
You need to be root to perform this command.
Sathiyaraj Sridhar8:05 PM
sudo yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-
ce.repo
Sadhana D8:06 PM
done in both
Raghavendran Annamalai8:06 PM
done
Sathiyaraj Sridhar8:07 PM
sudo yum install docker-ce docker-ce-cli containerd.io
@Harvind: Turn off camera
docker --version
lokesh kannan8:08 PM
do we need to run in git bash of windows?
Mathivanan8:08 PM
docker version 20.10.5, build 55c4c88
lokesh kannan8:08 PM
@sathiya
sudha TM8:08 PM
i have run the utils command by switching to "sudo su -", will this cause any
issue?
Sathiyaraj Sridhar8:09 PM
@lokesh: ok
vamsi krishna8:09 PM
Docker version 20.10.5, build 55c4c88
Vishal S8:09 PM
Docker version 20.10.5, build 55c4c88
Sathiyaraj Sridhar8:09 PM
@Sudha: Don't need to switch as root user.
Saju Krishnan8:09 PM
yes
Jaicy Vignesh8:10 PM
[vagrant@sloopstash-swm-wkr ~]$ docker --version
Docker version 20.10.5, build 55c4c88
BANDITA GARNAIK8:10 PM
yes
Saju Krishnan8:10 PM
[vagrant@sloopstash-swm-mgr ~]$ docker --version
Docker version 20.10.5, build 55c4c88
RamSenthil Kumar8:10 PM
Manager node completed
Rajkumar R T8:10 PM
yes
harvind kumar8:10 PM
yes
Arunkumar Nagaraj8:10 PM
yes
vamsi krishna8:10 PM
yes
RamSenthil Kumar8:10 PM
worker node in progress
Raghavendran Annamalai8:10 PM
yes
Karthik Sivashankar8:10 PM
Docker version 20.10.5, build 55c4c88
Saju Krishnan8:10 PM
[vagrant@sloopstash-swm-wkr ~]$ docker --version
Docker version 20.10.5, build 55c4c88
[vagrant@sloopstash-swm-wkr ~]$
Arunkumar Ponnurangam8:10 PM
yes, done. on both nodes
Saju Krishnan8:10 PM
ok ji
John Sundarraj8:10 PM
Docker version 20.10.5, build 55c4c88
Sathiyaraj Sridhar8:11 PM
sudo mkdir /etc/docker
sudo vim /etc/docker/daemon.json
{
"log-driver": "syslog",
"storage-driver": "overlay2"
}
Sathiyaraj Sridhar8:14 PM
sudo systemctl restart docker.service
RamSenthil Kumar8:15 PM
Completed in both nodes and docker running fine in both
Rajkumar R T8:15 PM
yes
Azharudeen AshrafAli8:15 PM
s
vamsi krishna8:15 PM
done
Sathiyaraj Sridhar8:15 PM
sudo systemctl enable docker.service
Saju Krishnan8:16 PM
yes done
harvind kumar8:16 PM
yes
BANDITA GARNAIK8:16 PM
yes
RamSenthil Kumar8:16 PM
yes done
Jaicy Vignesh8:16 PM
In progress with mgr
Swati Anpat8:16 PM
yes
You8:16 PM
completed
Kalaiarasan Kirubanandam8:16 PM
No.. system is struck...
Aanchal Mathew8:16 PM
done
Jaicy Vignesh8:17 PM
yes John
sathyaraj k8:17 PM
Yes
Rajkumar R T8:17 PM
yes
vamsi krishna8:17 PM
yes
BANDITA GARNAIK8:17 PM
yes
Mathivanan8:18 PM
yes
Aanchal Mathew8:18 PM
yes
Badrinarayanan Rajagopalan8:18 PM
yes
Sadhana D8:19 PM
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
Sathiyaraj Sridhar8:20 PM
sudo vim /etc/docker/daemon.json
Sathiyaraj Sridhar8:23 PM
ESC , SHIFT+:wq
Sadhana D8:25 PM
completed till enable docker.service
Sathiyaraj Sridhar8:32 PM
ifconfig
Sadhana D8:32 PM
able to see
RamSenthil Kumar8:32 PM
yes able to see
Karthik Sivashankar8:32 PM
yes
Kolli Santhosh8:32 PM
yes
Vishal S8:32 PM
s
Saju Krishnan8:32 PM
yes
Aanchal Mathew8:32 PM
yes
vamsi krishna8:32 PM
yes
Manimegalai Devaraj8:32 PM
yes
BANDITA GARNAIK8:32 PM
yes
Kalaiarasan Kirubanandam8:33 PM
able to see
Aiswarriya Kannan8:35 PM
yes
Sathiyaraj Sridhar8:35 PM
# manager
sudo docker swarm init --advertise-addr 192.168.99.107
sudo netstat -ntlp
RamSenthil Kumar8:37 PM
yes
Rajkumar R T8:37 PM
yes
Saju Krishnan8:37 PM
yes
Arunkumar Ponnurangam8:37 PM
yes
Kolli Santhosh8:37 PM
yes
BANDITA GARNAIK8:37 PM
yes
vamsi krishna8:37 PM
yes
lokesh kannan8:37 PM
s
Azharudeen AshrafAli8:37 PM
s
Sadhana D8:37 PM
yes
BANDITA GARNAIK8:38 PM
yes
Sathiyaraj Sridhar8:38 PM
sudo netstat -ntlp
Vishal S8:38 PM
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker
daemon running?
RamSenthil Kumar8:38 PM
yes running in netstat
Sadhana D8:38 PM
yes
archana sekar8:38 PM
yes
Sathiyaraj Sridhar8:38 PM
@Vishal: Use sudo before command
vamsi krishna8:38 PM
yes
Aanchal Mathew8:38 PM
yes
BANDITA GARNAIK8:38 PM
yes
Saju Krishnan8:38 PM
yes
archana sekar8:38 PM
yes
Azharudeen AshrafAli8:38 PM
s
Kolli Santhosh8:38 PM
yes
Devendra kumar8:38 PM
yes
Vishal S8:41 PM
@sathiyaraj sridhar:used sudo but same error appears
Sathiyaraj Sridhar8:42 PM
sudo docker node ls
archana sekar8:43 PM
yes
Arunkumar Ponnurangam8:43 PM
yes!!
Sadhana D8:43 PM
yes
You8:43 PM
yes
BANDITA GARNAIK8:43 PM
yes
RamSenthil Kumar8:43 PM
yes
vamsi krishna8:43 PM
yes
Aanchal Mathew8:43 PM
yes
Jaicy Vignesh8:43 PM
yes John
sudha TM8:43 PM
yes
Azharudeen AshrafAli8:43 PM
s
You8:43 PM
2377/7946 if possible pls explain again
Azharudeen AshrafAli8:46 PM
@Debi - 2377 - internode communication, node to node communication
7946 - cluster state transfer
Sathiyaraj Sridhar8:47 PM
sudo docker swarm join-token -q worker
Saju Krishnan8:48 PM
yes
vamsi krishna8:48 PM
yes
Jaicy Vignesh8:48 PM
yes
Sadhana D8:48 PM
yes
lokesh kannan8:48 PM
s
Aanchal Mathew8:48 PM
yes
Manimegalai Devaraj8:48 PM
yes
RamSenthil Kumar8:48 PM
yes
harvind kumar8:48 PM
yes
Arunkumar Ponnurangam8:48 PM
yes
BANDITA GARNAIK8:48 PM
yes
Sathiyaraj Sridhar8:51 PM
# Worker node
$ SWARM_WORKER_TOKEN=<TOKEN>
echo $SWARM_WORKER_TOKEN
Sathiyaraj Sridhar8:54 PM
sudo docker swarm join --token $SWARM_WORKER_TOKEN 192.168.99.107:2377
Saju Krishnan8:55 PM
This node joined a swarm as a worker.
vamsi krishna8:55 PM
This node joined a swarm as a worker.
Sadhana D8:55 PM
yes
Azharudeen AshrafAli8:55 PM
s
Devendra kumar8:55 PM
yes
sudha TM8:55 PM
yes
Jaicy Vignesh8:55 PM
s
RamSenthil Kumar8:55 PM
yes i am
Aanchal Mathew8:55 PM
yes
BANDITA GARNAIK8:55 PM
yes
Arunkumar Ponnurangam8:55 PM
yes
Sathiyaraj Sridhar8:56 PM
# Master node
sudo docker node ls
Azharudeen AshrafAli8:56 PM
s
sudha TM8:56 PM
yes
Saju Krishnan8:56 PM
yes
harvind kumar8:56 PM
yes
Jaicy Vignesh8:56 PM
yes
BANDITA GARNAIK8:56 PM
yes
Sadhana D8:56 PM
yes
Devendra kumar8:56 PM
yes
lokesh kannan8:56 PM
YES
vamsi krishna8:57 PM
yes
Saju Krishnan8:57 PM
yes
Kolli Santhosh8:57 PM
yes
Aanchal Mathew8:57 PM
yes
RamSenthil Kumar8:57 PM
yes john done
Sathiyaraj Sridhar8:58 PM
sudo docker image ls
sudo docker container ls
$ sudo script/vagrant/sloopstash-swm-mgr/halt
$ sudo script/vagrant/sloopstash-swm-wkr/halt
RamSenthil Kumar9:00 PM
Thanks for the day John
Jaicy Vignesh9:00 PM
Thank you John and sathyaraj
Kalaiarasan Kirubanandam9:00 PM
I have a doubt...
Arunkumar Ponnurangam9:01 PM
thank you!! John and Sathyaraj
Saju Krishnan9:01 PM
Ok John Thanks..
Aanchal Mathew9:01 PM
Thank You
Dhivyashree M9:01 PM
Thanks John
Karthik Sivashankar9:01 PM
Thanks John
Devendra kumar9:01 PM
Thanks John
Kolli Santhosh9:02 PM
Thanks John and Sathiyaraj
Prakash K9:03 PM
[vagrant@sloopstash-swm-wkr ~]$ sudo script/vagrant/sloopstash-swm-wkr/halt
sudo: script/vagrant/sloopstash-swm-wkr/halt: command not found
You9:03 PM
we joined 2377 why not 7946
Prakash K9:03 PM
halt is not working
santhosh mani9:07 PM
while configuring docker, adding docker repository facing
Could not fetch/save url https://download.docker.com/linux/centos/docker-ce.repo to
file /etc/yum.repos.d/docker-ce.repo: [Errno 14] curl#6 - "Could not resolve host:
download.docker.com; Unknown error"
Kalaiarasan Kirubanandam9:09 PM
John, can I share my screen?
Sathiyaraj Sridhar9:10 PM
@Prakash: first exit from vm and then execute halt command
Tajdeen Abdulla9:18 PM
Thanks John, Sathyaraj..

You might also like