All the podping.cloud hosts have their /etc/docker/daemon.json file set with:
{
"log-driver": "json-file",
"log-opts": {
"max-size": "100m",
"max-file": "5"
}
}
...but one log file was almost 9 gigs. I'm not sure how to make these settings actually take effect.
Dave /
npub1qx…kqf4d
2024-10-17 03:40:40
Author Public Key
npub1qx6kgzfm3z5qlffxnunsgnsaagwcxt6klx6q7gry56arj5r0yl3qgkqf4dPublished at
2024-10-17 03:40:40Event JSON
{
"id": "3eba1adaf43281c2cc114792d23fbb5b48de2d1931abd47fb13445b1c264a356",
"pubkey": "01b564093b88a80fa5269f27044e1dea1d832f56f9b40f2064a6ba39506f27e2",
"created_at": 1729136440,
"kind": 1,
"tags": [
[
"proxy",
"https://podcastindex.social/users/dave/statuses/113320685781746026",
"activitypub"
]
],
"content": "All the podping.cloud hosts have their /etc/docker/daemon.json file set with:\n\n{\n \"log-driver\": \"json-file\",\n \"log-opts\": {\n \"max-size\": \"100m\",\n \"max-file\": \"5\"\n }\n}\n\n...but one log file was almost 9 gigs. I'm not sure how to make these settings actually take effect.",
"sig": "93ed166ab970fac58126807caf287d71dd8fa50e30a2a463d36b751acf26deec6ad656dd610f7abeddb92698184cba525ccd6dd130c120a873c51d8df2f7809b"
}