[404]: /engine/reference/commandline/dockerd/

[Shylee1]

Location

https://www.docker.com/products/docker-desktop/settings/engine

Broken link

https://docs.docker.com/engine/reference/commandline/dockerd/?uuid=C89722DB-A37D-4348-AA8F-94AF5F754AA8

Comment

Docker Engine
v28.1.1
Configure the Docker daemon by typing a json Docker daemon [configuration file⁠](https://docs.docker.com/engine/reference/commandline/dockerd/).

This can prevent Docker from starting. Use at your own risk.

{
"builder": {
"gc": {
"defaultKeepStorage": "20GB",
"enabled": true
}
},
"experimental": false
}

[thaJeztah]

Interesting; the "location" where you found the broken link itself returns a 404 for me;
https://www.docker.com/products/docker-desktop/settings/engine

Where did you find that link?

[thaJeztah]

The https://docs.docker.com/engine/reference/commandline/dockerd/ URL looks indeed to be missing a redirect; it looks like that redirect was there, but stopped working? https://docs.docker.com/reference/cli/dockerd/

Link was found in the settings panel in docker desktop (which probably should've used a /go/ redirect), e.g. the existing /go/daemon/ or perhaps one specific for configuring the daemon 🤔

docs/data/redirects.yml

Lines 326 to 327 in d65261c

	"/reference/cli/dockerd/":
	- /go/daemon/

[thaJeztah]

Ah, looks like those were removed;

• desktop: go links #22765

@aevesdocker @ArthurFlag - was there a reason for removing the old redirects? I don't think we can, because existing product versions and websites will still use them

[aevesdocker]

@thaJeztah it's not been removed, just re-organized down below in that file 🤔

[aevesdocker]

@thaJeztah I see my mistake. Opening fix now

[thaJeztah]

Thanks!

[Shylee1]

Yea docker desktop personal, settings > engine > ….. then if ya hit the config button above the box, well I can’t remember but I think it might be broken too, but maybe not. Might check it just to be for sure

…

On Fri, Jun 6, 2025 at 5:44 AM Allie Sadler ***@***.***> wrote: Closed #22798 <#22798> as completed via #22800 <#22800>. — Reply to this email directly, view it on GitHub <#22798 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BIHEXCBIOJHCPDG5HRCAIQ33CFWINAVCNFSM6AAAAAB6XUQSV2VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJYGAZDANZTG43TSMA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[thaJeztah]

Thanks for confirming! Yes I found where it was coming from. We are in the process of updating such in-product links to use dedicated permalinks/redirects (e.g. https://docs.docker.com/go/daemon/) to make sure that we can keep those links up-to-date if content is moved in our docs.

But ironically, as part of changes related to that, we accidentally removed a redirect 😂. Thanks to your report, we discovered that case, so we added-back the redirect; #22800

[Shylee1]

Hey no worries, right on

…

On Fri, Jun 6, 2025 at 8:23 AM Sebastiaan van Stijn < ***@***.***> wrote: *thaJeztah* left a comment (docker/docs#22798) <#22798 (comment)> Thanks for confirming! Yes I found where it was coming from. We are in the process of updating such in-product links to use dedicated permalinks/redirects (e.g. https://docs.docker.com/go/daemon/) to make sure that we can keep those links up-to-date if content is moved in our docs. But ironically, as part of changes related to that, we accidentally removed a redirect 😂. Thanks to your report, we discovered that case, so we added-back the redirect; #22800 <#22800> — Reply to this email directly, view it on GitHub <#22798 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BIHEXCFM3DLZGFSPIEJ5IVD3CGI55AVCNFSM6AAAAAB6XUQSV2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNBZGI3DGNJQGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>