Prerequisites
- Raspberry Pi 4 Model B with 4G or 8G RAM
- MicroSD card (16GB or larger recommended)
- Ethernet cable connection of RPi to local area network (LAN)
Overview of key steps:
To install EVE-OS onto a Raspberry Pi 4 (RPi4) using Docker and a flashing utility of your choice (you might try Rufus), you will need 1 micro SD card at a minimum (This media will be completely overwritten. Make sure you don’t have any critical data on it) and an Ethernet connection. It’s also helpful to have your RPi connected to an HDMI monitor.
Highlights of steps described below:
- Pull the latest EVE-OS version from fledge’s docker data store.
- Create a microSD card image.
- Flash the image to a microSD card.
- Boot RPi 4 with EVE-OS.
- Onboard RPi4 with EVE-OS to ZEDEDA Cloud.
Install EVE-OS onto RPi 4
Laptop Software Prerequisite 1
Install Docker Desktop and (optionally) log in to your account (or register if new to Docker)
Commands are shown in bold font. The example below was input to a macOS terminal window.
Optionally pull code locally (this will occur automatically with the “run” command below too)
% docker pull lfedge/eve:latest-arm64
6.2.0-arm64: Pulling from lfedge/eve
Digest: sha256:505126d11dd3fe898aa3ebbb0c25ae1d755ea39b36e602a7dc7399f88db72f08
Status: Image is up to date for lfedge/eve:6.2.0-arm64
docker.io/lfedge/eve:6.2.0-arm64
Optional later update
% docker pull lfedge/eve:latest-arm64
latest-arm64: Pulling from lfedge/eve
ab2617240c09: Already exists
424115d47db8: Pull complete
a52c581b49fe: Pull complete
aa4d9fc4fefe: Pull complete
b891f5a78ff9: Pull complete
03eb3401b8ec: Pull complete
8a67acfddaac: Pull complete
4569d64a0fab: Pull complete
Digest: sha256:07028b994a631b60319ce4b142f2412fc609357f3cf44278fb9b1da576b9ddf4
Status: Downloaded newer image for lfedge/eve:latest-arm64
docker.io/lfedge/eve:latest-arm64
Create a microSD card image
% docker run --rm lfedge/eve:latest-arm64 live > live.img
WARNING: The requested image's platform (linux/arm64) does not match the detected host platform (linux/amd64) and no specific platform was requested
/usr/bin/mcopy: File "::/soft_serial" not found
1+0 records in
1+0 records out
1 byte copied, 0.0014029 s, 0.7 kB/s
Unknown (or unrecongnizable) GTP partition table on /tmp/output.img
1+0 records in
1+0 records out
512 bytes copied, 0.0011454 s, 447 kB/s
Warning: Partition table header claims that the size of partition table
entries is 0 bytes, but this program supports only 128-byte entries.
Adjusting accordingly, but partition table may be garbage.
Warning: Partition table header claims that the size of partition table
entries is 0 bytes, but this program supports only 128-byte entries.
Adjusting accordingly, but partition table may be garbage.
Creating new GPT entries in memory.
GPT data structures destroyed! You may now partition the disk using fdisk or
other utilities.
Setting name!
partNum is 0
mkfs.fat 4.1 (2017-01-24)
/tmp/data/tmp.nKjoNw0vDS has 64 heads and 32 sectors per track,
hidden sectors 0x0000;
logical sector size is 512,
using 0xf8 media descriptor, with 73726 sectors;
drive number 0x80;
filesystem has 2 32-bit FATs and 1 sector per cluster.
FAT size is 567 sectors, and provides 72560 clusters.
There are 32 reserved sectors.
Volume ID is 287a5d34, volume label EVE .
35+1 records in
35+1 records out
37747712 bytes (38 MB, 36 MiB) copied, 0.0298294 s, 1.3 GB/s
Setting name!
partNum is 3
1+0 records in
1+0 records out
1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.0022194 s, 472 MB/s
Setting name!
partNum is 1
198+1 records in
198+1 records out
208273408 bytes (208 MB, 199 MiB) copied, 0.498786 s, 418 MB/s
64+0 records in
64+0 records out
64 bytes copied, 0.0016325 s, 39.2 kB/s
No problems found. 26557 free sectors (13.0 MiB) available in 2
segments, the largest of which is 24543 (12.0 MiB) in size.
350+0 records in
350+0 records out
367001600 bytes (367 MB, 350 MiB) copied, 31.7514 s, 11.6 MB/s
0e6779af-591f-460f-8a21-ecea0a825d43
% ls -l
total 1442048
-rw-r--r-- 1 kathy staff 367001600 Jun 15 14:59 live.img
...
Copy (and perhaps save in a file) the unique string (highlighted in yellow above) that was output at the end of the docker run command. You’ll need to enter it into the Serial Number * field when you onboard the RPi4 to your ZEDEDA Cloud account.
Flash an image to a microSD card
Laptop Software Prerequisite 2
Install your chosen flashing utility.
Flash Image
Refer to the official documentation for your chosen flashing utility. Follow those instructions to complete the flashing process.
Boot RPi4 with EVE-OS
Insert the flashed microSD card into the RPi4 and boot, making sure it is connected to the local network over Ethernet.
Onboard RPi4 with EVE-OS to ZEDEDA Cloud
Laptop Software Prerequisite 3
Obtain a trial account for the ZEDEDA Cloud and log into your enterprise using a cookie-compliant browser.
Onboarding Data Prerequisites
Before proceeding, make sure you know the unique Onboarding Key and Serial Number.
Onboarding Key -- if you built the EVE-OS installer image using the Docker command above, then use the ZEDEDA Cloud key 5d0767ee-0547-4569-b530-387e526f8cb9
(or if you build EVE-OS using some other approach you can optionally create your own unique onboarding key that is specific to your custom-built installer image)
Serial Number -- saved result highlighted from “docker run…” command above.
After logging in to ZEDEDA Cloud, select the Edge Nodes page from the left navigation icons (the edge node icon is just under the home icon). In the upper right corner, click the + icon to open the Add Edge Node page.
On the Add Edge Node page, fill in the required fields (e.g., network interfaces) and any other optional details. The example screenshots below can be used as a guide, but be sure to enter your own unique onboarding key and serial number.
Do not forget to select (check) the “Activate Edge Node” checkbox in the lower left of the page before submitting the page using the “Add” button.
After about 5 min, your RPi node should show up and be active (green dot “Online”) on the Edge Nodes summary page. Click its name to browse four pages of details regarding your node. An example of the “Status” page is shown below.
Help
Need help? Head over to the #eve-rpi channel on slack or contact us.