If the packages or generated files installed in the Hermes Agent container are always gone, check the terminal.container_persistent first. If the container backend is not persisted, the file system may be destroyed with the session. Even if persisted, distinguish between "working directory volumes" and "container roots".
Let's look at the configuration first
In the official tooling documentation, container resource configuration includes container_persistent to determine whether the file system is persisted across sessions. The default idea is to keep the workspace through volume, rather than having the container root file system write infinitely.
Common causes
- Tasks write files to a temporary directory instead of a workspace.
- Container persistence is turned off and the next session is the new environment.
- The Docker mount path is not the same as the Hermes working directory.
- The package is installed on the temporary layer of the container and disappears naturally after the backend is rebuilt.
How to avoid
Let Hermes explicitly write the product to the project directory or mount directory; When caching dependencies are required, use a persistent container backend; Important artifacts are submitted to Git or copied to the host machine in a timely manner. The value of the container backend is isolation, not automatically saving all temporary files for you.
