Accessory Data: Directories vs Volumes

[leonvogt]

I would like to store my accessories data in a dedicated /var/ directory.

The are two options to mount accessories data: Volumes and Directories. The main difference is that directories creates the directory on the host before mounting the volume.
directories seems to be the right choice for me since I don't want to create the directories manually.

The issue I'm facing is that directories are scoped to the user's home directory. When I set directories to /var/lib/redis:/data, the directory $PWD/my-appname-redis//var/lib/redis is created on the host.

I could create the directories manually and use the volumes key, but I would like to avoid that.

I'm not sure if this behavior is intended or not. If my deploy user has the permission to create directories in the /var/lib directory, I see no reason why Kamal should not allow me to do so.

---

Additional Information:

Volumes approach:

redis:
  volumes:
    - /var/lib/redis:/data

Output

# kamal accessory boot redis
Running docker run [...] --volume /var/lib/redis:/data

---

Directories approach:

redis:
  directories:
    - /var/lib/redis:/data

Output

# kamal accessory boot redis
Running docker run [...] --volume $PWD/my-appname-redis//var/lib/redis:/data

If there are options to change this behavior, I'll be happy to explore them and contribute to resolving this issue.

[dhh]

I'd be happy to see a patch where directories declared with a leading / don't add PWD but still create the directory 👍