---
# System prepended metadata

title: '5GC+Pi: Daffa Randika Logbook'

---

# 5GC+Pi: Daffa Randika Logbook

## 05/06-05/10
### Plan
- [x] Register: Adinusa account
- [x] Enroll: Linux System Administration
- [x] Learn: Raspberry Pi OS Lite (64-bit)
- [x] Compare: D-Link DGS-1100-08V2 vs Ruijie RG-ES208GC vs Netgear GS308
- [ ] ~~Learn: Running VMs vs containers on Pi~~

### Notes
- Learned how to install raspberry pi OS lite and ssh into it, (Since the Raspberry PI hadn't been given, the OS couldn't be installed)
- Went through adinusa course, had a lab that had the command "nusactl", couldn't figure out how to run that command
![image](https://hackmd.io/_uploads/r1IQW2m70.png)

## 05/13-05/17
### Plan
- [x] Install Raspberry PI OS lite
- [x] Install qemu
- [ ] Create VM using qemu
- [x] Install Proxmox VM

### Results
- Check: KVM virtualization exists on pi
![image](https://hackmd.io/_uploads/B1FH_10Q0.png) 



<!-- ### Notes
* Currently unable to install any virtualization software because the Raspberry PI had no virtualization CPU core -->

## 05/20-05/24
### Plan
- [x] Run: VMs with KVM+QEMU on Pi 4 (acclererated KVM)
- [ ] Check: Proxmox VE web UI +daemon +run VMs :pushpin: 
- [x] Learn: Docker Compose :pushpin: 
### Results
* The command used to make qemu VM:
```shell
virt-install \
	--name ubuntu-vm      \
	--os-variant=ubuntu-lts-latest      \
	--ram 1024      \
	--cdrom=/home/pi/qemu-test/ubuntu-24.04-live-server-amd64.iso  \
	--graphics none


```
* Tough Pi supports KVM acceleration, because the ubuntu-server ISO is in a different architecture, KVM cannot be activated![image](https://hackmd.io/_uploads/SyBXCzZ40.png)
- Managed to run VM using QEMU, but still struggled to install the virtualized OS
![image](https://hackmd.io/_uploads/HkNj5EZEC.png)


### Notes
* Some notes
* Some problems

## 05/27-05/31
### Plan
- [ ] Find: Proxmox VE executables and daemons (web UI) - "proxmox manager"
- [ ] Find: boot device parameter for virtmanager
- [ ] Run: VMs using Proxmox VE
- [x] Learn: Compose vs Swarm +scenario

### Results
* Comparison for Compose vs Swarm

| Feature     | Compose                                       | Swarm                          |
|-------------|-----------------------------------------------|--------------------------------|
| Scope       | Single Docker Host                            | Cluster of Docker Hosts        |
| Use case    | Used mainly for development and testing       | Used mainly in production      |
| Scalability | Limited (because it's only for a single host) | Automatic scaling across hosts |
| Networking  | Uses internal networks to link containers     | Uses a virtual network         |


### Notes
* Some notes
* Some problems