I am building OCI images from on EKS cluster with "t3.medium" instances, Containerd and RunC/Gvisor enabled from a Gitlab-CI Runner.
I use multi-stage build
With Gvisor OR RunC enabled, build is completed, and no errors in logs, then image is pushed on registry (Harbor).
The problem is then i want to PULL images from my running env (On EKS/Containerd, or on my local Desktop with Docker-CE).
Images builded with RunC are OK, but images builded with Gvisor can't extract layers after pull...
Logs from Containerd:
Pulling image "XXXXXXXXXXXXX/flask:v0.0.2"
Warning Failed 21s (x2 over 54s) kubelet Error: ErrImagePull
Warning Failed 21s kubelet Failed to pull image "XXXXXXXXXXXX/flask:v0.0.2": rpc error: code = Unknown desc = failed to pull and unpack image "XXXXXXXX/flask:v0.0.2": failed to extract layer sha256:58f32bc1a6f6c7d3216d04a43eb8f061cb73dd091a8d0700c1bfe6bbbbd0e1da: link /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/157/fs /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/157/fs/tmp: operation not permitted: unknown
Hello,
Actual behavior
I am building OCI images from on EKS cluster with "t3.medium" instances, Containerd and RunC/Gvisor enabled from a Gitlab-CI Runner. I use multi-stage build
This is my build stage:
With Gvisor OR RunC enabled, build is completed, and no errors in logs, then image is pushed on registry (Harbor). The problem is then i want to PULL images from my running env (On EKS/Containerd, or on my local Desktop with Docker-CE). Images builded with RunC are OK, but images builded with Gvisor can't extract layers after pull...
Logs from Containerd:
Logs from Docker:
Expected behavior No Pull error for OCI images builded with kaniko on Runc or Gvisor
To Reproduce Steps to reproduce the behavior:
Does kaniko still support Gvisor builds ?
Triage Notes for the Maintainers
--cache
flag