Skip to content
This repository was archived by the owner on Jul 28, 2026. It is now read-only.

Getting started guide: correct the config file path - #299

Merged
rfratto merged 1 commit into
grafana-cold-storage:masterfrom
cityofships:fix_getting_started
Dec 29, 2020
Merged

Getting started guide: correct the config file path#299
rfratto merged 1 commit into
grafana-cold-storage:masterfrom
cityofships:fix_getting_started

Conversation

@cityofships

Copy link
Copy Markdown
Contributor

PR Description

The Dockerfile's CMD statement clearly expects the config file to be present at /etc/agent/agent.yaml location but following instructions in Getting Started guide gets potential user nowhere with error error loading config file /etc/agent/agent.yaml: error reading config file: open /etc/agent/agent.yaml: no such file or directory.

Which issue(s) this PR fixes

Notes to the Reviewer

PR Checklist

  • CHANGELOG updated
  • Documentation added
  • Tests updated

@CLAassistant

CLAassistant commented Dec 29, 2020

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@rfratto rfratto left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for fixing this! /etc/agent-config/agent.yaml is used in a bunch of other places correctly (e.g., where -config.file /etc/agent-config/agent.yaml is also passed explicitly as an arg), so it seems like a poorly handled copy and paste is responsible for this one.

@rfratto
rfratto merged commit 540bff4 into grafana-cold-storage:master Dec 29, 2020
@cityofships
cityofships deleted the fix_getting_started branch December 29, 2020 07:06
@mattdurham mattdurham mentioned this pull request Sep 7, 2021
3 tasks
mattdurham pushed a commit that referenced this pull request Nov 11, 2021
@github-actions github-actions Bot added the frozen-due-to-age Locked due to a period of inactivity. Please open new issues or PRs if more discussion is needed. label Apr 22, 2024
@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Apr 22, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

frozen-due-to-age Locked due to a period of inactivity. Please open new issues or PRs if more discussion is needed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants