[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2421: connect tahoe-lafs repo to Docker Hub

[Tahoe-LAFS]

#2421: connect tahoe-lafs repo to Docker Hub
------------------------------------+------------------------------------
     Reporter:  daira               |      Owner:  warner
         Type:  defect              |     Status:  new
     Priority:  normal              |  Milestone:  undecided
    Component:  dev-infrastructure  |    Version:  1.10.0
   Resolution:                      |   Keywords:  docker security github
Launchpad Bug:                      |
------------------------------------+------------------------------------

Comment (by warner):

 Ok, I think I've got things wired up.
 https://registry.hub.docker.com/u/dockertahoe/tahoe-lafs/ shows a new
 Docker build each time we push a change to github master. My remaining
 questions:

 * Can we have this live in Dockerhub's tahoe-lafs/tahoe-lafs instead of
 dockertahoe/tahoe-lafs ? I can see that the Dockerhub "dockertahoe"
 account is a member of the Dockerhub "tahoe-lafs" organization, but I
 don't see any way to put images in that location.

 * The current build (of github "master") has a "Tag Name" of "latest". I
 assume we should offer a container with the current git trunk, and a
 different container with the most recent release. What is the Docker
 naming convention here? Does "latest" imply unreleased software? Should we
 use "latest" to point at e.g. 1.10.1, and "dev" or something to point at
 current git master?

 I think I need amontero to answer these two.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2421#comment:5>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage