* docker scan: using an HTTP proxy
Explain how to use an HTTP proxy in `docker scan`. It's confusing
because it doesn't use the same settings as the engine, the CLI
or Docker Desktop.
Signed-off-by: David Scott <dave.scott@docker.com>
* Update engine/scan/index.md
Clarify proxy:port as proxyAddress:port
Co-authored-by: Paweł Gronowski <me@woland.xyz>
* Update engine/scan/index.md
Capitalize PowerShell
Co-authored-by: Paweł Gronowski <me@woland.xyz>
Co-authored-by: Paweł Gronowski <me@woland.xyz>
- Add missing code-hints (console, yaml)
- Consistently add an empty line after code-blocks
- Combine some examples where the output and the command were
put in separate blocks. With the "console" code-hint, this
is no longer nescessary.
- fix indentation in cloud/ecs-integration.md, which caused the
numbered-list to be interrupted.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
* Change the repository link to open an issue on docker scan plugin
Signed-off-by: Guillaume Lours <guillaume.lours@docker.com>
* Remove the statement on trials
Co-authored-by: Usha Mandya <47779042+usha-mandya@users.noreply.github.com>
See https://web.dev/external-anchors-use-rel-noopener/
Using noopener, as that addresses the security issue. "noreferer" blocks
the REFERER header, which may still be useful for some target URLs.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Allie Sadler