Litestream as an accessory

[AaronRustad]

I'm trying to configure Litestream as an accessory, and I'm stumped on why kamal (or more likely, a command it runs) is telling me that the /etc/litestream.yml is a directory.

userx@host ➜  my-app git:(kamalize) kamal accessory reboot litestream
  INFO [5353b848] Running /usr/bin/env mkdir -p .kamal on 178.xxx.xxx.xxx
  INFO [5353b848] Finished in 1.945 seconds with exit status 0 (successful).
Acquiring the deploy lock...
  INFO [cca2f937] Running docker login ghcr.io -u [REDACTED] -p [REDACTED] on 178.xxx.xxx.xxx
  INFO [cca2f937] Finished in 0.694 seconds with exit status 0 (successful).
  INFO [10c73bd5] Running docker network create kamal on 178.xxx.xxx.xxx
  INFO [e7493509] Running docker container stop my-app-litestream on 178.xxx.xxx.xxx
  INFO [e7493509] Finished in 0.275 seconds with exit status 0 (successful).
  INFO [44d8ce45] Running docker container prune --force --filter label=service=my-app-litestream on 178.xxx.xxx.xxx
  INFO [44d8ce45] Finished in 0.447 seconds with exit status 0 (successful).
  INFO [661001dd] Running /usr/bin/env mkdir -p my-app-litestream/etc on 178.xxx.xxx.xxx
  INFO [661001dd] Finished in 0.247 seconds with exit status 0 (successful).
  INFO Uploading /Users/userx/Documents/Development/climb/my-app/config/litestream.yml 100.0%
  INFO [e7705c76] Running /usr/bin/env chmod 755 my-app-litestream/etc/litestream.yml on 178.xxx.xxx.xxx
  INFO [e7705c76] Finished in 0.250 seconds with exit status 0 (successful).
  INFO [d0d8118c] Running /usr/bin/env mkdir -p .kamal/apps/my-app/env/accessories on 178.xxx.xxx.xxx
  INFO [d0d8118c] Finished in 0.257 seconds with exit status 0 (successful).
  INFO Uploading .kamal/apps/my-app/env/accessories/litestream.env 100.0%
  INFO [cfc64bfb] Running docker run --name my-app-litestream --detach --restart unless-stopped --network kamal --log-opt max-size="10m" --env-file .kamal/apps/my-app/env/accessories/litestream.en
v --volume volume_sfo2_01:/storage --volume $PWD/my-app-litestream/etc/litestream.yml:/etc/litestream.yml --label service="my-app-litestream" litestream/litestream:0.3 replicate on 178.xxx.xxx.xxx
  INFO [cfc64bfb] Finished in 1.256 seconds with exit status 0 (successful).
Releasing the deploy lock...
userx@host ➜  my-app git:(kamalize) kamal accessory logs  litestream
  INFO [7df870bd] Running docker logs my-app-litestream  --tail 100 --timestamps 2>&1 on 178.xxx.xxx.xxx
  INFO [7df870bd] Finished in 1.224 seconds with exit status 0 (successful).
2024-12-17T23:00:59.992627910Z 2024/12/17 23:00:59 ERROR failed to run error="read /etc/litestream.yml: is a directory"
2024-12-17T23:01:00.579825285Z 2024/12/17 23:01:00 ERROR failed to run error="read /etc/litestream.yml: is a directory"

The deploy.yml looks like:

accessories:
  litestream:
    image: litestream/litestream:0.3
    host: 178.xxx.xxx.xxx
    files:
      - config/litestream.yml:/etc/litestream.yml
    volumes: ["volume_sfo2_01:/storage"]
    env:
      secret:
        - LITESTREAM_ACCESS_KEY_ID
        - LITESTREAM_SECRET_ACCESS_KEY
    cmd: "replicate"

As far as I can tell, this looks correct to me.

Thanks for your help!

[AaronRustad]

Really not sure what happened. I ended up blowing away litestream app configs on the host and deploy/redeploy several times. ¯_(ツ)_/¯