Docker Installation

For Docker on Linux x86_64 / aarch64. Sign in with the application administrator password and select files inside mounted folders. Use the fnOS FPK for native NAS account sign-in and the system folder picker.

Import the image

Check Downloads for Docker availability first. Once you have the image archive for your NAS architecture and its .sha256 file, verify and import it from the archive directory:

sha256sum -c leelaa-audio-split-*.tar.sha256
docker load -i <track-factory-image.tar>

The current delivery is a local candidate archive; a public image has not been published. Importing it creates leelaa-audio-split:local. The source build entry is pnpm build:docker at the repository root; see the project README for prerequisites.

Choose folders and a port

Save the following as compose.yaml in your installation directory:

name: leelaa-audio-split
services:
  audio-split:
    image: leelaa-audio-split:local
    pull_policy: never
    init: true
    restart: unless-stopped
    read_only: true
    cap_drop: [ALL]
    security_opt: [no-new-privileges:true]
    stop_grace_period: 30s
    ports:
      - "${AUDIO_PORT:-8692}:8692"
    volumes:
      - data:/data
      - cache:/cache
      - type: bind
        source: ${AUDIO_INPUT_DIR:?请设置 AUDIO_INPUT_DIR 为源音频目录}
        target: /input
        read_only: true
        bind:
          create_host_path: false
      - type: bind
        source: ${AUDIO_OUTPUT_DIR:?请设置 AUDIO_OUTPUT_DIR 为输出目录}
        target: /output
        bind:
          create_host_path: false
      - type: bind
        source: /etc/machine-id
        target: /run/host/machine-id
        read_only: true
        bind:
          create_host_path: false
    tmpfs:
      - /tmp:rw,noexec,nosuid,size=64m
volumes:
  data:
  cache:

Input and output folders must already exist. The application runs as UID/GID 10001:10001, which needs read permission on input and write permission on output. Set paths and start it in the same terminal:

export AUDIO_INPUT_DIR=/your/nas/audiobooks
export AUDIO_OUTPUT_DIR=/your/nas/split-output
export AUDIO_PORT=8692
docker compose --project-directory . -f compose.yaml up -d

Open http://NAS-address:8692/. AUDIO_PORT changes the host port; the container still uses 8692. Folders appear as input and output in the app. Input is read-only; each job writes a new output folder. Fix invalid paths or permissions before starting, granting access only to selected folders.

First sign-in

The initial username is admin. A random password is generated in the persistent volume. The device administrator can view it in their own terminal:

docker compose -f compose.yaml exec audio-split cat /data/bootstrap-admin.txt

Change this password after signing in; the plaintext file is then removed. Use the License Center to handle software authorization before splitting. The initial password is never printed in container logs.

Update and back up

After importing a new archive, keep the installation directory, Compose project name, and folder settings, then run:

docker compose -f compose.yaml up -d --force-recreate

The data volume holds the administrator, license installation identity, platform connection, and job history. Stop the app before backing up the whole volume. The separate cache volume holds regenerable analysis and audition files. Source and output files remain in host folders.

docker compose down preserves data volumes. docker compose down -v deletes the administrator, local license records, and history; back up first. Removing the container does not delete host input or output files.

Device identity and recovery

Compose mounts the Linux host's /etc/machine-id read-only. Keep that mount and the data volume when recreating containers on the same host to preserve installation identity. Missing or invalid identity refuses startup instead of falling back to a temporary container ID. Do not copy another device's identity file.

Use License Recovery and Migration after clearing data or changing devices; a public device identifier alone cannot obtain a license. Docker and FPK are separate installations. Production Auth, migration, and physical NAS permissions still require validation in the corresponding environments.