Attaching the Jellyfin bind-mount in Proxmox

This is the only step that requires touching Proxmox. Everything else (installing packages, configuring YAAR, starting the service) is done from inside your existing Alpine container using setup.sh.

What this does

Proxmox's mp0 bind-mount makes a directory on the Proxmox host visible inside the container at a chosen path. YAAR expects to find your Jellyfin media at /nas/jellyfin inside the container.

You only need to run one of the options below — once, before running setup.sh.

Option A — Proxmox web UI (safest, no shell access needed)

Log into the Proxmox web UI.
Click your container in the left sidebar.
Go to Resources → Add → Mount Point.
Fill in: | Field | Value | |---|---| | Storage | — (leave blank for directory bind-mount) | | Host path | /mnt/nas/jellyfin (the path on your Proxmox host) | | Container path | /nas/jellyfin | | Read-only | No |
Click Add.
Restart the container from the web UI (or pct restart <CTID>).

Option B — Proxmox host shell (one command)

SSH into your Proxmox host (not the container), then:

pct set <CTID> -mp0 /mnt/nas/jellyfin,mp=/nas/jellyfin
pct restart <CTID>

Replace <CTID> with your container ID and /mnt/nas/jellyfin with the actual path to your Jellyfin media directory on the Proxmox host.

Verify the mount is visible inside the container

pct enter <CTID>
ls /nas/jellyfin
# Should show: Movies  Shows  (and whatever else is on your NAS)

Then run YAAR setup (inside the container)

# Get the YAAR archive into the container — choose one:
#   From host:  pct push <CTID> /path/to/yaar.tar.gz /root/yaar.tar.gz
#   Via scp:    scp yaar.tar.gz root@<container-ip>:/root/
#   Via browser: Proxmox web UI → container → Upload

# Then, inside the container:
tar xzf /root/yaar.tar.gz -C /root/
sh /root/yaar/setup.sh

setup.sh checks that it is not running on the Proxmox host and will refuse to proceed if it detects a PVE environment.

proxmox-mount.md 2.1 KB Historia Raaka