This is fixed for my PR #2105

It is connected to my other PR in testcontainers testcontainers/testcontainers-java#7178

@eddumelendez I noticed that my initial implementation was wrong as I based it on documentation from docker cli not looking at real files on filesystem, this time I did full check and make it work with test container, so it should be fine to merge this and connected PR in testcontainers

Can you please share links to the documentation, etc as part of the PR description?

here is link to documentations https://github.com/docker/cli/blob/a0756c3c2cacebf5e5dc6454cc280c3ddf675176/docs/reference/commandline/context_inspect.md?plain=1#L42
but it is stored in filesystem in different way

some insight can be found in here https://github.com/docker/cli/blob/33c7baa7edf962559a07c1fb59581f863a7e8862/cli/context/store/store.go#L26

I think a need a clear description. Those links are not helping. Thanks

I don't know what kind of description you have in mind but let me summarised what happen.

Initial support for docker context was lacking support for TLS, so it was not working in case you want to use docker remote with TLS - this was initial support #2036

In attempt to extend it I created PR #2105, but I assumed that was is described as output of docker context inspect is in fact in files on disk.
I assumed that Storage section exists in file, but after you merged it and I tried to use it I noticed that in fact this information is only gather in runtime by docker cli which can be track to https://github.com/docker/cli/blob/33c7baa7edf962559a07c1fb59581f863a7e8862/cli/context/store/store.go#L26

In my next attempt (this PR) I dig dipper what in fact is stored in ~/.docker/contexts and there are two folders for metadata and for tls.

ls -1 ~/.docker/contexts
meta
tls

This PR is relying on folder structure to pick up TLS information and provide them to docker-java when context is used.

I hope it is enough, but if not, let me know what more I can do to make this merged

Thanks! Indeed, it helps. I wanted to clarify this before to continue.

Thanks for your contribution, @piotrwielgolaski-tomtom !