Skip to content

denihhh/NatSysProject

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

51 Commits
 
 
 
 
 
 

Repository files navigation

Net&Sys Assignment: Running Containers for Application Development

Group Name: Kroni IT.

Team Mates:

  1. DANISH HAIKAL BIN MOHAMMAD (2219885)
  2. AHMAD ZULFAHMI BIN ZAINAL (2219235)
  3. MUHAMMAD FARIS BIN ROSLI (2215489)

Rules

  1. You are allowed to have 3 group members.
  2. When you complete the assignment, make sure to submit the repository link of your cloned project. Make sure all the files are as what you aspect in your repository.
  3. Answer all questions in the README.md, in your own repository. Either use the online VSCode, terminal or github to edit. Answers are expected where you see Fill answer here.
  4. Learn how to use markdown. https://www.w3schools.io/file/markdown-introduction/

Forking this project repository

  1. First thing you need in doing this assignment is to have a github account. Make sure to sign up at https://www.github.com

  2. The second thing you need is to fork the Net&Sys Assignment repository in your own github account.

    1. Go to https://github.com/ZainabBashi/NatSysProject and click fork to copy the project into your own repository
    2. Make sure that the new fork is now in your own repository

Questions:

  1. What is the link of the fork Net&Sys Assignment in your repository. (1 mark) https://github.com/denihhh/NatSysProject.git
  2. How many files and folders are in this repository. (1 mark) There is 1 file name README.md and 1 folder name image

Exploring github codespaces

  1. The next thing that we will be doing is exploring codespaces. First of all, read about codespaces https://docs.github.com/en/codespaces/overview#what-is-a-codespace
  2. Then go to the link https://github.com/codespaces and we shall start a new codespace.
  3. Click on New codespace.
  4. Choose your own Net&Sys Assignment repository to start your codespace.

  1. Once you have created you codespace, you will see the following. You might already be familiar with this, since it will look similar to VSCode.

  1. You will see the README file file. One is a preview of how it looks like on the web, and the other is the editing view in markdown language.
  2. Edit the README file. Make sure you have your group details correct, ie, group name and team members along with their matric Numbers.
  3. Once you have finish editing, click File->Save or ctrl-s to save it.
  4. After saving, you will notice an M or U next to your file. You will need to commit any changes, whenever you make changes so that it is uploaded to the github repository.

  1. Click on the source control, hint: its on the left side panel, and it will list down the files that have been modified or updated. Click on commit. It will then ask you "Would you like to stage all your changes and commit them directly?" Just say yes, and a new tab will appear. Type a message to log what you have done, and click on the check mark.

  1. After that, sync the changes to the main repository.
  2. Make sure to commit and sync your files to the main repository, or else, your work will be lost since it is not saved into the main repository when you submit your project.

Questions:

  1. What is default OS used to run the virtual environment for codespaces. (1 mark)

Linux OS virtual environment..

  1. What are the two options of RAM, disk and vcpu configuration you can have in running codespaces . (1 mark)

RAM = 4GB/8GB

DISK = 32GB/64GB

VCPU = 2/4

  1. Why must we commit and sync our current work on source control? (1 mark)

Commit: Saves a snapshot of your code, tracks changes, and documents progress.

Sync: Shares your changes with the team, backs up your work, and keeps everyone updated with the latest version

Exploring the Terminal

  1. Look at the TERMINAL tab. Explore and run commands according to the questions below.
  2. You can include your answers as images, or cut and paste the output here. If you are cutting and pasting your answers, wrap your answers in the codeblock clause in markdown. For example, if i run the command whoami the the output would look like the one below.
@joeynor ➜ /workspaces/OSProject (main) $ whoami 
codespace

Questions:

Look at the TERMINAL tab. Run the following commands and provide the output here.

  1. Run the command pwd . (1 mark)
__/workspaces/NatSysProject__
  1. Run the command cat /etc/passwd . (1 mark)
root:x:0:0:root:/root:/bin/bash
daemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin
bin:x:2:2:bin:/bin:/usr/sbin/nologin
sys:x:3:3:sys:/dev:/usr/sbin/nologin
sync:x:4:65534:sync:/bin:/bin/sync
games:x:5:60:games:/usr/games:/usr/sbin/nologin
man:x:6:12:man:/var/cache/man:/usr/sbin/nologin
lp:x:7:7:lp:/var/spool/lpd:/usr/sbin/nologin
mail:x:8:8:mail:/var/mail:/usr/sbin/nologin
news:x:9:9:news:/var/spool/news:/usr/sbin/nologin
uucp:x:10:10:uucp:/var/spool/uucp:/usr/sbin/nologin
proxy:x:13:13:proxy:/bin:/usr/sbin/nologin
www-data:x:33:33:www-data:/var/www:/usr/sbin/nologin
backup:x:34:34:backup:/var/backups:/usr/sbin/nologin
list:x:38:38:Mailing List Manager:/var/list:/usr/sbin/nologin
irc:x:39:39:ircd:/var/run/ircd:/usr/sbin/nologin
gnats:x:41:41:Gnats Bug-Reporting System (admin):/var/lib/gnats:/usr/sbin/nologin
nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin
_apt:x:100:65534::/nonexistent:/usr/sbin/nologin
systemd-timesync:x:101:101:systemd Time Synchronization,,,:/run/systemd:/usr/sbin/nologin
systemd-network:x:102:103:systemd Network Management,,,:/run/systemd:/usr/sbin/nologin
systemd-resolve:x:103:104:systemd Resolver,,,:/run/systemd:/usr/sbin/nologin
messagebus:x:104:105::/nonexistent:/usr/sbin/nologin
codespace:x:1000:1000::/home/codespace:/bin/bash
sshd:x:105:65534::/run/sshd:/usr/sbin/nologin
  1. Run the command df . (1 mark)
Filesystem     1K-blocks     Used Available Use% Mounted on
overlay         32847680 10407568  20746012  34% /
tmpfs              65536        0     65536   0% /dev
shm                65536        8     65528   1% /dev/shm
/dev/root       30298176 24249232   6032560  81% /vscode
/dev/sdb1       46127956      116  43752264   1% /tmp
/dev/loop3      32847680 10407568  20746012  34% /workspaces
  1. Run the command du . (1 mark)
4       ./.git/branches
8       ./.git/objects/73
8       ./.git/objects/97
4       ./.git/objects/info
12      ./.git/objects/5d
1888    ./.git/objects/pack
1924    ./.git/objects
8       ./.git/logs/refs/heads
12      ./.git/logs/refs/remotes/origin
16      ./.git/logs/refs/remotes
28      ./.git/logs/refs
36      ./.git/logs
68      ./.git/hooks
4       ./.git/lfs/tmp
8       ./.git/lfs
4       ./.git/refs/tags
8       ./.git/refs/heads
12      ./.git/refs/remotes/origin
16      ./.git/refs/remotes
32      ./.git/refs
8       ./.git/info
2116    ./.git
1972    ./images
4116    .
  1. Run the command ls . (1 mark) Fill answer here.
README.md  images
  1. Run the command ls -asl . (1 mark)
total 40
4 drwxrwxrwx+ 4 codespace root  4096 Jun 19 08:47 .
4 drwxr-xrwx+ 5 codespace root  4096 Jun 19 08:47 ..
4 drwxrwxrwx+ 9 codespace root  4096 Jun 19 08:48 .git
24 -rw-rw-rw-  1 codespace root 22656 Jun 19 08:51 README.md
4 drwxrwxrwx+ 2 codespace root  4096 Jun 19 08:47 images
  1. Run the command free -h . (1 mark)
              total        used        free      shared  buff/cache   available
Mem:          7.7Gi       1.3Gi       246Mi        65Mi       6.2Gi       6.0Gi
Swap:            0B          0B          0B
  1. Run the command cat /proc/cpuinfo . (1 mark)
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 25
model           : 1
model name      : AMD EPYC 7763 64-Core Processor
stepping        : 1
microcode       : 0xffffffff
cpu MHz         : 2592.381
cache size      : 512 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 1
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl tsc_reliable nonstop_t
sc cpuid extd_apicid aperfmperf pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm cmp_legacy svm cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw topoext invpcid_single vmmcall fsgsbase bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves clzero xsaveerptr rdpru arat npt nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold v_vmsave_vmload umip vaes vpclmulqdq rdpid fsrm                                                                                                                                  bugs            : sysret_ss_attrs null_seg spectre_v1 spectre_v2 spec_store_bypass srso
bogomips        : 4890.85
TLB size        : 2560 4K pages
clflush size    : 64
cache_alignment : 64
address sizes   : 48 bits physical, 48 bits virtual
power management:

processor       : 1
vendor_id       : AuthenticAMD
cpu family      : 25
model           : 1
model name      : AMD EPYC 7763 64-Core Processor
stepping        : 1
microcode       : 0xffffffff
cpu MHz         : 2592.652
cache size      : 512 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 1
apicid          : 1
initial apicid  : 1
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl tsc_reliable nonstop_t
sc cpuid extd_apicid aperfmperf pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm cmp_legacy svm cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw topoext invpcid_single vmmcall fsgsbase bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves clzero xsaveerptr rdpru arat npt nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold v_vmsave_vmload umip vaes vpclmulqdq rdpid fsrm                                                                                                                                  bugs            : sysret_ss_attrs null_seg spectre_v1 spectre_v2 spec_store_bypass srso
bogomips        : 4890.85
TLB size        : 2560 4K pages
clflush size    : 64
cache_alignment : 64
address sizes   : 48 bits physical, 48 bits virtual
power management:
  1. Run the command top and type q to quit. (1 mark)
top - 09:10:57 up 26 min,  0 users,  load average: 0.13, 0.16, 0.30
Tasks:  18 total,   1 running,  17 sleeping,   0 stopped,   0 zombie
%Cpu(s):  3.2 us,  3.2 sy,  0.0 ni, 87.1 id,  6.5 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem :   7929.6 total,    250.6 free,   1497.6 used,   6181.4 buff/cache
MiB Swap:      0.0 total,      0.0 free,      0.0 used.   6049.9 avail Mem 

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
   2597 codespa+  20   0   21.6g 394428  55168 S   6.2   4.9   0:42.87 node
      1 codespa+  20   0    1136    640    640 S   0.0   0.0   0:00.04 docker-init
      7 codespa+  20   0    7236   1792   1792 S   0.0   0.0   0:00.01 sleep
     48 root      20   0   12196   3480   2560 S   0.0   0.0   0:00.00 sshd
   1423 codespa+  20   0    2616   1536   1536 S   0.0   0.0   0:00.01 sh
   1464 root      20   0    2616   1408   1408 S   0.0   0.0   0:00.00 sh
   2347 codespa+  20   0    2624   1536   1536 S   0.0   0.0   0:00.00 sh
   2370 codespa+  20   0 1356668 103272  45440 S   0.0   1.3   0:08.13 node
   2479 root      20   0 1983176  87260  52992 S   0.0   1.1   0:00.31 dockerd
   2507 root      20   0 1872564  48220  30592 S   0.0   0.6   0:00.36 containerd
   2706 codespa+  20   0 1240308  52308  41216 S   0.0   0.6   0:00.28 node
   3306 codespa+  20   0 1117012  65112  42240 S   0.0   0.8   0:01.77 node
   3813 codespa+  20   0 1021720  88556  40704 S   0.0   1.1   0:03.13 node
   4295 codespa+  20   0    2616   1536   1536 S   0.0   0.0   0:00.01 sh
   4349 root      20   0    2616   1664   1664 S   0.0   0.0   0:00.00 sh
   4571 codespa+  20   0   16628  11520   3328 S   0.0   0.1   0:00.20 bash
   5319 codespa+  20   0  994784  54008  40064 S   0.0   0.7   0:00.17 node
  14580 codespa+  20   0   10880   3584   3200 R   0.0   0.0   0:00.00 top
  1. Run the command uname -a. (1 mark)
Linux codespaces-0f7712 6.5.0-1021-azure #22~22.04.1-Ubuntu SMP Tue Apr 30 16:08:18 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
  1. What is the available free memory in the system. (1 mark)

    6.0 GB available free memory

  2. What is the available disk space mounted on /workspace. (1 mark)
    20746012 KB

  3. Name the version and hardware architecture of the linux Virtual environment. (1 mark)

No LSB modules are available.

Distributor ID: Ubuntu

Description: Ubuntu 20.04.6 LTS

Release: 20.04

Codename: focal

  1. What is the difference between ls vs ls -asl. (1 mark)

ls: Lists filenames in the directory.

ls -asl: Lists all files (including hidden) with sizes and detailed information (permissions, owner, group, size, and timestamp).

  1. What is the TLB size of the Virtual CPU. (1 mark)

    TLB size : 2560 4K pages

  2. What is the CPU speed of the Virtual CPU. (1 mark)

    Processor 0: cpu MHz : 2592.381

    Processor 1: cpu MHz : 2592.652

    from cat /proc/cpuinfo

  3. What is the top running process that consumes the most CPU cycles. (1 mark)

    Process node with PID 2597 is the top running process that has consumed the most CPU cycles overall (6.2%).

Running your own container instance.

  1. At the terminal, run a linux instance. By typing the following command.
docker pull debian
docker run --detach -it debian
  1. This will run the debian container. To check if the debian container is running, type
@denihhh ➜ /workspaces/NatSysProject (main) $ docker ps -a
CONTAINER ID   IMAGE     COMMAND   CREATED          STATUS          PORTS     NAMES
4f1ac28158f8   debian    "bash"    27 seconds ago   Up 25 seconds             reverent_antonelli
  1. Keep note of the name used by your container, this is usually given random names unless you specify your own name. Now run a bash command on the container. Make sure you use the name of your container instead of the one shown here.
docker exec -i -t reverent_antonelli /bin/bash
  1. Create a file on the container. First you must make sure you are in the bash command prompt of the container. The container is new, and does not have any software other than the debian OS. To create a new file, you will need an editor installed. In the bash shell of the container, run the package manager apt-get to install nano text editor.
root@f65be1987f84:~# apt-get update      

root@f65be1987f84:~# apt-get install nano

root@f65be1987f84:~# cd /root

root@f65be1987f84:~# nano helloworld.txt
  1. Edit your helloworld.txt, create your messsage and save by typing ctrl-X. Once saved, explore using the container to see where the file is located. Then exit the shell, by typing exit.

  2. Stop the container and run docker ps -a, and restart the container again. Is your file in the container still available?

@joeynor ➜ /workspaces/OSProject (main) $ docker stop romantic_jackson

@joeynor ➜ /workspaces/OSProject (main) $ docker ps -a
CONTAINER ID   IMAGE     COMMAND   CREATED          STATUS                        PORTS     NAMES
f65be1987f84   debian    "bash"    19 minutes ago   Exited (137) 18 seconds ago             romantic_jackson

@joeynor ➜ /workspaces/OSProject (main) $ docker restart romantic_jackson
  1. Stop the container and delete the container. What happened to your helloworld.txt?
@joeynor ➜ /workspaces/OSProject (main) $ docker stop romantic_jackson

@joeynor ➜ /workspaces/OSProject (main) $ docker ps -a
CONTAINER ID   IMAGE     COMMAND   CREATED          STATUS                        PORTS     NAMES
f65be1987f84   debian    "bash"    19 minutes ago   Exited (137) 18 seconds ago             romantic_jackson

@joeynor ➜ /workspaces/OSProject (main) $ docker rm romantic_jackson

Questions:

  1. Are files in the container persistent. Why not?. (1 mark)

    No, files in a Docker container are not persistent by default. This is because containers are designed to be ephemeral and stateless. When a container is deleted, its filesystem and any changes made within the container are also removed. To persist data beyond the life of a container, you need to use Docker volumes or bind mounts, which allow data to be stored on the host system and survive container restarts and deletions.

  2. Can we run two, or three instances of debian linux? . (1 mark)

    Yes, you can run multiple instances of Debian Linux containers. Docker allows you to create and run multiple containers from the same image simultaneously. Each container runs in its own isolated environment with its own filesystem, processes, and network interfaces. To run multiple instances, you can simply execute the docker run command multiple times, and Docker will create and manage these instances independently.

Running your own container with persistent storage

  1. In the previous experiment, you might have notice that containers are not persistent. To make storage persistent, you will need to mount them. At the terminal, create a new directory called myroot, and run a instance of debian linux and mount myroot to the container. Find out the exact path of my root, and mount it as the root folder in the debian container.
  2. Create a file in /root on the container, the files should also appear in myroot of your host VM.
@joeynor ➜ /workspaces/OSProject (main) $ mkdir myroot
@joeynor ➜ /workspaces/OSProject (main) $ cd myroot/
@joeynor ➜ /workspaces/OSProject/myroot (main) $ pwd
/workspaces/OSProject/myroot

@joeynor ➜ /workspaces/OSProject/myroot (main) $ docker run --detach -it -v /workspaces/OSProject/myroot:/root debian

Questions:

  1. Check the permission of the files created in myroot, what user and group is the files created in docker container on the host virtual machine? . (2 mark)
    Answer: User: root, Group: root
@denihhh ➜ /workspaces/NatSysProject (main) $ ls -l /workspaces/NatSysProject
total 32
-rw-rw-rw-  1 codespace root 22216 Jun 19 09:17 README.md
drwxrwxrwx+ 2 codespace root  4096 Jun 19 08:47 images
drwxrwxrwx+ 2 root      root  4096 Jun 19 09:37 myroot
  1. Can you change the permission of the files to user codespace. You will need this to be able to commit and get points for this question. (2 mark)
//use sudo and chown
sudo chown -R codespace:codespace myroot

Answer: Yes

@denihhh ➜ /workspaces/NatSysProject (main) $ sudo chown -R codespace:codespace myroot

@denihhh ➜ /workspaces/NatSysProject (main) $ ls -l /workspaces/NatSysProject
total 32
-rw-rw-rw-  1 codespace root      22216 Jun 19 09:17 README.md
drwxrwxrwx+ 2 codespace root       4096 Jun 19 08:47 images
drwxrwxrwx+ 2 codespace codespace  4096 Jun 19 09:37 myroot

You are on your own, create your own static webpage

  1. Create a directory called webpage in your host machine
  2. Inside the directory, create a page index.html, with any content you would like
  3. Then, run the apache webserver and mount the webpage directory to it. Hint:
## the -p 8080:80 flag points the host port 8080 to the container port 80

docker run --detach -v /workspaces/OSProject/webpage:/usr/local/apache2/htdocs/ -p 8080:80 httpd
  1. If it works, codespace will trigger a port assignment and provide a URL for you to access your webpage like the one below.

  1. You can also see the Port in the PORTS tab, next to the terminal tab.

  2. You can then access your website by adding an index.html towards the end of your url link, like the one below.

Questions:

  1. What is the permission of folder /usr/local/apache/htdocs and what user and group owns the folder? . (2 mark)

    drwxr-xr-x+ 2 root root 4096 Jun 19 11:26 /usr/local/apache2/htdocs

    Owner (root) has full access, while the group (root) and others have read and execute permissions only.

  2. What port is the apache web server running. (1 mark)

    Port 80 inside the Docker container

  3. What port is open for http protocol on the host machine? (1 mark)

    Port 8080 on the host machine is mapped to port 80 inside the Docker container running the Apache web server, allowing access to the web server over HTTP

Create SUB Networks

  1. In docker, you can create your own private networks where you can run multiple services, in this part, we will create two networks, one called bluenet and the other is rednet
  2. Run the docker create network to create you networks like the ones below
## STEP 1:
## Create Networks ##
docker network create bluenet
docker network create rednet`

## STEP 2: (automatically running)
## Create (1) Container in background called "c1" running busybox image ##
docker run -itd --net bluenet --name c1 busybox sh
docker run -itd --net rednet --name c2 busybox sh

Questions:

  1. Describe what is busybox and what is command switch --name is for? . (2 mark)

Busybox: A lightweight Linux distribution that combines many common Unix utilities into a single executable, often used in Docker containers for its minimalistic footprint.

'--name': This command switch in Docker assigns a specific name to a container, allowing it to be referenced by name in other Docker commands instead of by its container ID.

  1. Explore the network using the command docker network ls, show the output of your terminal. (1 mark)
@denihhh ➜ /workspaces/NatSysProject/webpage (main) $ docker network ls
NETWORK ID     NAME      DRIVER    SCOPE
6d516f3e62f5   bluenet   bridge    local
2da0c429038c   bridge    bridge    local
a9def5dee8bb   host      host      local
a7ee13e4053d   none      null      local
dc21aa325a02   rednet    bridge    local
  1. Using docker inspect c1 and docker inspect c2 inscpect the two network. What is the gateway of bluenet and rednet.? (1 mark)

C1:

"Gateway": "172.18.0.1",

C2:

"Gateway": "172.19.0.1",
  1. What is the network address for the running container c1 and c2.

C1:

"IPAddress": "172.18.0.2",

C2:

"IPAddress": "172.19.0.2",
  1. Using the command docker exec c1 ping c2, which basically issue a ping from container c1 to c2. Are you able to ping? Show your output . (1 mark)

Answer: No, cannot ping. Output:

@denihhh ➜ /workspaces/NatSysProject/webpage (main) $ docker exec c1 ping c2
ping: bad address 'c2'

Bridging two SUB Networks

  1. Let's try this again by creating a network to bridge the two containers in the two subnetworks
docker network create bridgenet
docker network connect bridgenet c1
docker network connect bridgenet c2
docker exec c1 ping c2

Output:

@denihhh ➜ /workspaces/NatSysProject/webpage (main) $ docker network create bridgenet
5e4da6a38b95b0d0e75153d015289d72e1309c226b276b4e0e3176cc2a330225
@denihhh ➜ /workspaces/NatSysProject/webpage (main) $ docker network connect bridgenet c1
@denihhh ➜ /workspaces/NatSysProject/webpage (main) $ docker network connect bridgenet c2

@denihhh ➜ /workspaces/NatSysProject/webpage (main) $ docker exec c1 ping c2
PING c2 (172.20.0.3): 56 data bytes
64 bytes from 172.20.0.3: seq=0 ttl=64 time=0.076 ms
64 bytes from 172.20.0.3: seq=1 ttl=64 time=0.076 ms
64 bytes from 172.20.0.3: seq=2 ttl=64 time=0.059 ms
64 bytes from 172.20.0.3: seq=3 ttl=64 time=0.070 ms
64 bytes from 172.20.0.3: seq=4 ttl=64 time=0.072 ms
64 bytes from 172.20.0.3: seq=5 ttl=64 time=0.073 ms
64 bytes from 172.20.0.3: seq=6 ttl=64 time=0.071 ms
64 bytes from 172.20.0.3: seq=7 ttl=64 time=0.081 ms

What to submit

  1. Make sure to commit all changes on your source control, and make sure your source control is sync to the repository.
  2. Check your repository link, to see if all the files and answers are included in the repository.
  3. Submit through italeem, by providing the link to your repository.
  4. Due by 30 May, 2024

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors

Languages

  • HTML 100.0%