Passing the socket (and in the future there's no guarantee it's a socket) to every job works until there's a second attribute related to the docker connection.  It'd probably be better to describe a DockerConfiguration struct where the default object is equivalent to the default configuration (see http.RoundTripper and DefaulTransport for good examples where the default object a user creates does the right thing), and then pass that into the job.