Cannot mount volumes on stock Postgres image

[tragiclifestories]

Hi! Just playing around with Lima for the first time and having trouble mounting directories using the stock Postgres image - raising here since it doesn't look like Postgres is doing anything too wild so it may be a lima bug?

Reproduction

mkdir -p /tmp/lima/pgdata
lima nerdctl run -v "/tmp/lima/pgdata:/var/lib/postgresql/data" postgres:13
#=> chown: changing ownership of '/var/lib/postgresql/data': Permission denied

Looking at the postgres dockerfile, it creates the directory and CHOWNs it, and then declares the VOLUME afterwards - nothing else in the file seems immediately relevant.

Lima version 0.8.0

Mounts in lima.yaml:

# Expose host directories to the guest, the mount point might be accessible from all UIDs in the guest
# Default: none
mounts:
  - location: "~/Projects"
    # CAUTION: `writable` SHOULD be false for the home directory.
    # Setting `writable` to true is possible, but untested and dangerous.
    writable: true
  - location: "/tmp/lima"
    writable: true

[AkihiroSuda]

sshfs isn't robust (and fast) enough to be used as /var/lib/postgresql.

Please use lima nerdctl volume create to create a named volume inside the guest ext4 filesystem.

[luiz290788]

When you say it isn't fast enough, would this be impractical for a local development environment?

Besides that, is it possible to fix the permission problem? Even if it is not fast enough, this problem might appear in other scenarios where the performance bottleneck is not an issue.