Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com>

[26.1] vendor: update buildkit to v0.13.2

Includes fix for HTTP fallback

Signed-off-by: Derek McGowan <derek@mcg.dev>
(cherry picked from commit eeec716)
Signed-off-by: Austin Vazquez <macedonv@amazon.com>

…5c058dfe70ddc0006d8552f632b2-to-26.1

[26.1 backport] vendor: update containerd to v1.7.16

If dockerd runs on a host with a read-only /proc/sys/net filesystem,
it isn't able to enable or disable IPv6 on network interfaces when
attaching a container to a network (including initial networks during
container creation).

In release 26.0.2, a read-only /proc/sys/net meant container creation
failed in all cases.

So, don't attempt to enable/disable IPv6 on an interface if it's already
set appropriately.

If it's not possible to enable IPv6 when it's needed, just log (because
that's what libnetwork has always done if IPv6 is disabled in the
kernel).

If it's not possible to disable IPv6 when it needs to be disabled,
refuse to create the container and raise an error that suggests setting
environment variable "DOCKER_ALLOW_IPV6_ON_IPV4_INTERFACE=1", to tell
the daemon it's ok to ignore the problem.

Signed-off-by: Rob Murray <rob.murray@docker.com>
(cherry picked from commit 01ea18f)
Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>

If env var DOCKER_BRIDGE_PRESERVE_KERNEL_LL=1, don't assign fe80::1/64
to a bridge, and don't delete any link local address with prefix fe80::/64.

Signed-off-by: Rob Murray <rob.murray@docker.com>
(cherry picked from commit 57ada4b)
Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>

[26.1 backport] Allow for a read-only "/proc/sys/net".

[26.1 backport] Option to avoid deleting the kernel_ll address from bridges.