fix(docs): add a note on docker configuration.md doc to explain accep…

[amirmotlagh]

…ted values for boolean type refering to issue #16014

What this PR does / why we need it:

Which issue(s) this PR fixes:
Fixes #16014

Special notes for your reviewer:

Checklist

• Reviewed the CONTRIBUTING.md guide (required)
• Documentation added
• Tests updated
• Title matches the required conventional commits format, see here
  • Note that Promtail is considered to be feature complete, and future development for logs collection will be in Grafana Alloy. As such, feat PRs are unlikely to be accepted unless a case can be made for the feature actually being a bug fix to existing behavior.
• Changes that require user attention or interaction to upgrade are documented in docs/sources/setup/upgrade/_index.md
• If the change is deprecating or removing a configuration option, update the deprecated-config.yaml and deleted-config.yaml files respectively in the tools/deprecated-config-checker directory. Example PR

[CLAassistant]

All committers have signed the CLA.

[JStickler]

[docs team] Thanks for taking the time to update the docs. Sorry it took me so long to get to the review, I was on vacation.

[JStickler]

@amirmotlagh Have you signed the CLA? Or possibly you've submitted this PR under a different email address than the one you've signed the CLA with?

[amirmotlagh]

@amirmotlagh Have you signed the CLA? Or possibly you've submitted this PR under a different email address than the one you've signed the CLA with?

The email address was not as same as my github email address. Now it is signed

[JStickler]

[docs team] LGTM, I'll just remove one unnecessary character and then merge.

[loki-gh-app]

The backport to release-3.3.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-16299-to-release-3.3.x origin/release-3.3.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x 2071a5098b4e5214fb8f8c646ae0081b39a563af

When the conflicts are resolved, stage and commit the changes:

git add . && git cherry-pick --continue

If you have the GitHub CLI installed:

# Push the branch to GitHub:
git push --set-upstream origin backport-16299-to-release-3.3.x
# Create the PR body template
PR_BODY=$(gh pr view 16299 --json body --template 'Backport 2071a5098b4e5214fb8f8c646ae0081b39a563af from #16299{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title 'fix(docs): add a note on docker configuration.md doc to explain accep… (backport release-3.3.x)' --body-file - --label 'size/L' --label 'type/docs' --label 'backport' --base release-3.3.x --milestone release-3.3.x --web

Or, if you don't have the GitHub CLI installed (we recommend you install it!):

# Push the branch to GitHub:
git push --set-upstream origin backport-16299-to-release-3.3.x

# Create a pull request where the `base` branch is `release-3.3.x` and the `compare`/`head` branch is `backport-16299-to-release-3.3.x`.

# Remove the local backport branch
git switch main
git branch -D backport-16299-to-release-3.3.x