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.

Sign up for GitHub

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

Jump to bottom

Inconsistent paragraph #19988

Open
1 task done
jbmestelan opened this issue May 7, 2024 · 0 comments · May be fixed by #19846
Open
1 task done

Inconsistent paragraph #19988

jbmestelan opened this issue May 7, 2024 · 0 comments · May be fixed by #19846
Assignees
@dvdksn
Labels
area/networking Relates to anything around networking

Comments

@jbmestelan
Copy link

Is this a docs issue?

  • My issue is about the documentation content or website

Type of issue

Information is incorrect

Description

The sentence
If you're behind an HTTP or HTTPS proxy server, for example in corporate settings, the daemon proxy configurations must be specified in the systemd service file, not in the daemon.json file or using environment variables. makes little sense.

  • Obviously, we are behind an HTTP or HTTPS proxy server; that is the context of the article.
  • the previous sentence just made the point that the daemon.json file prevails; now we are told the opposite?

Location

https://docs.docker.com/config/daemon/systemd/

Suggestion

No response
@jbmestelan jbmestelan added the status/triage Needs triage label May 7, 2024
@dvdksn dvdksn linked a pull request May 13, 2024 that will close this issue
Open
@dvdksn dvdksn self-assigned this May 13, 2024
@dvdksn dvdksn added area/networking Relates to anything around networking and removed status/triage Needs triage labels May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dvdksn dvdksn

Labels
area/networking Relates to anything around networking
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: conflicting http proxy configuration for daemon dvdksn/docs
2 participants
@jbmestelan @dvdksn