Synology (no terminal)
Synology’s Container Manager app runs the same container image every other install page on this site uses — you just get there by pasting a file into a form instead of running a command. Nothing below needs the NAS’s command line.
What you need
Section titled “What you need”- A Synology NAS running DSM 7.2 or later, with Container Manager installed (Package Center → search “Container Manager” → Install, if it isn’t already).
- A few minutes and a browser open to your NAS’s own web interface — the same one you used to install Container Manager.
Open Container Manager and start a new project
Section titled “Open Container Manager and start a new project”- Open Container Manager from DSM’s main menu.
- Go to the Project section in the left-hand navigation.
- Use the button that creates a new project (in current versions of Container Manager this is labeled Create).
- Give it a name —
palaiais fine, and does not need to match anything else. - Choose or create the shared folder Container Manager should keep this project’s files in. The folder name doesn’t matter either; this is just where Container Manager stores the file you paste next, not where palaia keeps what you save in it (more on that below).
Paste the compose file
Section titled “Paste the compose file”Container Manager’s next step asks how you want to provide the project’s setup. Look for the option that lets you type or paste a compose file directly, rather than uploading one — depending on your version this is labeled something close to Create docker-compose.yml. Paste the file below into that box exactly as it is, then continue.
# palaia v3 hub — compose deployment.## Usage:# cd v3/deploy && docker compose up -d# docker compose logs -f # prints the reachable URL on startup## Then open http://palaia.local:8420/ from any device on the same network# (http://localhost:8420/ on this machine). The hub runs on the host network# so that name reaches your other devices — see v3/deploy/README.md, "mDNS".## Docker Desktop (macOS/Windows) runs containers inside a hidden virtual# machine, where the host network is not your network. There: delete the# `network_mode: host` line and the PALAIA_CLOUD_BIND line below, remove the# `#` in front of the `ports:` block, and open http://localhost:8420/.## Data (vault, index, config) lives in the `palaia_home` named volume, so it# survives `docker compose down` / container recreation — only# `docker compose down -v` discards it.services: hub: # rc-channel-note — release candidate: the `stable` tag is created by the # final 3.0.0 release only. Until then, use `:beta` here. image: ghcr.io/byte5ai/palaia:stable container_name: palaia # The host network: the hub's own name announcement (palaia.local) # reaches the local network only from here; Docker's bridge network does # not forward it. Port 8420 answers on this machine's addresses exactly # as a published `8420:8420` would. network_mode: host # Docker Desktop only (see the header): publish the ports instead. # ports: # - "8420:8420" # - "127.0.0.1:8422:8422" volumes: - palaia_home:/data environment: # The operating mode lives in config.yaml, where the dashboard changes # it; a PALAIA_MODE here would silently override every such change. # `restart: unless-stopped` below starts the hub again after the # dashboard's "Restart" button ends it. PALAIA_SELF_RESTART: "1" # SPEC-501: tells the dashboard's "Update available" banner which # instructions to show — this file, so "run `palaia update`, # then `docker compose pull && docker compose up -d`" rather than a # store's own update button. Leave this as-is; it describes this # file, not a preference to change. PALAIA_DEPLOYMENT: compose # The cloud entry — palaia's AI connection only, for a tunnel on this # machine (Tailscale Funnel, cloudflared) — listens on loopback only: # never reachable from another device. Docker Desktop: delete this # line together with `network_mode: host` (the `ports:` block does # the same there). PALAIA_CLOUD_BIND: "127.0.0.1" restart: unless-stopped # SPEC-502 container posture. The image already runs as a non-root user # (see Dockerfile: `USER palaia`); this block closes what is left. # # - `no-new-privileges` stops any setuid binary inside the image from # regaining root — nothing in the image needs to, and an add-on # someone installs later must not be able to. # - Every Linux capability is dropped. The hub binds 8421 and nginx # binds 8420, both above 1024, so NET_BIND_SERVICE is not needed # either; nothing here wants a capability. # - The root filesystem is read-only. Everything the container writes # at runtime goes to one of the two tmpfs mounts below or to the # `palaia_home` volume: nginx renders its config and keeps its temp # paths under /tmp/nginx (see entrypoint.sh and nginx.conf.template), # and /run is there for anything expecting a runtime directory. # If you add a service that needs to write elsewhere in the image, # give it a tmpfs rather than turning this off. security_opt: - no-new-privileges:true cap_drop: - ALL read_only: true tmpfs: - /tmp - /run healthcheck: test: ["CMD", "curl", "-fsS", "http://127.0.0.1:8420/api/health"] interval: 30s timeout: 5s start_period: 20s retries: 3
volumes: palaia_home:This is the same file the Install it page’s Compose option uses — nothing Synology-specific has been changed, so it stays correct as that file does.
Release candidate: until
3.0.0is final there is nostableimage yet. Before you paste the file above, change itsimage:line fromghcr.io/byte5ai/palaia:stabletoghcr.io/byte5ai/palaia:beta.
About that shared folder, and where your memory actually lives
Section titled “About that shared folder, and where your memory actually lives”The folder you picked two steps ago holds the project’s own compose file — it is not where palaia keeps what you save. That lives in the palaia_home volume the pasted file declares at its bottom, which Docker manages on its own and keeps around even if you delete the project and recreate it later. You don’t need to do anything about this; it’s mentioned here only so deleting the project folder later doesn’t look like it should have deleted your memory too — it doesn’t.
Start it
Section titled “Start it”Continue past any remaining setup screens (Container Manager may offer to also set up quick web access — safe to skip, it isn’t needed) and finish creating the project. Container Manager pulls the image and starts the container; the project’s status shows Running once it has.
If it doesn’t reach Running, open the container’s log from Container Manager itself — the Container section, select palaia, then its Log (or Details) tab — rather than a terminal; the same startup message Install it describes shows up there.
Open the hub
Section titled “Open the hub”You reached Container Manager just now through your NAS’s own address in a browser — the same address, with :8420 instead of DSM’s own port, reaches palaia:
http://<your-NAS-address>:8420The compose file runs the container on the NAS’s own network, so it also announces itself by name: http://palaia.local:8420 opens it from your other devices too, the same as every other Linux install. Whether that name resolves depends on how your network handles it — some routers keep it from crossing between separate networks, the caveat Install it covers. Either way, the address above always works.
From there, a short setup wizard takes over — see Get palaia running for what that looks like, or Your first shared memory for the full walkthrough once it’s done.
Later: updating
Section titled “Later: updating”Open the project in Container Manager and use the action that rebuilds it from the compose file — usually an Action menu or Build button on the project’s own page. If your version doesn’t pull a fresh image on its own, delete the project and recreate it the same way as above: your memory is untouched either way, since it lives in the separate palaia_home volume, not the project’s folder.
Something not covered here? Troubleshooting & FAQ covers the issues people actually hit, or the project’s issue tracker for anything new.