Stream your Omarchy desktop to another computer using Sunlight/Moonlight #179

dougvk · 2025-07-15T05:29:28Z

dougvk
Jul 15, 2025

Sunshine Docker Run (Generic) — With Video Group and WAYLAND_DISPLAY Instructions

Below is a fully generic command and setup guide for running Sunshine via Docker on Linux desktops with Wayland, including instructions for ensuring your user has video device access and for determining your WAYLAND_DISPLAY value.

1. Ensure Your User is in the `video` Group

For hardware-accelerated encoding (VAAPI, etc.), your user must be in the video group, which owns GPU device files.

How to add your user to the video group:

sudo usermod -aG video <USERNAME>

Replace <USERNAME> with your actual Linux username. Log out and log back in (or run newgrp video) for the group change to take effect.

To confirm:

groups <USERNAME>

You should see video listed among the groups.

2. Find Your `WAYLAND_DISPLAY` Value

The WAYLAND_DISPLAY environment variable is needed for streaming your graphical session.

How to find the value:

In your terminal, enter:

echo $WAYLAND_DISPLAY

You’ll typically see something like wayland-0, wayland-1, etc.

3. Generic Docker Run Command

Replace all placeholder values as indicated.

docker run -d \
  --device /dev/dri/ \
  --device /dev/uinput \
  --group-add video \
  --name=sunshine \
  --restart=unless-stopped \
  --ipc=host \
  --cap-add=SYS_ADMIN \
  -e PUID=$(id -u <USERNAME>) \
  -e PGID=$(id -g <USERNAME>) \
  -e TZ=<YOUR_TIMEZONE> \
  -e WAYLAND_DISPLAY=<YOUR_WAYLAND_DISPLAY> \
  -v /home/<USERNAME>/sunshine:/config \
  -v /run/user/$(id -u <USERNAME>)/<YOUR_WAYLAND_DISPLAY>:/run/user/$(id -u <USERNAME>)/<YOUR_WAYLAND_DISPLAY> \
  -v /run/user/$(id -u <USERNAME>):/run/user/$(id -u <USERNAME>) \
  -p 47984-47990:47984-47990/tcp \
  -p 48010:48010 \
  -p 47998-48000:47998-48000/udp \
  lizardbyte/sunshine:latest-archlinux

Replace:

<USERNAME>: your Linux login name
<YOUR_TIMEZONE>: your local timezone string, e.g. Europe/Berlin
<YOUR_WAYLAND_DISPLAY>: value from echo $WAYLAND_DISPLAY

Example for user alex, Europe/Paris, and wayland-1:

docker run -d \
  --device /dev/dri/ \
  --device /dev/uinput \
  --group-add video \
  --name=sunshine \
  --restart=unless-stopped \
  --ipc=host \
  --cap-add=SYS_ADMIN \
  -e PUID=$(id -u alex) \
  -e PGID=$(id -g alex) \
  -e TZ=Europe/Paris \
  -e WAYLAND_DISPLAY=wayland-1 \
  -v /home/alex/sunshine:/config \
  -v /run/user/$(id -u alex)/wayland-1:/run/user/$(id -u alex)/wayland-1 \
  -v /run/user/$(id -u alex):/run/user/$(id -u alex) \
  -p 47984-47990:47984-47990/tcp \
  -p 48010:48010 \
  -p 47998-48000:47998-48000/udp \
  lizardbyte/sunshine:latest-archlinux

4. Quick Checklist

Add user to video group for GPU access
Get your WAYLAND_DISPLAY value for proper Wayland streaming
Adjust all <...> fields in the run command accordingly

If you need further roles or group permissions (for example, for input devices), follow similar steps as above for the corresponding group.

Then download the Moonlight Client and start with these settings. I recommend using Tailscale to create a "home" network of local devices. Add your host's IP on Tailscale then get going!

foeken · 2025-07-26T12:41:31Z

foeken
Jul 26, 2025

For those reading along, to get mouse/keyboard input working:

sudo usermod -aG input $USER

In the docker run, I added --group-add input (not sure it's needed)

And then:

echo 'KERNEL=="uinput", MODE="0660", GROUP="input"' | sudo tee /etc/udev/rules.d/99-uinput.rules

0 replies

dougvk · 2025-07-26T13:16:23Z

dougvk
Jul 26, 2025
Author

interesting, let me check my notes, maybe I forgot that part. in the instructions

…

On Sat, Jul 26, 2025 at 14:41, Andre Foeken < ***@***.*** > wrote: For those reading along, to get mouse/keyboard input working: sudo usermod -aG input $USER In the docker run, I added --group-add input (not sure it's needed) And then: echo 'KERNEL=="uinput", MODE="0660", GROUP="input"' | sudo tee /etc/udev/rules.d/99-uinput.rules — Reply to this email directly, view it on GitHub ( #179 (comment) ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AADCB7FLPWNJPFFLL6FMXIT3KNZRBAVCNFSM6AAAAACBQ3VJKGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGOBZGYZTINA ). You are receiving this because you authored the thread. Message ID: <basecamp/omarchy/repo-discussions/179/comments/13896344 @ github. com>

0 replies

dougvk · 2025-07-28T13:45:51Z

dougvk
Jul 28, 2025
Author

yep - forgot that part of the setup. good catch

0 replies

dougvk · 2026-02-25T10:52:56Z

dougvk
Feb 25, 2026
Author

Update (February 25, 2026): Arch + Docker compose/systemd guide that worked reliably for me.

The key change vs older examples is using an Arch Linux Sunshine image tag and managing it with Docker Compose + systemd.

1) Host prep (input permissions)

sudo usermod -aG input "$USER"
sudo tee /etc/udev/rules.d/85-sunshine-input.rules >/dev/null <<'EOF'
KERNEL=="uinput", SUBSYSTEM=="misc", OPTIONS+="static_node=uinput", TAG+="uaccess", GROUP="input", MODE="0660"
EOF
sudo udevadm control --reload-rules
sudo udevadm trigger

Log out/in once after adding yourself to input.

2) Create persistent dirs

mkdir -p ~/docker/sunshine/{config,assets}

3) Compose file (`~/docker/sunshine/compose.yml`)

name: sunshine

services:
  sunshine:
    container_name: sunshine
    image: lizardbyte/sunshine:v2025.1027.181930-archlinux
    restart: unless-stopped

    # Important on some hosts for /dev/dri and /dev/uinput access
    user: "0:0"
    privileged: true
    ipc: host

    environment:
      TZ: Etc/UTC

    devices:
      - /dev/dri:/dev/dri
      - /dev/uinput:/dev/uinput

    # Arch image expects config under /home/lizard/.config/sunshine
    volumes:
      - ./config:/home/lizard/.config/sunshine
      - ./assets:/home/lizard/.local/share/sunshine/assets

    ports:
      - "47984-47990:47984-47990/tcp"
      - "48010:48010/tcp"
      - "47998-48000:47998-48000/udp"

4) Bring it up

cd ~/docker/sunshine
docker compose up -d

5) Bind to systemd for boot startup

Create /etc/systemd/system/sunshine-compose.service:

[Unit]
Description=Sunshine stack managed by Docker Compose
Requires=docker.service
After=docker.service network-online.target
Wants=network-online.target

[Service]
Type=oneshot
RemainAfterExit=yes
WorkingDirectory=/home/youruser/docker/sunshine
ExecStart=/usr/bin/docker compose up -d --remove-orphans
ExecStop=/usr/bin/docker compose down
TimeoutStartSec=120
TimeoutStopSec=120

[Install]
WantedBy=multi-user.target

Then:

sudo systemctl daemon-reload
sudo systemctl enable --now sunshine-compose.service

6) Firewall (if using ufw)

Open Sunshine ports only on the interface you actually use (LAN or tailscale0), for example:

sudo ufw allow in on tailscale0 to any port 47984:47990 proto tcp
sudo ufw allow in on tailscale0 to any port 48010 proto tcp
sudo ufw allow in on tailscale0 to any port 47998:48000 proto udp

7) First run

Open https://<host>:47990, set Sunshine credentials, then pair Moonlight.

8) Why this worked without Wayland setup

Sunshine can capture with multiple backends; in this setup it used KMS/DRM, not Wayland portal/wlr capture.
KMS/DRM path mainly needs direct access to /dev/dri (GPU) and /dev/uinput (input injection) plus a connected display.
The failures in older attempts were mostly runtime/path/permission mismatches (image tag, config mount path, container user privileges), not a mandatory Wayland-specific requirement.

If anyone wants, I can also post a tighter hardened variant (dropping privileged and adding only specific capabilities/devices), but the above was the straightforward stable setup.

0 replies

jesalazaro · 2026-03-22T01:11:05Z

jesalazaro
Mar 22, 2026

Hi, it worked for me right out of the box, but I wanted to ask if you know a way to connect during the login screen. I think it’s impossible because of disk encryption, but it doesn’t hurt to ask.

0 replies

dougvk · 2026-03-22T01:20:27Z

dougvk
Mar 22, 2026
Author

Glad to hear it worked for you right away! If you're looking for a way to wake up your screen during the login screen, you can create a bash script to simulate mouse movement. This works for me.

…

On Sun, Mar 22, 2026 at 10:11, Jaiver Salazar O. < ***@***.*** > wrote: Hi, it worked for me right out of the box, but I wanted to ask if you know a way to connect during the login screen. — Reply to this email directly, view it on GitHub ( #179?email_source=notifications&email_token=AADCB7H6FM4OSVUYL2LVA534R44T5A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRSGQ4DCMZXUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-16248137 ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AADCB7AL5MXRS2MM2TYHQOL4R44T5AVCNFSM6AAAAACV7DWV6WVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMRUHAYTGNY ). You are receiving this because you authored the thread. Message ID: <basecamp/omarchy/repo-discussions/179/comments/16248137 @ github. com>

1 reply

jesalazaro Mar 22, 2026

Glad to hear it worked for you right away! If you're looking for a way to wake up your screen during the login screen, you can create a bash script to simulate mouse movement. This works for me.
…
On Sun, Mar 22, 2026 at 10:11, Jaiver Salazar O. < @.*** > wrote: Hi, it worked for me right out of the box, but I wanted to ask if you know a way to connect during the login screen. — Reply to this email directly, view it on GitHub ( #179?email_source=notifications&email_token=AADCB7H6FM4OSVUYL2LVA534R44T5A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRSGQ4DCMZXUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-16248137 ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AADCB7AL5MXRS2MM2TYHQOL4R44T5AVCNFSM6AAAAACV7DWV6WVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMRUHAYTGNY ). You are receiving this because you authored the thread. Message ID: <basecamp/omarchy/repo-discussions/179/comments/16248137 @ github. com>

What I actually meant was being able to either enter the password automatically at startup or connect via Moonlight while still on the decrypt screen to type it remotely.

From what I’ve found, neither really works with full disk encryption enabled. The system requires the password to be entered locally before it fully boots, so Moonlight can’t connect at that stage.

The only way I managed to get it working was by removing disk encryption so the system can autologin and be reachable right away. Otherwise, you’re stuck needing physical access,

dougvk · 2026-03-22T01:40:02Z

dougvk
Mar 22, 2026
Author

pre-boot yes. but like. just leave ur computer on?

…

On Sun, Mar 22, 2026 at 10:31, Jaiver Salazar O. < ***@***.*** > wrote: > > > Glad to hear it worked for you right away! If you're looking for a way to > wake up your screen during the login screen, you can create a bash script > to simulate mouse movement. This works for me. > … ( # ) > On Sun, Mar 22, 2026 at 10:11, Jaiver Salazar O. < *@*.*** > wrote: Hi, it > worked for me right out of the box, but I wanted to ask if you know a way > to connect during the login screen. — Reply to this email directly, view > it on GitHub ( #179 ( #179 ) > ?email_source=notifications&email_token=AADCB7H6FM4OSVUYL2LVA534R44T5A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRSGQ4DCMZXUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-16248137 > ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AADCB7AL5MXRS2MM2TYHQOL4R44T5AVCNFSM6AAAAACV7DWV6WVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMRUHAYTGNY > ). You are receiving this because you authored the thread. Message ID: > <basecamp/omarchy/repo-discussions/179/comments/16248137 @ github. com> > > What I actually meant was being able to either enter the password automatically at startup or connect via Moonlight while still on the login screen to type it remotely. From what I’ve found, neither really works with full disk encryption enabled. The system requires the password to be entered locally before it fully boots, so Moonlight can’t connect at that stage. The only way I managed to get it working was by removing disk encryption so the system can autologin and be reachable right away. Otherwise, you’re stuck needing physical access — Reply to this email directly, view it on GitHub ( #179?email_source=notifications&email_token=AADCB7BZRYFLILDPMVZCKFL4R4673A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRSGQ4DIMZQUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-16248430 ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AADCB7HMB62HUEZAXVV2JBT4R4673AVCNFSM6AAAAACV7DWV6WVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMRUHA2DGMA ). You are receiving this because you authored the thread. Message ID: <basecamp/omarchy/repo-discussions/179/comments/16248430 @ github. com>

0 replies

Uh oh!

Stream your Omarchy desktop to another computer using Sunlight/Moonlight #179

Uh oh!

dougvk Jul 15, 2025

Sunshine Docker Run (Generic) — With Video Group and WAYLAND_DISPLAY Instructions

1. Ensure Your User is in the video Group

2. Find Your WAYLAND_DISPLAY Value

3. Generic Docker Run Command

Replace:

4. Quick Checklist

Replies: 7 comments · 1 reply

Uh oh!

foeken Jul 26, 2025

Uh oh!

dougvk Jul 26, 2025 Author

Uh oh!

dougvk Jul 28, 2025 Author

Uh oh!

Uh oh!

dougvk Feb 25, 2026 Author

1) Host prep (input permissions)

2) Create persistent dirs

3) Compose file (~/docker/sunshine/compose.yml)

4) Bring it up

5) Bind to systemd for boot startup

6) Firewall (if using ufw)

7) First run

8) Why this worked without Wayland setup

Uh oh!

Uh oh!

jesalazaro Mar 22, 2026

Uh oh!

dougvk Mar 22, 2026 Author

Uh oh!

Uh oh!

jesalazaro Mar 22, 2026

Uh oh!

dougvk Mar 22, 2026 Author

dougvk
Jul 15, 2025

1. Ensure Your User is in the `video` Group

2. Find Your `WAYLAND_DISPLAY` Value

Replies: 7 comments 1 reply

foeken
Jul 26, 2025

dougvk
Jul 26, 2025
Author

dougvk
Jul 28, 2025
Author

dougvk
Feb 25, 2026
Author

3) Compose file (`~/docker/sunshine/compose.yml`)

jesalazaro
Mar 22, 2026

dougvk
Mar 22, 2026
Author

dougvk
Mar 22, 2026
Author