Updates:

[jacobweinstock]

Description

• Use latest v1.0.0 linuxkit images.
• Add images dir with runc and containerd to be able to better control the version.
• Use latest upstream init as it has cgroups v2 as the default.
• Add dhcp to the linuxkit services so that interfaces stay configured after lease times expire.
• Update to latest Docker in Docker version and update linuxkit spec to handle cgroups v2.
• Increase the kernel command line parameter size to 4096 bytes to allow for longer things to be passed like certs, etc.
• Default to linuxkit 1.2.0 binary as the containerd issues are resolved with the ccgroup v2 changes.

Why is this needed

Fixes: #

How Has This Been Tested?

How are existing users impacted? What migration steps/scripts do we need?

Checklist:

I have:

• [ ] updated the documentation and/or roadmap (if required)
• [ ] added unit or e2e tests
• [ ] provided instructions on how to upgrade

[chrisdoherty4]

What was the motivation for finer version control over runc and containerd?

[jacobweinstock]

What was the motivation for finer version control over runc and containerd?

Upstream moves a bit slow for me 😬 , in terms of getting to the latest versions. These additions were helpful in my troubleshooting but im not against removing them entirely if you have some concerns. There's enough trade-offs both ways for me to be fine with either approach.

[chrisdoherty4]

Presumably you mean upstream linuxkit, not upstream containerd? I.e. you're not trying to get some edge patch from containerd?

Assuming its linuxkit, I'm good with building given we're using official release tags/commits.

[jacobweinstock]

Presumably you mean upstream linuxkit, not upstream containerd? I.e. you're not trying to get some edge patch from containerd?

Assuming its linuxkit, I'm good with building given we're using official release tags/commits.

Yeah, upstream linuxkit.