Kaniko build fails on kind with "unlinkat /product_uuid: device or resource busy"

[mobs75]

Kaniko fails to clean up the build filesystem with unlinkat //product_uuid: device or resource busy — a known issue specific to kind clusters (GoogleContainerTools/kaniko#2164).

Fix: add --ignore-path=/product_uuid to the Kaniko executor args, right after --insecure-registry.

This is a documented upstream Kaniko issue, not something that needs investigation — just needs the flag added to olaris-op/kaniko-build.yaml (or wherever the executor args are defined) and it's resolved.

[sciabarracom]

hm but kaniko is no more used since a lot of time? where is happening?

[mobs75]

I see that it's not called from the root Taskfile.yml (which uses Buildx), it's still wired into olaris-op's own Taskfile.yml as an in-cluster build path:

build:
  cmds:
  - task: install-registry
  - task: tag-commit-push
  - task: kaniko-build
  - task: build-logs

So if you run task build from inside olaris-op directly (rather than from the superproject root), it still deploys a Kaniko build Job into the current cluster (kaniko-build.yaml), and that's where this fails on kind. You'd told me before that Kaniko shouldn't be used anymore (replaced by Docker Buildx), so I'm guessing this is just leftover code from before the migration that never got cleaned up in olaris-op/Taskfile.yml. If so, might be worth removing the whole kaniko-build/build-logs chain there instead of patching it. Happy to open a PR for that if you'd rather.