Not really (unfortunately). Kubernetes can leverage a number [1] of container runtimes - OpenShift uses CRI-O, for instance. There's also the problem that Docker can refer to a container runtime, orchestration engine (Swarm, which is analogous to k8s), CLI tools (`docker` and `docker-compose`), or HTTP API (registry). At my last few gigs the maintenance of separate configs for docker[-]compose and k8s has been a consistent pain point.

The container ecosystem is pretty complicated :-).

[1] https://kubernetes.io/docs/setup/production-environment/cont...