Hi Benedikt, sorry for not answering for a week.

our storage driver is the default aufs:

Storage Driver: aufs Root Dir: /var/lib/docker/aufs Backing Filesystem: extfs Dirs: 189 Dirperm1 Supported: false

... based on ext4, also with default option (journaling only on metadata).

That should be fine. Copy on write file systems in general require some attention when using databases (and other applications with massive small writes), but you don't use one (so you shouldn't have an issue with the file system here).

However, we have a persistent volume for the BaseX database files pointed to a regular folder on the host (ext4). To my understanding the storage driver isn't used in this case.

You're right.

Is there a recommendation for a basex filesystem?

The file system is not too important, as long as no copy on write is applied (chattr +t for BTRFS, but read up on that before using it). Ext4, XFS, ... should not require any special attention. I'm not aware anybody every considered different file systems and BaseX performance in a reasonable benchmark yet, but BaseX' access patterns do not differ substantially from other database systems. Regards, Jens -- Jens Erat Universität Konstanz Kommunikations-, Infomations-, Medienzentrum (KIM) Abteilung Basisdienste D-78457 Konstanz Mail: jens.erat@uni-konstanz.de