Spark & Reachy Photo Booth

Clone the repo

To easily manage containers without sudo, you must be in the docker group. If you choose to skip this step, you will need to run Docker commands with sudo.

Open a new terminal and test Docker access. In the terminal, run:

docker ps

If you see a permission denied error (something like permission denied while trying to connect to the Docker daemon socket), add your user to the docker group so that you don't need to run the command with sudo.

sudo usermod -aG docker $USER
newgrp docker

git clone https://github.com/NVIDIA/spark-reachy-photo-booth.git
cd spark-reachy-photo-booth

Create your environment

cp .env.example .env

Edit .env and set:

• NVIDIA_API_KEY: your NVIDIA API key (must start with nvapi-...)
• HF_TOKEN: your Hugging Face token (must start with hf_...)
• EXTERNAL_MINIO_BASE_URL: leave unchanged, unless you want to (see the section "Enable QR-code sharing on your local network")

To access the FLUX.1-Kontext-dev model, sign in to your Hugging Face account, then review and accept the FLUX.1-Kontext-dev and FLUX.1-Kontext-dev-onnx License Agreements and Acceptable Use Policy.

The remaining values are configured with reasonable defaults for local development (MinIO). For production deployments or untrusted environments, these values should be changed and stored securely.

Set up Reachy

• Plug the power cable to the base of Reachy and to a power outlet.
• Plug a USB-C cable to the base of Reachy and to the DGX Spark.
• Engage the power switch at the base of Reachy. The LED next to the switch should turn red.

You can verify that the robot is detected by running:

lsusb | grep Reachy

You should see a device printed in the terminal similar to Bus 003 Device 003: ID 38fb:1001 Pollen Robotics Reachy Mini Audio.

Run the following command to make sure the Reachy speaker can reach the maximum volume.

./robot-controller-service/scripts/speaker_setup.sh

Start the stack

Sign in to the nvcr.io registry:

docker login nvcr.io -u "\$oauthtoken"

When prompted for a password, enter your NGC personal API key.

docker compose up --build -d

This command pulls and builds container images, and downloads the required model artifacts. The first run can take between 30 minutes and 2 hours, depending on your internet speed. Subsequent runs usually complete in about 5 minutes.

Open the UI in your browser

On the DGX Spark, open Firefox (pre-installed) and browse to the Web UI: http://127.0.0.1:3001.

Optional: Enable QR-code sharing on your local network

Reachy can take pictures of people and generate images based on them. The web UI displays the generated images along with a QR code for downloading them. This section explains how to set up the system so that the QR code is accessible from users' phones.

For QR codes to open on your phone, your DGX Spark and phone must be on the same local network. Ensure that your router permits device-to-device communication within the network.

1. Find your Spark’s local IP address

On the Spark, run the following command:

ip -f inet addr show enP7s7 | grep inet

Or this command if your Spark is connected through Wi-Fi

ip -f inet addr show wlP9s9 | grep inet

Find the IPv4 on your LAN (often something like 192.168.x.x or 10.x.x.x).

2. Ensure MinIO is reachable from your phone

• Same network: connect your phone to the same Wi‑Fi/LAN as the DGX Spark.
• Firewall: by default, DGX Spark does not block incoming requests. If you installed a firewall, allow inbound traffic to the DGX Spark on 9010 (MinIO API).

3. Update .env and restart

Edit .env and replace:

• EXTERNAL_MINIO_BASE_URL=127.0.0.1:9010 → EXTERNAL_MINIO_BASE_URL=<SPARK_LAN_IP>:9010

Then restart:

docker compose down
docker compose up --build -d

Optional: Going Further & Customizing the Application

Guides

• Getting Started – In-depth setup and configuration walkthrough
• Writing Your First Service – How to create and integrate a new service

Service Configuration

Each service has its own README with details on customization, environment variables, and service-specific configuration:

For detailed guidance on customizing service configurations, extending the demo with new tools, or creating your own services, refer to the Development tab.