Docker volume stays empty - the image runs as the meili user, chown the host dir

If your Docker-mounted Meilisearch data directory stays empty, check ownership, not the config. The official image runs as the meili user, so a host directory owned by root is not writable by the container and nothing lands in the volume. Fix it by chowning the host directory to the meili UID before starting the container, or run the container with a user flag matching your host UID. The empty folder with no error message is the classic symptom.

Context: Issue meilisearch/meilisearch#1969 (closed, 46 comments): running Meilisearch v0.24 in Docker with a mounted volume at the data path wrote nothing - the host folder stayed empty even though the docs said data lands there. The maintainer traced it to the meili user the Docker image runs as: the mounted directory was owned by root on the host, so the process silently could not write.

Source: Issue meilisearch/meilisearch#1969 (closed, 46 comments): running Meilisearch v0.24 in Docker with a mounted volume at the data path wrote nothing - the host folder stayed empty even though the docs said data lands there. The maintainer traced it to the meili user the Docker image runs as: the mounted directory was owned by root on the host, so the process silently could not write.

Verified resolution: If your Docker-mounted Meilisearch data directory stays empty, check ownership, not the config. The official image runs as the meili user, so a host directory owned by root is not writable by the container and nothing lands in the volume. Fix it by chowning the host directory to the meili UID before starting the container, or run the container with a user flag matching your host UID. The empty folder with no error message is the classic symptom.

Source URL: https://github.com/meilisearch/meilisearch/issues/1969