Update deployments/automation/FOG Project.md
All checks were successful
Automatic Documentation Deployment / Sync Docs to https://kb.bunny-lab.io (push) Successful in 6s
All checks were successful
Automatic Documentation Deployment / Sync Docs to https://kb.bunny-lab.io (push) Successful in 6s
This commit is contained in:
@@ -1,37 +0,0 @@
|
||||
## FOG Project Deployment
|
||||
If you want to deploy the FOG Project software in your homelab environment to remotely image devices via PXE boot, follow the instructions below to get through the process.
|
||||
|
||||
!!! info "assumptions"
|
||||
It is assumed that you are deploying FOG Project in Ubuntu Server 26.04 or newer. This documentation does not account for distro-specific issues in other operating systems.
|
||||
|
||||
It is also assumed that you allocate at least 4-cores and 8GB of RAM with at least 256GB of storage for the OS and FOG images.
|
||||
|
||||
!!! warning "Potential Netplan Misconfiguration"
|
||||
I observed an oddity with the networking stack of the Ubuntu Server VM, so just to be safe, run the following command to check that you have both the `nameservers` pointing to your DNS server(s) and `routes` pointing to your default gateway.
|
||||
|
||||
```sh
|
||||
cd /etc/netplan
|
||||
ls
|
||||
<look for the netplan file>
|
||||
nano <netplan file>
|
||||
```
|
||||
|
||||
Ensure it looks something like this, and fix it if any fields are missing:
|
||||
|
||||
```yaml
|
||||
network:
|
||||
ethernets:
|
||||
ens18:
|
||||
addresses:
|
||||
- 192.168.3.9/24
|
||||
routes:
|
||||
- to: default
|
||||
via: 192.168.3.1
|
||||
match:
|
||||
macaddress: bc:24:11:5c:eb:c9
|
||||
nameservers:
|
||||
addresses: [192.168.3.25, 192.168.3.26]
|
||||
search: []
|
||||
set-name: ens18
|
||||
version: 2
|
||||
```
|
||||
Reference in New Issue
Block a user