/app/config.yaml is a directory

[stefano-medapps]

Running a fresh install of agentmemory using the readme instructions

npx @agentmemory/agentmemory

Docker container starts but crashes:

2026-04-14 16:24:09 Failed to load config file for logging: /app/config.yaml, using default local logging. Error: Failed to read config file '/app/config.yaml': Is a directory (os error 21)
2026-04-14 16:24:09 OpenTelemetry is disabled
2026-04-14 16:23:18 Error: Failed to read config file '/app/config.yaml': Is a directory (os error 21)

drwxr-xr-x@ 12 staff  staff   384B 14 Apr 16:10 .
drwxr-xr-x@  4 staff  staff   128B 14 Apr 16:09 ..
-rw-r--r--@  1 staff  staff   4.5K 14 Apr 16:05 AGENTS.md
drwxr-xr-x@ 27 staff  staff   864B 14 Apr 16:05 dist
-rw-r--r--@  1 staff  staff   325B 14 Apr 16:05 docker-compose.yml
drwxr-xr-x   2 staff  staff    64B 14 Apr 16:07 iii-config.docker.yaml
-rw-r--r--@  1 staff  staff   1.2K 14 Apr 16:05 iii-config.yaml
-rw-r--r--@  1 staff  staff    11K 14 Apr 16:05 LICENSE
-rw-r--r--@  1 staff  staff   2.0K 14 Apr 16:05 package.json
drwxr-xr-x@  6 staff  staff   192B 14 Apr 16:05 plugin
-rw-r--r--@  1 staff  staff    34K 14 Apr 16:05 README.md

Looks like iii-config.docker.yaml is not included in the npm package

[rohitg00]

You're right, that's a real bug. Reproduced and fixed in v0.8.7 (release notes).

What happened

The 0.8.6 tarball shipped `docker-compose.yml` but not `iii-config.docker.yaml`. The compose file mounts:

```yaml
volumes:

• ./iii-config.docker.yaml:/app/config.yaml:ro
  ```

Docker resolves missing host-path bind sources by silently creating them as empty directories. So when `npx @agentmemory/agentmemory` ran `docker compose up`, Docker created `iii-config.docker.yaml/` as an empty dir next to the compose file (exactly what your `ls` showed) and mounted that empty dir at `/app/config.yaml` inside the iii-engine container. The engine tried to open it as a file and got EISDIR. Brown-paper-bag — the `files` array in `package.json` was missing one line.

Fix

```bash
npm install -g @agentmemory/agentmemory@0.8.7

or

npx -y @agentmemory/agentmemory@0.8.7
```

Verified `package/iii-config.docker.yaml` is now in the published tarball at the package root.

Cleanup if you already hit this

Docker auto-created an empty directory named `iii-config.docker.yaml` wherever the broken 0.8.6 package was extracted (probably under your npm cache). It's safe to delete:

```bash
docker compose down -v # if you have a running stack from the broken install
rm -rf ~/.npm/_npx # let npx re-download a clean 0.8.7 copy
```

Then `npx -y @agentmemory/agentmemory@0.8.7` should come up clean.

Regression guard

Added a test that parses every bind mount in `docker-compose.yml` and asserts the source file is shipped via `package.json` `files`. CI will fail if anyone adds a new bind mount without a corresponding files entry. This class of bug can't reach a release again.

Thanks for the clean repro — the `ls` output with the directory entry was the giveaway.