Doesn't this break docker logs calls? At least on 1.7? > On Oct 8, 2015, at 2:31 PM, Colin Walters <[email protected]> wrote: > > Hi, > > I was chatting with someone running Atomic Host whose / partition had filled > up due to a container logging going out of control. > > Since 1.7 docker has supported: > > https://docs.docker.com/reference/logging/journald/ > > And journald supports log file rotation based on disk space. Any objections > to just doing this by default? > > The main downside I can see is that your logs won't be automatically > migrated, so it could be surprising to people in a release stream. >
- [atomic-devel] Switching the default log driver to journal... Colin Walters
- Re: [atomic-devel] Switching the default log driver t... Tim St. Clair
- Re: [atomic-devel] Switching the default log driv... Tim St. Clair
- Re: [atomic-devel] Switching the default log driver t... Jason Brooks
- Re: [atomic-devel] Switching the default log driver t... Clayton Coleman
- Re: [atomic-devel] Switching the default log driv... Colin Walters
- Re: [atomic-devel] Switching the default log driver t... Joe Brockmeier
- Re: [atomic-devel] Switching the default log driv... Daniel J Walsh
- Re: [atomic-devel] Switching the default log driver t... Nick Coghlan
