-
Notifications
You must be signed in to change notification settings - Fork 462
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iotedge check "container-engine-logrotate" should not require rotate options when driver is "local" #6754
Comments
I think we just need to add a match arm for "local" that behaves like the journald arm, here:
|
I've sent the PR for the journald part, but when looking deeper into it, it seems like all logging drivers, but the default json-file logger, do rotate logs automatically. So maybe the following would be better instead of a separate match of "local" driver:
|
…h is the default). This fixes Azure#6754 NOTE: All other logging driver usually do logrotation on their own
…h is the default). This fixes Azure#6754 NOTE: All other logging driver usually do logrotation on their own
…h is the default). This fixes Azure#6754 NOTE: All other logging driver usually do logrotation on their own
…h is the default). This fixes Azure#6754 NOTE: All other logging driver usually do logrotation on their own
…h is the default). This fixes Azure#6754 NOTE: All other logging driver usually do logrotation on their own
…h is the default). This fixes Azure#6754 NOTE: All other logging driver usually do logrotation on their own
…h is the default). This fixes Azure#6754 NOTE: All other logging driver usually do logrotation on their own
This issue is being marked as stale because it has been open for 30 days with no activity. |
Expected Behavior
iotedge check
should not warn me that the "Container engine is not configured to rotate module logs..." when I use Docker's local log driver. The container engine is configured to rotate module logs; the local driver provides default values formax-size
andmax-file
if the user does not explicitly give them.Current Behavior
IoT Edge docs recommend that I use Docker's local log driver. When I follow that recommendation by creating daemon.json like this:
...then the
iotedge
tool's "container-engine-logrotate" check emits a warning because I didn't explicitly add alog-opts
object withmax-file
andmax-size
values to daemon.json.Runtime Versions
iotedge version
]: 1.4docker version
]: any version that supports the local log driverAdditional Information
@drwill-ms originally filed this as doc issue MicrosoftDocs/azure-docs#100762. I'm filing this issue because I believe the fix should be made in
iotedge check
instead.The text was updated successfully, but these errors were encountered: