Task Command April11

John Sundarraj5:18 PM
https://sloopstash.com/blog/how-to-effectively-implement-blue-green-deployment-
model-devops.html
You5:31 PM
sathyaraj pls allow me in linux so i can run the command
Rajkumar R T5:35 PM
yes
karthik s5:35 PM
yes
Sathishkumar M5:35 PM
yes
Jaicy Vignesh5:35 PM
yes
vaithiy anathan5:35 PM
yes
debi5:35 PM
i did manual part
Bharath Sathyan5:35 PM
yes
Shivakanth Chandrasekaran5:35 PM
s
Arunkumar Nagaraj5:35 PM
yes
Tajdeen Abdulla5:35 PM
Yes
Kavi Arasu5:35 PM
yes
debi5:35 PM
yaml is pending
Bandita Garnaik5:35 PM
i have build only docker images
Kalaiarasan Kirubanandam5:35 PM
docker file completed..
yaml is pending..
cd /opt
mv kickstart-docker kickstart-docker-bak
You5:38 PM
permission denied
add sudo
You5:38 PM
ok
Wait debi
You5:39 PM
all my file moved
i can not see kickstart docker
linux
Aanchal Mathew5:43 PM
should we remove docker images if its already created
No need
ok
s
Mani kandan5:46 PM
s
s
yes
yes
Mathivanan5:46 PM
yes
santhosh G5:46 PM
yes
Kolli Santhosh5:46 PM
yes
Arunkumar Ponnurangam5:46 PM
yes
sathyaraj k5:46 PM
yes
Aiswarriya Kannan5:46 PM
yes
Dhivyashree M5:46 PM
yes
lokesh kannan5:46 PM
s
Swati Anpat5:46 PM
yes
harvind kumar5:46 PM
yes
sudha TM5:47 PM
yes
vamsi nalla5:47 PM
yes
Sathiyaraj Sridhar5:51 PM
sudo docker container run -t -i --rm sloopstash/amazonlinux:v1 /bin/bash
yum update -y
Mani kandan5:53 PM
can u pls resend i am not in that time
Azharudeen AshrafAli5:53 PM
yum install -y wget tar gzip vim procps
yum install -y libcurl openssl xz-libs
wget https://fastdl.mongodb.org/linux/mongodb-linux-x86_64-amazon2-4.4.4.tgz
i have some issues in machine john
vamsi nalla5:59 PM
please change to classic editor before copying commands from evernote
tar -zxvf mongodb-linux-x86_64-amazon2-4.4.4.tgz
bash: docker: command not found
cp mongodb-linux-x86_64-amazon2-4.4.4/bin/* /usr/local/bin/
Mani kandan6:00 PM
for me i stopped here itself ...
Sudharshan_Pranav@DESKTOP-V1GLSSN MINGW64 /opt/kickstart-docker (master)

$ docker container run -t -i --rm sloopstash/amazonlinux:v1 /bin/bash
bash: docker: command not found
rm -r mongodb-linux-x86_64-amazon2-4.4.4*
Mathivanan6:03 PM
why removing the extracted directory bro...
mkdir -p /opt/mongodb/conf
$ mkdir -p /opt/mongodb/data
$ mkdir -p /opt/mongodb/log
vim /opt/mongodb/conf/mongod.conf
https://docs.mongodb.com/manual/tutorial/install-mongodb-on-amazon/
vamsi nalla6:12 PM
so both installation instructions and configuration both we need to search
separately right
processManagement:
fork: true
net:
bindIp: 0.0.0.0
port: 27017
storage:
dbPath: /opt/mongodb/datadbPath: /opt/mongodb/data
systemLog:
destination: file
path: "/opt/mongodb/log/mongod.log"
logAppend: true
storage:
journal:
enabled: true
typo in file name mongodb.conf
@vamsi yes
vamsi nalla6:13 PM
okay John
processManagement:
fork: true
net:
bindIp: 0.0.0.0
port: 27017
storage:
dbPath: /opt/mongodb/data
systemLog:
destination: file
logAppend: true
storage:
journal:
enabled: true
vim /opt/mongodb/conf/mongod.conf
mongod -f /opt/mongodb/conf/mongod.conf
how to save ..
Kavi Arasu6:16 PM
yes done
debi6:17 PM
bash-4.2# mongod -f /opt/mongodb/conf/mongod.conf
Error opening config file: Is a directory
try 'mongod --help' for more information
gettin this error
Saju Krishnan6:17 PM
yes done
Prakash K6:17 PM
Prakash K6:19 PM
ps -ef
netstat -ntlp
"/opt/mongodb/conf/mongod.conf" E212: Can't open file for writing
sathyaraj k6:24 PM
Yes
Mathivanan6:24 PM
yws
Prakash K6:24 PM
yes
vamsi nalla6:24 PM
yes
Rajkumar R T6:24 PM
yes
sudha TM6:24 PM
yes
yes
yes
You6:24 PM
yes
yes
Singaravel M6:24 PM
yes
yes
yes
yes
Sunil Munusamy6:24 PM
yes
archana sekar6:24 PM
yes
Devi Narayanan6:24 PM
Yes
Manimegalai Devaraj6:24 PM
yes
Swati Anpat6:24 PM
yes
Ganesan Dhandapani6:24 PM
yes
yes
Gattupalli Balakrishna ePA Team6:24 PM
yes
"/opt/mongodb/conf/mongod.conf" E212: Can't open file for writing
debi6:28 PM
getting error as permission denied
Please watch his creen for now...we'll fix it after that.
sudha TM6:40 PM
yes
Singaravel M6:40 PM
yes
Badrinarayanan Rajagopalan6:40 PM
yes
Rajkumar R T6:40 PM
yes
yes
yes
s
santhosh G6:40 PM
yes..
Mathivanan6:40 PM
clear for me
yes
yes
vamsi nalla6:40 PM
yes
yes
yes
yes
sathyaraj k6:40 PM
yes
yes
Prakash K6:40 PM
yes
Devi Narayanan6:40 PM
Yes
yes
clear
Kavi Arasu6:40 PM
yes
yes
# Docker image to use.
FROM sloopstash/amazonlinux:v1
# Install system packages.
RUN set -x \
&& yum update -y \
&& yum install -y wget tar gzip vim procps \
&& yum install -y libcurl openssl xz-libs
# Download and extract MongoDB.
WORKDIR /tmp
RUN set -x \
&& wget https://fastdl.mongodb.org/linux/mongodb-linux-x86_64-amazon2-4.4.4.tgz
--quiet \
&& tar -zxvf mongodb-linux-x86_64-amazon2-4.4.4.tgz > /dev/null \
&& cp mongodb-linux-x86_64-amazon2-4.4.4/bin/* /usr/local/bin/ \
&& rm -r mongodb-linux-x86_64-amazon2-4.4.4*
# Create necessary directories.
RUN set -x \
&& mkdir -p /opt/mongodb/data \
&& mkdir -p /opt/mongodb/log \
&& mkdir -p /opt/mongodb/conf \
&& history -c
# Set default work directory.

WORKDIR /opt/mongodb
sathyaraj k6:44 PM
@sathiyaraj ... Please share the history output also ..23lines
wait one second
sathyaraj k6:45 PM
ok
Mathivanan6:46 PM
why we are using "--quiet " ...??
Mathivanan6:47 PM
ok bro
Sridhar Rathod6:47 PM
Hi Guys, Please ask questions in english. Thanks.
Muthu Kumaran6:48 PM
do we need multipler run statement can the workdir be set as /tmp and all the
commands in one run
@sridhar yes....will infrom in interbval
please put the commnad
sudo docker image build -t sloopstash/mongodb:v1 -f docker/mongodb.dockerfile
docker/context/mongodb
cd /opt/kickstart-docker
debi6:56 PM
unable to prepare context: path "docker/context/mongodb" not found
somasundaram selvamuthukumar6:56 PM
successfuly built
Mathivanan6:56 PM
done.. image created
done ..
done
Rajkumar R T6:57 PM
done
done
done
Swati Anpat6:57 PM
Done
done
vamsi nalla6:58 PM
i will do after the session... connected outside the VM
[sudo] password for dhivyashree:
Sending build context to Docker daemon 1.583kB
Error response from daemon: dockerfile parse error line 1: unknown instruction: M
done
Sending build context to Docker daemon 1.071kB
Error response from daemon: the Dockerfile (.dockerfile.4680aa19f05e7592420a)
cannot be empty
You6:58 PM
now working
ok
done
Successfully built 8be2d0f73674
Successfully tagged sloopstash/mongodb:v1
karthik s6:58 PM
done
Raghavendran Annamalai6:58 PM
yes built successfullty
Kavi Arasu6:59 PM
done
done
ganesh6:59 PM
done
Running
Rajasekar P N6:59 PM
Done
sathyaraj k7:00 PM
Running
Prakash K7:00 PM
running
Successfully built 75ac6151c9f1
Successfully tagged sloopstash/mongodb:v1
You7:00 PM
it is working
sathyaraj k7:00 PM
history command output pls
shall i?
sathyaraj k7:00 PM
Thanks John
1 yum update -y
2 yum install -y wget tar gzip vim procps
3 yum install -y libcurl openssl xz-libs
4 clear
5 wget https://fastdl.mongodb.org/linux/mongodb-linux-x86_64-amazon2-4.4.4.tgz
6 ls
7 tar -zxvf mongodb-linux-x86_64-amazon2-4.4.4.tgz
8 cp mongodb-linux-x86_64-amazon2-4.4.4/bin/* /usr/local/bin/
9 rm -r mongodb-linux-x86_64-amazon2-4.4.4*
10 mkdir -p /opt/mongodb/data
11 mkdir -p /opt/mongodb/log
12 mkdir -p /opt/mongodb/conf
13
Will be back in 10 mins
14 vim /opt/mongodb/conf/mongod.conf
16 mongod -f /opt/mongodb/conf/mongod.conf
17 ps -ef
18 netstat -ntpl
19 mongo
22 ls /usr/local/bin/
23 history
sudha TM7:01 PM
getting : no build stage in current context
mallikarjun prasad7:04 PM
i think it is /dev/nuill / is missing
sudha TM7:05 PM
the issue was with my docker file. Fixed that. Able to build now, thanks!

RUN set -x \
&& yum update -y \
WORKDIR /tmp
RUN set -x \
--quiet \
RUN set -x \
&& history -c
I was able to create mongodb image..tx
yes done
Azarudeen Ashraf7:12 PM
done

RUN set -x \
&& yum update -y \
WORKDIR /tmp
RUN set -x \
--quiet \
RUN set -x \
&& history -c

Hi John.. my previous questiion was why dont we create with single run like this..
As you mentioned in the previous sessions.. this will reduce the layer ... any
reason for separting it with 3 RUN statement
WORKDIR /tmp
RUN set -x \
&& yum update -y \
&& yum install -y libcurl openssl xz-libs \
--quiet \
&& rm -rf mongodb-linux-x86_64-amazon2-4.4.4* \
&& mkdir -p /op
@Muthukumaran, already answer this many times. Again, if we do like this we end up
with bulky fs layer.
Which affects container boot performance at large scale.
Actually.. i have this confusion like when too use more than one RUN statement in
dockerfile
That we can learn by practising it more.
is that like 4 to 5 commands contained in singler RUN
Okay
I group commands based on functionality...in RUN statement

RUN set -x \
&& yum update -y \
&& yum install -y wget vim procps tar gzip xz
# Download and extract Node.js.
WORKDIR /tmp
RUN set -x \
&& wget https://nodejs.org/dist/v14.16.0/node-v14.16.0-linux-x64.tar.xz --quiet \
&& mkdir -p /usr/local/lib/nodejs \
&& tar -xJvf node-v14.16.0-linux-x64.tar.xz -C /usr/local/lib/nodejs \
&& rm node-v14.16.0-linux-x64.tar.xz
# Install npm packages.
WORKDIR /opt/app
ENV PATH=/usr/local/lib/nodejs/node-v14.16.0-linux-x64/bin:$PATH
ENV NODE_PATH=/opt/app/node_modules
RUN set -x \
&& npm install mongodb@3.6.5 \
&& npm install express@4.17.1
WORKDIR /opt/app
sudo docker image build -t sloopstash/nodejs-app:v1 -f docker/nodejs.dockerfile
docker/context/nodejs
i think create neccessary folder missed
Rajkumar R T7:32 PM
done
Successfully built 79a0f42e5c91
Successfully tagged sloopstash/nodejs-app:v1
/opt/kickstart-docker/docker/nodejs.dockerfile: no such file or directory
@saju create docker file
Kavi Arasu7:35 PM
done
done
done
done
image build for nodejs
vamsi nalla7:35 PM
done
done
done
RUN set -x \
&& yum update -y \
&& yum install -y wget vim procps tar gzip xz
# Download and extract Node.js.
WORKDIR /tmp
RUN set -x \
&& wget https://nodejs.org/dist/v14.16.0/node-v14.16.0-linux-x64.tar.xz --quiet \
&& mkdir -p /usr/local/lib/nodejs \
&& tar -xJvf node-v14.16.0-linux-x64.tar.xz -C /usr/local/lib/nodejs \
&& rm node-v14.16.0-linux-x64.tar.xz
RUN set -x \
&& mkdir /opt/app \
&& mkdir /opt/app/source \
&& mkdir /opt/app/log
# Install npm packages.
WORKDIR /opt/app
ENV PATH=/usr/local/lib/nodejs/node-v14.16.0-linux-x64/bin:$PATH
ENV NODE_PATH=/opt/app/node_modules
RUN set -x \
&& npm install mongodb@3.6.5 \
&& npm install express@4.17.1
WORKDIR /opt/app
sudo docker image build -t sloopstash/nodejs-app:v1 -f docker/nodejs.dockerfile
docker/context/nodejs
unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat
/opt/kickstart-docker/docker/nodejs.dockerfile: no such file or directory
getting an error
debi7:37 PM
+ npm install express@4.17.1
npm WARN saveError ENOENT: no such file or directory, open '/opt/app/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/opt/app/package.json'
npm WARN app No description
npm WARN app No repository field.
npm WARN app No README data
npm WARN app No license field.
ok
done
Successfully built 87db153b2610
Successfully built 1a353111dd98
REPOSITORY TAG IMAGE ID CREATED SIZE
sloopstash/nodejs-app v1 76453e1709b0 3 seconds ago 1.06GB
<none> <none> c13cee74678c 5 minutes ago 1.06GB
sloopstash/mongodb v1 793d78e498da 32 minutes ago 1.16GB
vamsi nalla7:38 PM
created.
Kavi Arasu7:38 PM
yes
done
done
yes
Barani7:39 PM
done
karthik s7:39 PM
done
I have created the nodejs.dockerfile in docker/context
now its running
Mathivanan7:40 PM
mkdir: cannot create directory '/opt/app/source': No such file or directory
@Mathivana please copy the dockerfile content properly
Mathivanan7:42 PM
sorry i forgot to create /op/app dir... now i created
processManagement:
fork: false
net:
bindIp: 0.0.0.0
port: 27017
storage:
systemLog:
destination: file
logAppend: true
storage:
journal:
enabled: true
[program:mongodb]
command=bash -c "mongod -f /opt/mongodb/conf/mongod.conf"
process_name=%(program_name)s
[program:nodejs-app]
command=/bin/bash -c "node init.js"
directory=/opt/app/source
autorestart=false
stdout_logfile=/opt/app/log/stdout.log
stderr_logfile=/opt/app/log/stderr.log
ys
karthik s7:50 PM
Done
yes
yes
s
No
yes
yes
debi7:50 PM
yes
yes
yes
Swati Anpat7:50 PM
yes
Rajkumar R T7:50 PM
yes
yes
Kavi Arasu7:50 PM
yes
sudha TM7:50 PM
yes
vamsi nalla7:50 PM
yes
yes
Mathivanan7:52 PM
yes
I have an issue
You7:56 PM
whatsapp
compose-nodejs-app.yml
compose-proj.yml
there is an existing folder named app under kickstart-docker, do we have to delete
app folder and create new one for init.js file
yes
ok.tq
$ cd /opt/kickstart-docker
$ sudo docker-compose -f docker/compose-proj.yml -p proj-stg up -d
app/init.js
ok john thanks
debi8:19 PM
ERROR: Service 'app' depends on service 'redis' which is undefined.
Kavi Arasu8:19 PM
Creating network "proj-stg_common" with driver "bridge"
ERROR: Pool overlaps with other one on this address space
Rajkumar R T8:19 PM
sudo docker network rm crm-net
udo docker-compose -f docker/compose-proj.yml -p proj-stg up -d
[sudo] password for dhivyashree:
ERROR: .FileNotFoundError: [Errno 2] No such file or directory: './docker/compose-
proj.yml'
do we need to remove volume also
Error: No such network: crm-net
debi8:20 PM
ERROR: Service 'app' depends on service 'redis' which is undefined.
Kavi Arasu8:21 PM
done
Creating volume "proj-stg_mongodb-data" with local driver
Creating volume "proj-stg_mongodb-log" with local driver
Creating proj-stg_mongodb_1 ... done
Creating proj-stg_app_1 ... done
sudo: docker-compose: command not found
vamsi nalla8:22 PM
same error
Install Docker compose
$ cd /opt/kickstart-docker
$ sudo docker-compose -f docker/compose-proj.yml -p proj-stg up -d
karthik s8:23 PM
Working
still showing the same error
Kavi Arasu8:23 PM
i got output
this error i am getting
ganesh8:24 PM
could you please paste the mongodb.ini and nodejs.ini file
Rajkumar R T8:24 PM
done
@ganesh:
[program:mongodb]
autorestart=false
sudo docker network rm crm-dev_common
done...
done
muthu@muthu:/opt/kickstart-docker$ sudo docker-compose -f docker/compose-proj.yml
-p proj-stg up -d
Creating volume "proj-stg_mongodb-data" with local driver
Creating volume "proj-stg_mongodb-log" with local driver
muthu@muthu:/opt/kickstart-docker$ sudo docker container ls
CONTAINER ID IMAGE COMMAND CREATED
STATUS
http://localhost:8080/health
not able to see nodejs container
@sathyaraj am getting error as compose command not found
mv mongodb/mongod.conf mongodb/conf/
@ganesh:
[program:mongodb]
autorestart=false
sudo docker-compose -f docker/compose-proj.yml -p proj-stg down
sudo rm -rf mongodb/conf/mongod.conf
sudo docker-compose am getting here itslef
mv mongodb/mongod.conf mongodb/conf/
sudo chown -R $USER:$USER /opt/kickstart-docker
@Ganesh
processManagement:
fork: false
net:
bindIp: 0.0.0.0
port: 27017
storage:
systemLog:
destination: file
logAppend: true
storage:
journal:
enabled: true
sathyaraj k8:35 PM
RROR: Version in "./docker/compose-proj.yml" is unsupported. You might be seeing
this error because you're using the wrong Compose file version. Either specify a
supported version (e.g "2.2" or "3.3") and place your service definitions under the
`services` key, or omit the `version` key and place your service definitions at the
root of the file to use version 1.
vamsi nalla8:35 PM
installed docker compose... now working
http://localhost:8080/dashboard
http://localhost:8080/account/create?id=1&name=abc
http://localhost:8080/account/create?id=2&name=foo
http://localhost:8080/account/update?id=1&name=sathiyaraj
http://localhost:8080/account/delete?id=2
Prakash K8:36 PM
yes
Rajkumar R T8:36 PM
yes
yes
sudha TM8:36 PM
yes
yes
Arunkumar Nagaraj8:36 PM
yes
karthik s8:36 PM
Clear
Azharudeen AshrafAli8:36 PM
yes
Kavi Arasu8:36 PM
yes
Badrinarayanan Rajagopalan8:36 PM
yes
yes
yes
vamsi nalla8:36 PM
really helpful.. clear
I have done till mongod.conf
yes
Yes
yes
Mathivanan8:37 PM
yes
after that am not clear..
Thulasiraja m8:37 PM
Yes
yes.. I'm really comfortable.. able to identify my gaps...
yes
yes clear john
me
i have issue
yes ckear'
i dont see nodejs container started
Thank you John
thank you john and sathya
Kavi Arasu8:37 PM
Yes. It is very informative. Is it possible to have similar working session for
Swarm?
Thank You
sudo curl -L "https://github.com/docker/compose/releases/download/1.28.5/docker-
compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
sudo chmod +x /usr/local/bin/docker-compose
sudo ln -s /usr/local/bin/docker-compose /usr/bin/docker-compose
sudha TM8:41 PM
when building image file for nodejs getting below error : returned a non-zero code:
4
sudha TM8:42 PM
can you please share the nodejs docker file content again?
vamsi nalla8:43 PM
containers are running but not able to access app
sudo docker container logs proj-stg_app_1
sudo docker logs d3ce916c110b
Error: The directory named as part of the path /opt/app/log/stdout.log does not
exist in section 'program:nodejs-app' (file: '/etc/supervisord.d/nodejs.ini')
For help, use /usr/bin/supervisord -h
okay.. thanks john
You guys can now take nodejs.dockerfile from clipboard.
somasundaram selvamuthukumar8:51 PM
Hi john i am having issue
i am having returned error code 4
while building the nodejs image
kickstart-docker -> app -> init.js
sudo docker network rm crm-dev_common
@Saju: kickstart-docker -> app -> init.js
@Saju: kickstart-docker -> docker -> compose-proj.yml
@Saju: Copy those content from the clipboard.
already app folder is thr do I need to delete it ?
sudo docker container exec -ti proj-stg_app_1 /bin/bash
@Saju: yes
cat /etc/supervisord.d/nodejs.ini
supervisorctl status
tail -f /opt/app/log/stdout.log
tail -f /opt/app/log/stderr.log
tail -f /opt/app/log/stderr.log
cd /opt/app/source
node init.js
@Sathyaraj I have copied from clipboard
vamsi nalla8:59 PM
Hi Jon/Sathya.. both containers are running... not able to access using browser
after that pls
cd /opt/app/source
node init.js
thank you very much john and sathiya it was nice workout session
sathyaraj k9:02 PM
proj-stg_app container , unable to connect
Error response from daemon: Container
688aeadb0a705f6071c4a641a07e6213278aacab79bb3f507e2c3c1330d167a5 is not running
Thanks John and Sathiyaraj
@john.. whats the url to acces the app
[program:mongodb]
ganesh9:04 PM
docker-compose --version
ganesh@ganesh-ThinkPad-T440p:/opt/kickstart-docker$ sudo docker container ls
STATUS PORTS NAMES
4cf052e7ffd1 sloopstash/mongodb:v1 "/usr/bin/supervisor�" 4 minutes ago Up
4 minutes proj-stg_mongodb_1
ganesh@ganesh-ThinkPad-T440p:/opt/kickstart-docker$
autorestart=false
mongodb.ini
mongodb.ini
nodejs.ini
nodejs.ini
ok
Thanks John & Sathyaraj
@sathyaraj: Did you follow every procedures properly?
sathyaraj k9:06 PM
yes
should i share cmd output
Yes please
sathyaraj k9:07 PM
sathya@sathya-lenovo:/opt/kickstart-docker$ sudo docker image ls
[sudo] password for sathya:
REPOSITORY TAG IMAGE ID CREATED SIZE
sloopstash/nodejs-app v1 ca14386c0406 About an hour ago 1.06GB
sloopstash/mongodb v1 80598a3b4368 2 hours ago 1.16GB
sathya@sathya-lenovo:/opt/kickstart-docker$ sudo docker-compose -f docker/compose-
proj.yml -p proj-stg up -d
sathya@sathya-lenovo:/opt/kickstart-docker$
sathya@sathya-lenovo:/opt/kickstart-docker$ sudo docker container ls
CONTAINER ID IMAGE COMMAND
sathyaraj k9:08 PM
app container not showing
sathya@sathya-lenovo:/opt/kickstart-docker$ sudo docker container ls
STATUS PORTS NAMES
b9db01386046 sloopstash/mongodb:v1 "/usr/bin/supervisor�" 8 seconds ago Up
5 seconds proj-stg_mongodb_1
@Sathyraj can you share the container up command
I have created 2 files
under supervisor
sudha TM9:09 PM
ERROR: pull access denied for sloopstash/nodejs-app, repository does not exist or
may require 'docker login': denied: requested access to the resource is denied
ok fine
vamsi nalla9:13 PM
I will recheck everything, incase of issues will check next Saturday morning
session...Thanks lot for the session.
cat /etc/supervisord.d/mongodb.ini

Task Command April11

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Task Command April11

Uploaded by

Copyright:

Available Formats

John Sundarraj5:18 PM

Sudharshan_Pranav@DESKTOP-V1GLSSN MINGW64 /opt/kickstart-docker (master)

# Set default work directory.

# Install system packages.

# Install system packages.

# Set default work directory.

# Install system packages.

You might also like