I’ll start:

When I was first learning to use Docker, I didn’t realize that most tutorials that include a database don’t configure the database to persist. Imagine my surprise when I couldn’t figure out why the database kept getting wiped!

  • vegetaaaaaaa@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 year ago

    I prefer this method:

    {
      "log-driver": "syslog",
      "log-opts": {
        "tag": "docker.{{.Name}}"
      }
    }
    

    This way container logs are forwarded to /var/log/syslog, which already contains all other services logs, and has sane rotation rules by default (and it allows rsyslog to manage log forwarding/shipping if needed).

    • object_Object@programming.dev
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      Thanks, good to know! I had no idea about the tags. Looks like there’s a lot more variables available.

      I just reread the docs on the log drivers - they mentioned that as of docker 20.x local logs now work with all drivers as it buffers the logs locally as well. I think this is probably why I hadn’t explored the other drivers before - couldn’t use docker-compose logs.