Skip to content
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

Steps direct one to configure logs but not sufficiently to avoid a warning later when running iotedge check #100762

Closed
drwill-ms opened this issue Oct 31, 2022 · 3 comments

Comments

@drwill-ms
Copy link

Why not prevent that later warning by including the configuration to enable circular logging. After running iotedge check and investigating that warning, I was recommended to use the following:

{
    "log-driver": "local",
    "log-opts": {
        "max-size": "10m",
        "max-file": "3"
    }
}

Document Details

Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

@RamanathanChinnappan-MSFT
Copy link
Contributor

@drwill-ms

Thanks for your feedback! We will investigate and update as appropriate.

@AshokPeddakotla-MSFT
Copy link
Contributor

@PatAltimore Please look into this feedback and update the doc as appropriate.

@PatAltimore
Copy link
Contributor

Hi @drwill-ms,

iotedge check will be changed in the referenced bug Azure/iotedge#6754. I'm going to request the doc bug be closed.

Thanks,
Pat

#please-close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants