Launching the profiler failed.

[mkchakra]

Using the latest version.

kubectl flame authz-7b995986b4-xddkf -n test -l java Verifying target pod ... ✔ Launching profiler ... ❌ pod failed

when i look into the pod logs i see this.

kubectl logs pods/kubectl-flame-57b65fbd-6667-48f5-9835-bb7f5fefc7c0-7tj95 -n test {"type":"progress","data":{"time":"2020-10-08T20:38:50.79538225Z","stage":"started"}} {"type":"error","data":{"reason":"open /var/lib/docker/image/overlay2/layerdb/mounts/f39d32b7755fd31190f3919a3e94870dd7147b5349dd3c268a85411af101184f/mount-id: no such file or directory"}}

any pointers for debugging this further what is happening.

[mkchakra]

I see the problem, it currently assuming that the storage driver is overlay2 while we are using aufs

[edeNFed]

You are correct. Supporting other storage drivers is planned for future release.

[dontmint]

I installed docker at a different path eg: /data/docker, please add a flag to specify this location

[joscabmar]

I am having this issue in AKS:

Verifying target pod ... ✔
Launching profiler ... ❌

When inspecting the logs in the kubectl flame pod:

kubectl logs kubectl-flame-cc7b0469-504b-4c90-a5b5-6dd797675d91-6c2lw
{"type":"progress","data":{"time":"2021-06-16T09:08:36.020796231Z","stage":"started"}}
{"type":"error","data":{"reason":"open /var/lib/docker/image/overlay2/layerdb/mounts/containerd://400e37fbed1e7a36429210bb1c9842bf94d2974ededfff703bd48bb78c810a1b/mount-id: no such file or directory"}}

[0x91]

looks like it doesn't support containerd