Kernel provenance and runtime identification — Docker Desktop 4.91.0

Hello Docker Support,

For Docker Desktop 4.91.0, build 239619, on Mac with Apple silicon, could you provide official public references for:

  1. Kernel build provenance: A verifiable mapping from this release to the exact kernel binary’s cryptographic digest, source revision, ordered patches, final configuration and build toolchain.

  2. Runtime identification: A supported method, under a trusted-host model, to establish that the kernel loaded for a particular Linux VM boot corresponds to that binary. Please distinguish what version strings or build IDs establish from what they do not, and identify any required trust assumptions.

If either mapping is unavailable, please clarify the limitation. We are seeking public documentation only, without sharing diagnostic logs or private information.

Thank you.

HI. We are a Docker community, not the Docker Support (even if they ar visiting the forum occasionally)

Can you explain your goal without sharing any “private information”? Your post looks like at leats partially generated and at least for me, it does not make it clear what you are exactly looking for.

If you can describe some context, someone might be able to give you some pointers, but the two points give me the impression of looking for something that Docker Desktop was not made for. It is just for development to be able to work with Docker in a small virtual machine and use some useful extension that helps during development.

Thanks, fair point. The first post was too formal and didn’t explain what I was trying to do. Sorry for addressing it to Docker Support rather than the community.

I’m using Docker Desktop on an Apple silicon Mac for local development and repeatable tests. I want to record which Linux kernel the tests actually ran on, and trace it back to the kernel shipped with that Desktop release. I’m assuming the Mac itself is trusted, not trying to prove that a compromised machine is safe.

Is there a documented link from a Desktop release to the kernel binary and its source/build configuration? And is there a supported way to match the running VM’s kernel to that binary, beyond the version string?

I may be asking for more detail than Desktop exposes. If that’s the case, knowing that limitation would help too. A pointer to the right docs would be much appreciated.

It looks like I forgot about this topic.

There is no Docker Desktop documentation for what you want as it is just a Linux in a virtual machine. If you want to learn about kernel configuration, you can use the standard Linux commands in a container like

docker run --rm -it bash zcat /proc/config.gz

Or to filter out comments:

docker run --rm -it bash zcat /proc/config.gz | grep -v '^#'