Configuration file will not generate, and agent is in boot loop (happens immediately after initial installation.)

[tbmedia]

What's wrong?

When I attempt to follow the instructions step-by-step, the tool repeatedly fails.

Specifically, I install the Grafana extension through the Docker Desktop application, and it generates without a configuration. When I attempt to provide my details provided by Grafana to link my account to my docker instance, it simply hangs and never progresses.

The error indicates that the configuration file is not being generated. "error loading config file /etc/agent-config/config.yaml: error reading config file open /etc/agent-config/config.yaml: no such file or directory"

Steps to reproduce

Open a cleanly installed Docker Desktop on Windows 10. Go to "Extensions" and find "Grafana Cloud Integration". Click Install. Attempt to enter the code provided through Grafana Cloud. This will not work, and the following error is thrown on the logs: "error loading config file /etc/agent-config/config.yaml: error reading config file open /etc/agent-config/config.yaml: no such file or directory" The second container named "grafana-docker-desktop-extension-agent" will be in a restart loop. The first container ("service") will be running just fine.

Uninstalling does not help. Uninstalling and closing Docker Desktop does not help. Uninstalling, closing docker desktop, and restarting the entire physical machine does not help. Turning off extensions completely (wiping the data), and then turning it back on does not help.

System information

Docker Desktop 4.24.2 running on Windows 10 Pro

Software version

grafana agent 0.32.1 (auto installed through Docker Desktop)

Configuration

I do not have a configuration, which is why the error is being thrown. This is supposed to be auto generated (plausably with the provided information from Grafana Cloud, which I've attempted many times to provide), so far as I know. This is likely the solution I need, though! I'd love to create one with a little help to bypass this problem.

Logs

2023-10-27 14:09:54 2023/10/27 21:09:54 error loading config file /etc/agent-config/config.yaml: error reading config file open /etc/agent-config/config.yaml: no such file or directory
2023-10-27 14:25:35 2023/10/27 21:25:35 error loading config file /etc/agent-config/config.yaml: error reading config file open /etc/agent-config/config.yaml: no such file or directory
2023-10-27 14:25:35 2023/10/27 21:25:35 error loading config file /etc/agent-config/config.yaml: error reading config file open /etc/agent-config/config.yaml: no such file or directory
2023-10-27 14:25:36 2023/10/27 21:25:36 error loading config file /etc/agent-config/config.yaml: error reading config file open /etc/agent-config/config.yaml: no such file or directory
2023-10-27 14:25:37 2023/10/27 21:25:37 error loading config file /etc/agent-config/config.yaml: error reading config file open /etc/agent-config/config.yaml: no such file or directory
2023-10-27 14:25:38 2023/10/27 21:25:38 error loading config file /etc/agent-config/config.yaml: error reading config file open /etc/agent-config/config.yaml: no such file or directory
2023-10-27 14:25:40 2023/10/27 21:25:40 error loading config file /etc/agent-config/config.yaml: error reading config file open /etc/agent-config/config.yaml: no such file or directory
2023-10-27 14:25:44 2023/10/27 21:25:44 error loading config file /etc/agent-config/config.yaml: error reading config file open /etc/agent-config/config.yaml: no such file or directory
2023-10-27 14:25:50 2023/10/27 21:25:50 error loading config file /etc/agent-config/config.yaml: error reading config file open /etc/agent-config/config.yaml: no such file or directory
2023-10-27 14:26:03 2023/10/27 21:26:03 error loading config file /etc/agent-config/config.yaml: error reading config file open /etc/agent-config/config.yaml: no such file or directory
2023-10-27 14:26:29 2023/10/27 21:26:29 error loading config file /etc/agent-config/config.yaml: error reading config file open /etc/agent-config/config.yaml: no such file or directory
2023-10-27 14:27:21 2023/10/27 21:27:21 error loading config file /etc/agent-config/config.yaml: error reading config file open /etc/agent-config/config.yaml: no such file or directory
2023-10-27 14:28:21 2023/10/27 21:28:21 error loading config file /etc/agent-config/config.yaml: error reading config file open /etc/agent-config/config.yaml: no such file or directory
2023-10-27 14:29:21 2023/10/27 21:29:21 error loading config file /etc/agent-config/config.yaml: error reading config file open /etc/agent-config/config.yaml: no such file or directory

[tbmedia]

If it helps, this is the error it throws after I uninstall, then attempt to reinstall without restarting my machine:

"Extension was not installed. Reason: installation could not be completed due to: forwarding VM socket "/run/guest-services/grafana_docker-desktop-extension/grafana-docker-desktop-extension.sock" to "\\.\pipe\dockerExtensions-grafana_docker-desktop-extension-grafana-docker-desktop-extension": open \.\pipe\dockerExtensions-grafana_docker-desktop-extension-grafana-docker-desktop-extension: Access is denied."

[github-actions[bot]]

This issue has not had any activity in the past 30 days, so the needs-attention label has been added to it. If the opened issue is a bug, check to see if a newer release fixed your issue. If it is no longer relevant, please feel free to close this issue. The needs-attention label signals to maintainers that something has fallen through the cracks. No action is needed by you; your issue will be kept open and you do not have to respond to this comment. The label will be removed the next time this job runs if there is new activity. Thank you for your contributions!

[aditya-konarde]

Pulling this into current quarter so that we can triage and address.

[mshahzeb]

This error is related to grafana-agent

The extension was updated to use alloy around 6 months ago. https://github.com/grafana/grafana-docker-desktop-extension/commit/b99e3b3220b4c5eddaf7116921f187d7478967c3

This should not be an issue in the latest version with alloy.