Headless deployment setup in Raspberry Pi - Step-by-Step Execution

Concept Flow - Headless deployment setup

Prepare SD Card with OS

↓

Enable SSH and Wi-Fi

↓

Insert SD Card into Pi

↓

Power On Pi

↓

Find Pi IP Address

↓

SSH into Pi

↓

Deploy and Run Code

↓

Done

This flow shows the steps to set up a Raspberry Pi without a monitor or keyboard, using network access to control it remotely.

Execution Sample

Raspberry Pi

1. Flash Raspberry Pi OS on SD card
2. Create empty file named 'ssh' in boot partition
3. Add 'wpa_supplicant.conf' with Wi-Fi details
4. Insert SD card and power on Pi
5. SSH into Pi using its IP address

These steps prepare the Raspberry Pi for headless access by enabling SSH and Wi-Fi before first boot.

Execution Table

Step	Action	Result	Notes
1	Flash OS image to SD card	SD card ready with OS	Base system installed
2	Create empty 'ssh' file in boot	SSH enabled on boot	Allows remote login
3	Add 'wpa_supplicant.conf' with Wi-Fi info	Pi connects to Wi-Fi on boot	Network ready
4	Insert SD card into Pi and power on	Pi boots and connects to network	No monitor needed
5	Find Pi IP address on network	IP address identified	Use router or network scan
6	SSH into Pi using IP	Remote terminal access	Control Pi remotely
7	Deploy code or run commands	Code runs on Pi	Headless deployment complete
Exit	All steps done	Pi ready for use	Headless setup successful

💡 All setup steps completed, Pi is accessible remotely without monitor or keyboard

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 6	Final
SD Card	Empty	OS flashed + ssh file added	Wi-Fi config added	Inserted in Pi	N/A	Ready for boot
Pi State	Off	Off	Off	Booting	Online on network	Accessible via SSH
Network	No connection	No connection	Configured	Connecting	Connected	Connected
SSH Access	Disabled	Enabled	Enabled	Enabled	Connected	Connected

Key Moments - 3 Insights

Why do we create an empty 'ssh' file on the SD card?

Creating the 'ssh' file tells the Raspberry Pi to enable SSH on boot, allowing remote access without needing to connect a monitor or keyboard. See execution_table step 2.

How does the Pi connect to Wi-Fi without a screen?

By adding a 'wpa_supplicant.conf' file with Wi-Fi details to the SD card before boot, the Pi uses this info to connect automatically. See execution_table step 3.

How do we find the Pi's IP address to SSH into it?

You can check your router's connected devices list or use a network scanning tool to find the Pi's IP address after it connects. See execution_table step 5.

Visual Quiz - 3 Questions

Look at the execution_table, at which step is SSH enabled on the Raspberry Pi?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Check the 'Action' and 'Result' columns in execution_table row for step 2.

According to variable_tracker, what is the state of the network after step 4?

A No connection

B Connecting

C Configured

D Connected

💡 Hint

Look at the 'Network' row and the column 'After Step 4' in variable_tracker.

If the 'wpa_supplicant.conf' file is missing, what will happen at step 4?

A Pi will connect to Wi-Fi anyway

B SSH will be disabled

C Pi will not connect to Wi-Fi

D Pi will fail to boot

💡 Hint

Refer to execution_table step 3 and the role of the Wi-Fi config file.

Concept Snapshot

Headless Deployment Setup:
1. Flash Raspberry Pi OS to SD card.
2. Enable SSH by adding empty 'ssh' file.
3. Configure Wi-Fi with 'wpa_supplicant.conf'.
4. Insert SD card, power on Pi.
5. Find Pi IP and SSH in remotely.
Allows control without monitor or keyboard.

Full Transcript

Headless deployment setup means preparing a Raspberry Pi so you can use it without a monitor or keyboard. First, you flash the Raspberry Pi OS onto an SD card. Then, you enable SSH by creating an empty file named 'ssh' in the boot partition. Next, you add a file called 'wpa_supplicant.conf' with your Wi-Fi details so the Pi can connect to your network automatically. After inserting the SD card and powering on the Pi, you find its IP address on your network. Finally, you use SSH to connect to the Pi remotely and deploy your code. This setup lets you control the Pi from another computer easily.

Practice

1. What is the main purpose of a headless deployment setup on a Raspberry Pi?

easy

A. To connect multiple Raspberry Pis in a cluster

B. To install a graphical user interface on the Raspberry Pi

C. To control the Raspberry Pi without a monitor, keyboard, or mouse

D. To update the Raspberry Pi firmware automatically

Solution

1. Step 1: Understand headless setup concept

   Headless setup means using the Raspberry Pi without directly connecting a monitor, keyboard, or mouse.

2. Step 2: Identify the main purpose

   This setup allows remote control, usually via SSH, without extra devices attached.

3. Final Answer:

   To control the Raspberry Pi without a monitor, keyboard, or mouse -> Option C

4. Quick Check:

   Headless = Remote control without peripherals [OK]

Hint: Headless means no monitor or keyboard needed [OK]

Common Mistakes:

• Thinking headless means adding a GUI
• Confusing headless with networking multiple Pis
• Assuming it updates firmware automatically

2. Which file must you add to the Raspberry Pi's boot partition to enable SSH on headless setup?

easy

A. ssh_enable

B. ssh.txt

C. enable_ssh.conf

D. ssh

Solution

1. Step 1: Recall SSH enabling method

   To enable SSH on boot, you add an empty file named exactly 'ssh' (no extension) to the boot partition.

2. Step 2: Identify correct filename

   Only the file named 'ssh' without extension works; others are ignored.

3. Final Answer:

   ssh -> Option D

4. Quick Check:

   Empty file named 'ssh' enables SSH [OK]

Hint: Add empty file named 'ssh' to boot partition [OK]

Common Mistakes:

• Adding file with extension like .txt
• Using wrong filenames like ssh_enable
• Not adding any file at all

3. Given this wpa_supplicant.conf content added to the boot partition, what will happen after the Raspberry Pi boots?

country=US
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1

network={
  ssid="HomeWiFi"
  psk="mypassword"
  key_mgmt=WPA-PSK
}

medium

A. The Pi will fail to connect because the country code is missing

B. The Pi will connect to the Wi-Fi network named 'HomeWiFi' automatically

C. The Pi will connect but require manual password entry

D. The Pi will connect to any open Wi-Fi network nearby

Solution

1. Step 1: Analyze wpa_supplicant.conf content

   The file includes correct country code, control interface, and network block with SSID and password.

2. Step 2: Understand Wi-Fi connection behavior

   With this config, the Pi will automatically connect to the specified Wi-Fi network on boot.

3. Final Answer:

   The Pi will connect to the Wi-Fi network named 'HomeWiFi' automatically -> Option B

4. Quick Check:

   Valid wpa_supplicant.conf = Auto Wi-Fi connect [OK]

Hint: Correct wpa_supplicant.conf auto connects Wi-Fi [OK]

Common Mistakes:

• Thinking country code is optional and causes failure
• Assuming manual password input is needed
• Believing it connects to any open network

4. You added the 'ssh' file and 'wpa_supplicant.conf' to the boot partition but cannot SSH into your Raspberry Pi after boot. What is the most likely mistake?

medium

A. The 'ssh' file has a .txt extension, so SSH is not enabled

B. The Raspberry Pi does not support headless setup

C. You forgot to connect a monitor and keyboard

D. The Pi boots too fast to accept SSH connections

Solution

1. Step 1: Check common headless setup errors

   A common error is naming the 'ssh' file with an extension like '.txt', which disables SSH enabling.

2. Step 2: Evaluate other options

   Raspberry Pi supports headless setup; monitor/keyboard not needed; boot speed does not block SSH.

3. Final Answer:

   The 'ssh' file has a .txt extension, so SSH is not enabled -> Option A

4. Quick Check:

   File must be named exactly 'ssh' without extension [OK]

Hint: Check 'ssh' file has no extension [OK]

Common Mistakes:

• Assuming monitor is required for SSH
• Thinking Pi doesn't support headless mode
• Blaming boot speed for SSH failure

5. You want to set up a Raspberry Pi headlessly to connect to a hidden Wi-Fi network named 'SecretNet' with password 'safePass123'. Which wpa_supplicant.conf snippet correctly configures this?

hard

A. network={ ssid="SecretNet" psk="safePass123" scan_ssid=1 }

B. network={ ssid=SecretNet psk=safePass123 hidden=1 }

C. network={ ssid="SecretNet" psk="safePass123" hidden=1 }

D. } 1=neddih "321ssaPefas"=ksp "teNterceS"=diss {=krowten

Solution

1. Step 1: Understand hidden Wi-Fi config

   To connect to a hidden Wi-Fi, you must set scan_ssid=1 to actively scan/probe for the non-broadcasting SSID.

2. Step 2: Check option correctness

   network={ ssid="SecretNet" psk="safePass123" scan_ssid=1 } includes scan_ssid=1 with correct quotes around SSID and password.

3. Final Answer:

   network={ ssid="SecretNet" psk="safePass123" scan_ssid=1 } -> Option A

4. Quick Check:

   Hidden Wi-Fi needs scan_ssid=1 [OK]

Hint: scan_ssid=1 for hidden Wi-Fi [OK]

Common Mistakes:

• Omitting scan_ssid=1 for hidden networks
• Not quoting SSID and password
• Using wrong parameter names like 'hidden=1' alone