The adapter builds its base URL as `base_url or settings.storage_url or self._default_local_base_url()`, and the fallback returns a `file://` URI under the repository root [11]. On that evidence, pointing `STORAGE_URL` at a directory should drop the object store, which is the inference the author made and then had to withdraw [10]. What actually runs is `_normalize_root_path`, one line: `root_path.replace("\\", "/").strip("/")` [14]. Python's `strip` works on both ends, so the absolute `/home/appuser/soit-storage` comes out as the relative `home/appuser/soit-storage`, and fsspec's LocalFileSystem resolves that against the process working directory [14]. The image sets `WORKDIR /app/` [15]. The write therefore goes to `/app/home/...`, and constructing the adapter inside the container raised `PermissionError: [Errno 13] Permission denied: '/app/home'` [13]. For a path normalizer, converting absolute paths into relative ones is an unusual service to offer.
`/app` is root-owned because `server/Dockerfile` copies the tree with `COPY ./ /app/` and no `--chown`, while the final instruction is `USER appuser` at uid 10001 [16]. A volume does not rescue it, since Docker creates the mount point root-owned as well [17]. That leaves running the API as root or pre-chowning a mount [18]. So the transfer condition for anyone else's object-store-free variant is narrow: the image's working directory has to be writable by the runtime user, or the normalizer has to stop eating the leading slash.
Four counts the containers still standing, out of seven that compose actually starts. Seven declared services minus the three that exit is four [4][21], and six of the twelve names in the original command are gone [22]. One image dominates the saving, Milvus at 2.6GB [5]. Read "a couple hundred megabytes" as 200 to 300MB and MinIO is roughly 9 to 13 times smaller [19][23], which is why keeping it costs an evaluator very little.
The method is what makes this write-up durable: a deployment guide records intent, a health check records behaviour [8]. That holds on the vector store, where a failed readiness check sets the field to `unavailable` and still returns 200, because the docstring says the platform degrades gracefully without it [6][7]. It breaks on storage, where the 503 branch reports "Object storage is unavailable" [6] for a fault that is really path handling plus directory ownership [12][13]. The author says two of his three code-derived conclusions failed on contact with a running stack, and that publishing the paper version would have left readers with a stack that starts and then refuses to show a UI [20]. The text supplied to me documents the first of those and cuts off mid-aside before the second [24]. One demonstrated failure of this kind is enough for me: a compose file plus a health router is not evidence about which services are optional, and the only way to find out is to boot the trimmed configuration.
