That makes sense. This is generally not an issue in the same pod. The failures seem to happen when the docker daemon starts happen within a few milliseconds of each other in two containers in the same pod.
I missed that pipelines can themselves be part of a DAG, Configuration | Drone. So running the publish steps as parallel pipelines should allow us to work around this issue.
I will follow up with the dind folks if we keep seeing issues.