tools/stx/stx-build-tools-chart/stx-builder
Davlet Panech b11b136df0 debian: docker-in-docker: override --mtu
Docker-in-docker pod doesn't work in some k8s environments because it
always assumes MTU=1500, even when k8s container network's MTU is
smaller than that. This causes downloads to fail intermittently in
containers that run within the internal docker.

Solution: allow option to override MTU in docker helm chart & the stx
tool.

Also: remove explicit reference to dockerd entry point script from the
helm chart because its name may change in future docker image versions.

TESTS
=======================================
Make sure "--mtu" is passed or omitted when starting docker daemon
depending on whether STX_CONTAINER_MTU is defined.

Story: 2010055
Task: 45691

Signed-off-by: Davlet Panech <davlet.panech@windriver.com>
Change-Id: Iaee08ee8d568d28fe9e8cdc11f0308aa9ff32d42
2022-06-28 15:43:35 -04:00
..
configmap debian: define extra env vars for docker apps 2022-04-26 10:52:05 -04:00
dependency_chart debian: docker-in-docker: override --mtu 2022-06-28 15:43:35 -04:00
templates debian: better resolv.conf in builder containers 2022-04-22 11:58:49 -04:00
.gitignore gitignore build artifacts 2022-03-04 13:59:05 -05:00
.helmignore stx tool: control: Add the support of control module 2021-09-15 21:35:47 -04:00
Chart.yaml debian: add Docker service to helm chart 2022-03-10 13:32:37 -05:00
values.yaml debian: better resolv.conf in builder containers 2022-04-22 11:58:49 -04:00