dock VS recon

Just some friendly feedback: from the page you've linked to and this post, it's a little confusing to figure out what this is and why I should use it over the native Docker CLI. The GitHub page is a little more informative - even adding a framing headline like "A tool for using Docker containers as environments" or "Dock is a thin wrapper around the Docker CLI that makes Docker environments seamless" above the screenshot on your landing page would probably go a long way to communicating what your tool does and who should care.

I'm adding tests around the newest subcommand in dock, which is a thin wrapper around docker to streamline the use of Docker in a "development" context (as opposed to a deployment context). I recently added the run subcommand for running a command in the newest build of a Docker container, which will have certain configurable shortcuts, like running the command with the local user's ID, bind mounting the local project directory, and "nesting" the Docker daemon.

Hi /u/benzaita, thanks for sharing. I'm working on a tool with similar functionality (dock), so it's interesting to see a different approach in the same space. The features and Why use dockerized are great breakdowns of the advantages of this approach, and points that I've often made or observed myself, so it's great to have lists of these points to reference.