Overview
For starting Archivematica, using Docker was the easiest method. Installation instructions are documented at the following link.
https://github.com/artefactual/archivematica/tree/qa/1.x/hack
Following the steps worked well for installation, but I am documenting the points where I encountered failures as a memo.
Elasticsearch container
When starting the Elasticsearch container, instructions were given to set vm.max_map_count.
https://github.com/artefactual/archivematica/tree/qa/1.x/hack#elasticsearch-container
If this setting is forgotten, the Elasticsearch container would not start, as shown below.
docker compose up
[+] Running 10/0
✔ Container am-mysql-1 Running 0.0s
✔ Container am-archivematica-storage-service-1 Running 0.0s
✔ Container am-nginx-1 Running 0.0s
✔ Container am-clamavd-1 Running 0.0s
✔ Container am-elasticsearch-1 Created 0.0s
✔ Container am-fits-1 Running 0.0s
✔ Container am-gearmand-1 Running 0.0s
✔ Container am-archivematica-mcp-client-1 Running 0.0s
✔ Container am-archivematica-dashboard-1 Created 0.0s
✔ Container am-archivematica-mcp-server-1 Running 0.0s
Attaching to archivematica-dashboard-1, archivematica-mcp-client-1, archivematica-mcp-server-1, archivematica-storage-service-1, clamavd-1, elasticsearch-1, fits-1, gearmand-1, mysql-1, nginx-1
elasticsearch-1 | [2024-06-18T02:16:40,373][INFO ][o.e.e.NodeEnvironment ] [am-node] using [1] data paths, mounts [[/usr/share/elasticsearch/data (/dev/root)]], net usable_space [11.4gb], net total_space [48.2gb], types [ext4]
...
elasticsearch-1 | ERROR: [1] bootstrap checks failed
elasticsearch-1 | [1]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
...
dependency failed to start: container am-elasticsearch-1 exited (78)
Summary
Regarding Docker startup, it is noted that it is designed for developers, and care should be taken when using it in production environments. We hope this serves as a useful reference for using Archivematica.