JSON entity files
JSON files are parsed as if each line is a single JSON object. This can be super helpful for getting a list of containers, for example; docker ps -a --format=json > /etc/OliveTin/containers.json.
Display names in JSON
OliveTin uses the first string value found in fields named title, name, id, hostname, host, or label as the instance name in the UI. Matching is case-insensitive. See Display names in the entities overview.
Docker’s JSON output uses Names, which is not one of those fields. Without title or name, OliveTin falls back to Docker’s ID field (matched as id) and shows the container ID instead of the human-readable name. Either map Names when generating the file (for example with jq to add a name field) or include an explicit title or name key in each object.
{"title":"media-indexing-container","ID":"4bafe6f9f956","Image":"fedora","State":"exited"}
{"title":"media-playback-container","ID":"d25f37c49c35","Image":"fedora","State":"exited"}docker ps --format=json lines (without title or name, OliveTin shows ID instead of Names){"Command":"\"/opt/entrypoint.sh\"","CreatedAt":"2024-02-08 15:27:42 +0000 GMT","ID":"4bafe6f9f956","Image":"fedora","Labels":"?","LocalVolumes":"0","Mounts":"","Names":"media-indexing-container","Networks":"bridge","Ports":"","RunningFor":"13 days ago","Size":"0B","State":"exited","Status":"Exited (128) 13 days ago"}
{"Command":"\"/opt/entrypoint.sh\"","CreatedAt":"2023-12-17 20:58:03 +0000 GMT","ID":"d25f37c49c35","Image":"fedora","Labels":"?","LocalVolumes":"0","Mounts":"","Names":"media-playback-container","Networks":"bridge","Ports":"","RunningFor":"27 days ago","Size":"0B","State":"exited","Status":"Exited (137) 27 days ago"}