-
Notifications
You must be signed in to change notification settings - Fork 487
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
grafana-agent-logs failing to boot on k3d #451
Comments
Thanks for reporting! I ran into this when working on #406 and worked around it by bind mounting that file to the k3d container: https://github.com/grafana/agent/blob/main/example/k3d/scripts/create.bash
|
I can confirm that I'm able to reproduce your problem with
(As long as /etc/machine-id exists on the host) That being said, I don't think it's an acceptable permanent workaround and the manifests should still be modified. |
Thanks for the quick response. I am able to work around it with the extra |
This issue has been automatically marked as stale because it has not had any activity in the past 30 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
This is the first issue I'm running into when testing Grafana Cloud. The issue should not be closed probably |
With latest loki yaml from README (run today):
Leave the
grafana-agent-logs
pods unable to start. Fromk describe
:but my
/etc/machine-id
file is the expected 32 character hex.The loki install worked on a k3d cluster last week on a cluster with
k3d cluster create grafana --servers 1 --agents 1
(when it was still called promtail).k3d
4.2.0,kubernetes 1.20.1
.The text was updated successfully, but these errors were encountered: