It is more useful to allow to specify not a tag but a pattern or template that can refer to container id and name so both can present in logs.

Would really love an option like this!

@LK4D4 any chance you can review this. The design is based on your suggestions.

@ibuildthecloud #12422 was merged, can you rebase this PR?

Will do, thanks

Very useful feature!

@ibuildthecloud could you please rebase this due to #12422 is now merged? also this will be kinda related to #13362

@runcom and (at least, I suggested), related to #12876, because that PR also has a way to specify the "tag" for logging. Would be nice to have a consistent UX for defining the tag among the various log-drivers

@thaJeztah thanks for pointing to that, will keep that in mind. Now just wait @ibuildthecloud to rebase because many things changed here. And btw yes, would be cool to have something just for the tag option because other -log-opt are needed for other thinghies such as defining network hosts, ports etc etc per log driver

I still think it's good to define via --log-opt, just that if it's done that way, it would be nice if all drivers used the same convention (where possible). I don't think a dedicated flag should be added just for the 'tag'.

@ibuildthecloud I'll carry this for you. Thanks for work! Sorry for all that bikeshedding.