LiteFS flyio/litefs image: "fusermount3": executable file not found in $PATH

[rsas]

Excited to read about and try LiteFS Cloud!

Starting with the official Docker image from flyio/litefs today, I get the following error on my M1:

$ docker run --rm -v "$PWD/litefs-docker.yml:/etc/litefs.yml" -v "$PWD/litefs-fuse:/litefs-fuse" -v "$PWD/litefs-data:/litefs-data" flyio/litefs mount

config file read from /etc/litefs.yml
LiteFS v0.5.1, commit=00c0ca55a1f85c3273898d11e9cd5e076b966174
level=INFO msg="no backup client configured, skipping"
level=INFO msg="no proxy target set, skipping proxy"
level=INFO msg="Using static primary: primary=true hostname= advertise-url="
ERROR: cannot init file system: cannot open file system: fusermount: exec: "fusermount3": executable file not found in $PATH
level=INFO msg="F67C9CDDDD481575: primary lease acquired, advertising as "
level=INFO msg="set cluster id on \"static\" lease \"LFSC114C62D1FB2CFA59\""
level=INFO msg="F67C9CDDDD481575: exiting primary, destroying lease"

The litefs-docker.yml is as follows:

fuse:
  dir: "/litefs-fuse"

data:
  dir: "/litefs-data"

lease:
  type: "static"
  candidate: true

Is it an image problem?

[benbjohnson]

We build the flyio/litefs Docker image to make it easy to distribute the binary to other Docker images since the litefs binary needs run in your own image. However, you bring up a good point about trying it out. I added an issue to fix it so it is runnable on its own.

[rsas]

Thanks Ben, I understand the reasoning, but it was not self-explanatory at the time I tried it.