AhmadMS1988

We do not want to run it in privileged mode.

It worked actually, but still the purpose to run it without privileged.

One question comes to my mind, as we by default use the oci worker, what is this containerd mount?

Is there any logs or commands that I can execute to help investigating more?

It worked as expected on both Amazon linux 2 and Ubuntu EKS optimized images based on 20.04. The output of /proc/mounts is: ``` overlay / overlay rw,context="system_u:object_r:data_t:s0:c208,c287",relatime,lowerdir=/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/71/fs:/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/59/fs:/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/55/fs:/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/50/fs:/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/45/fs:/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/40/fs,upperdir=/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/425/fs,workdir=/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/425/work 0 0 proc...

Unfortunately, it did not work. I got the same error.

@reta no special timeouts is configured. We use the client with its default configuration. The client works as expected then suddenly all opensearch requests will return the previous error immediately....

@koushyk I suppose it is still not working. @bcressey @stmcginnis I have opened [this](https://github.com/moby/buildkit/issues/4667) ticket with buildkit team about running it in rootless without privileged mode as it is still...

Any chance this can be included in with aws-k8s-1.30?

Bottlerocket has that enabled now for all 1.33 images, so I think it should be safe to proceed.