hello, I've just spotted something related to the newer Keto images (since the

-sqlite

tag was dropped). If I understand correctly, the idea was that the "standard" Keto image would include sqlite anyway, so there was no need to have two images. However, in the -sqlite images, the Dockerfile created the destination directory /var/lib/sqlite and set the right permissions on it: https://github.com/ory/keto/blob/master/.docker/Dockerfile-sqlite#L21 This meant that a named volume mount to

/var/lib/sqlite

would get the right permissions, and be writeable. The newer images, e.g. v0.10.0, were built without these lines, and so the named volume is created at docker-runtime with

root

ownership, and so the image doesn't run as expected. The two solutions I can see are either: 1. build a -sqlite image using the separate Dockerfile, or 2. create the directory in the "standard" image, so the volume mount works as expected what do you think?