Basically, a docker plugin is essentially this:

docker run -d -v /var/run/docker.sock:/var/run/docker.sock cpuguy83/something_crazy
And if you want to share that with people, in the instructions we are telling them to do the same thing, but not everyone necessarily uses the unix socket, and even if they do it may not be in this location.

In addition, for such a common pattern this is pretty silly.

Instead I propose that we can automatically bind mount a socket if requested using --plugin from the CLI.

docker run -d --plugin cpuguy83/something_crazy
This would have a default path for placing the socket in the container, but could potentially be customizable.