Unable to CollectDump where Type != Full in Kubernetes

[pinkfloydx33]

I've got dotnet-monitor configured as a side car container running in Azure Kubernetes. Using the API I am able to successfully take a gcdump or trace and have it egress to Azure Blob Storage as well as to the File System. I am also able to do the same for dump if I specify type=Full. I am unable to collect a dump with any other type (i.e. WithHeap ) as it always end up with a FileNotFoundException with a message in the operation log similar to:

"Could not find file '/diag/dumps/16caa2fe-01b5-4f63-8329-cd7b2d8fd8d5_1'."

The dumps sub-folder gets created and a 0-byte file is created in the root of the /diag folder. I can use the File System egress to export gcdump or trace files to the /diag folder (or its sub-folders) so I don't see how it can necessarily be a permissions error (which is the only thing I've found in the documentation and in issues/discussions), plus Type=Full works just fine as well.

I've tried every possible combination of configuring securityContext; at the spec and container levels, setting fsGroup, overriding runAsUser and runAsGroup but nothing works. I always end up with the same failure.

Interestingly, I seem to have a similar problem as #6991. If I run the configuration as specified in #6991 (comment) then I can take a dump. However once I replace it with my application image it is no longer possible. Unlike #6991, I'm not running DataDog or anything like it.

For what it's worth:

• my application is:
  • an ASPNET 8.0, single-file/self-contained application
  • uses runtime-deps:8.0-bookworm-slim as it's base image
    • I've also tried with aspnet:8.0-bookworm-slim
  • runs as non-root (using the default APP_UID user)
• I've tried using monitor 8.0, 9.0 and latest
• I've tried falling back to root user / groups (via securityContext) on both containers

Does anyone have any ideas on what might be causing this, or something I can look into further?