Reset to the state according to the state of Gentoo upstream,
to commit b93160fedf4e7a6f7f4101dfb7f3ff0df5cee2c0.
to create Flatcar patches on top of that.
Docker client and daemon started to fail at sending or handling most
local connections when being compiled with Go 1.19.11, which addresses
CVE-2023-29406 by blocking invalid host headers of HTTP/1. As a
workaround, Docker started to define a dummy host header, and to use
it for local connections.
Backport the fixes to Flatcar to fix the runtime failures.
See also https://github.com/moby/moby/issues/45935,
https://github.com/moby/moby/pull/45942.
Reset to the state according to the state of Gentoo upstream,
to commit 964117a9a27f8c048d646f423ffaf09b57bfad00,
to create Flatcar patches on top of that.
The official release variable is used to decide whether a build ID gets
appended to the FLATCAR_VERSION (or VERSION in os-release) or not. It
was set for the image job but not for the vms job, causing the
build_sysext script to get the build ID appended to the FLATCAR_VERSION
which causes a mismatch with the one from the image job.
Set the official release variable in the vms job as well.
The ci-cleanup file gets created in ci-automation/ to remove any
leftovers when a build gets stopped. Since it is in the git tree, git
status sees untracked files which is a bit confusing.
Ignore the ci-cleanup file.
When running the build_packages script, one can encounter an error such as
'Error fetching binhost package info from.' This pertains to SDK packages (not
board packages). Since we have transitioned to the SDK container, the SDK
packages are no longer published independently from the container image.
- Mark the package as stable.
- Remove the socket unit's rate limiting.
- Fixes to configuration handling. We are trying to upstream these
changes, so this package will be eventually moved to
portage-stable. But updating it in coreos-overlay for now to drop
the use of the obsolete cygwin USE flags.
Upstream PR: https://github.com/gentoo/gentoo/pull/31615
It's from Gentoo commit 7a8c3fa265d02fa74b8881a4dca3cfeb9d8a938c.
The modifications we did were upstreamed (under different USE flags
that we already properly set up), so no point it keeping the package
in overlay.
