Error: volume already claimed. Litefs, consul with bluegreen strategy

Right, unfortunately those two are incompatible, :cactus::

The bluegreen strategy cannot be used for Machines with attached volumes.

Generally, this is geared toward apps that use a separate Postgres database (or that’s my inference, anyway).

rolling and immediate are the only possibilities when your app has persistent volumes.

LiteFS itself takes a little head-scratching at first, but it’s typically really solid after the initial acclimation period.

Hope this helps!