EKS Bottlerocket Support - CRIU Statically linked

[Siedlarczyk]

Hi,
I have been performing a few tests, and while running zeropod on EKS with Bottlerocket, I faced a problem with the CRIU binary, as it is probably dynamically linked in the imaged specified in the zeropod installer.

If supporting this is something this repo aims for, I'd be more than welcome to open and PR to fix this in order to suppor this.

[ctrox]

Yes, improving compatibility with more k8s distributions is always welcome. But with Bottlerocket there are probably other issues, it's similar to GKE's container OS where most of the root filesystem is read only. There the host-opt-path had to be modified to a writable (and executable) path: https://github.com/ctrox/zeropod/tree/main/config/gke

Can you tell me the error you see when installing?

[Siedlarczyk]

I have faced some issues regarding the RO FS from bottlerocket, this I have circled chaging the templates locally. But this is fine though.
Something I noticed is when using the CRIU binary for performing the snapshots, as it is dynamically linked, some .so libraries are not present, hence it will not perform the snapshot and the applications will fail.
Maybe compiling CRIU statically, and providing it as an option in the image you provide to install the user containerd install might be a alternative way for this.

But that being said, I can structure everything in a more clear way, and we can work on the PRs together it that is welcome.

Kudos on the project however!

[ctrox]

Thanks!

Something I noticed is when using the CRIU binary for performing the snapshots, as it is dynamically linked, some .so libraries are not present, hence it will not perform the snapshot and the applications will fail.
Maybe compiling CRIU statically, and providing it as an option in the image you provide to install the user containerd install might be a alternative way for this.

I once tried statically compiling CRIU but it's not that simple. There's this which we could adapt but I want to keep building CRIU here so we can patch it when needed (and include the existing patches in criu/). Alternatively, could you run ldd on the criu binary on bottle rocket to see what is missing?