* 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>
These capabilities were reverted in a38b96b8cd,
because the version of containerd and runc that shipped together with
docker 20.10.0 did not support them.
Current versions of containerd and runc support these, so possibly we can
include them again in a patch release, but otherwise support will come in
the next (22.06) release of docker engine.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
These were notes about distro versions that have been EOL for a long
time, and an old version of docker engine that's EOL as well.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
containerd, docker engine and the docker cli were split into separate
packages in the 18.09 release. We kept this note on the release-notes
for current releases, but by now it's mostly "old news", so move the
warning to the 18.09 release notes page (which was the release in which
this change was made).
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
This warning has been in place for a Year, and while there's
still users running on this version of Ubuntu, it's not really
our responsibility to notify them about their distro version
being EOL.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
The "nightly" channel hasn't been updated for a long time, so while it's
not actively updated, we should not show instructions for it.
The "test" channel is still updated in preparation of new releases, but
including the instructions in between the regular installation procedure
introduced quite some "noise" that's irrelevant to most users (who would
be installing the "stable" channel).
This patch removes the instructions to enable the nightly and test channels
from the installation instructions.
While making these changes, I also synced somme wording between distros
for consistency, and removed a stray section about storage-drivers, as
that's already outlined in the "optional post-installation steps".
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
See https://tracker.debian.org/news/1305679/accepted-apt-240-source-into-unstable/:
* Install an empty /etc/apt/keyrings directory.
This directory is intended to provide an alternative to
/usr/share/keyrings for placing keys used with signed-by.
See also https://wiki.debian.org/DebianRepository/UseThirdParty?action=diff&rev2=47&rev1=46 (which was edited following a discussion with the APT maintainers about the expected usage):
> If future updates to the key will be managed by an apt/dpkg package as recommended below, then it SHOULD be downloaded into `/usr/share/keyrings` using the same filename that will be provided by the package. If it will be managed locally , it SHOULD be downloaded into `/etc/apt/keyrings` instead.
Signed-off-by: Tianon Gravi <admwiggin@gmail.com>
The example for setting the MTU on the swarm ingress network uses the wrong property:
`--opt com.docker.network.mtu=1200`
instead of
`--opt com.docker.network.driver.mtu=1200`
Dockertopia
Prabhav Thali
dockertopia
Takuya N
Slawka
NishantBanat
Jerae Duffin
CrazyMax
Justin Chadwell
Sebastiaan van Stijn
Allie Sadler
David Scott
Jared Boone
Fabio Guarini
Usha Mandya
Sebastiaan van Stijn
Usha Mandya
Tianon Gravi
Allie Sadler
Anca Iordache
Guillaume Lours
Guillaume Lours
halprin
Chris Crone
Mandraenke