docker-compose up -d fails on Raspberry Pi 4: unknown log opt 'max-size' for journald log driver

[Adri 'C-Fu' Mansor]

Trying to run nefarious for the first time on a Pi. Getting these errors:

`root@MaxPi:~/nefarious# docker-compose up -d
nefarious_transmission_1 is up-to-date
nefarious_redis_1 is up-to-date
Creating nefarious_watchtower_1 ... error
Creating nefarious_jackett_1 ...
Creating nefarious_celery_1 ...

Creating nefarious_jackett_1 ... error
ver

Creating nefarious_celery_1 ... error

ERROR: for nefarious_celery_1 Cannot create container for service celery: unknown log opt 'max-size' for journald log driver

ERROR: for watchtower Cannot create container for service watchtower: unknown log opt 'max-size' for journald log driver

ERROR: for jackett Cannot create container for service jackett: unknown log opt 'max-size' for journald log driver

ERROR: for celery Cannot create container for service celery: unknown log opt 'max-size' for journald log driver
ERROR: Encountered errors while bringing up the project.`

Not really sure what it means. I'm using dietpi as the OS, if that matters.

[lardbit]

Ah, ok so your docker installation defaulted to the journald logging driver which doesn't support the max-size logging parameter. I'll research a permanent solution, but, in the meantime, just delete the logging lines in docker-compose.base.yml (and docker-compose.transmission-vpn.yml if you're using the vpn).

So, delete all the occurrences of the following:

logging:
      options:
        max-size: 10m

Can you also tell me what this command returns so I can find a permanent solution?

docker info 2>/dev/null | grep "Logging Driver"

[Adri 'C-Fu' Mansor]

Sorry for the delay! Here ya go!

root@MaxPi:~# docker info 2>/dev/null | grep "Logging Driver"
 Logging Driver: journald

[lardbit]

Ok my suspicions were right. Your docker installation (journald vs json driver) doesn't support the max-size parameter so just delete that entire logging block I pasted above and then bring it all back up:

docker-compose up -d --force-recreate 

[lardbit]

I'm sure there's a way to enable that logging parameter but it's probably not worth the trouble

[lardbit]

Closing due to inactivity and a workaround that should work for docker installations without the json logging driver.