[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:  amontero
         Type:  defect              |     Status:  new
     Priority:  normal              |  Milestone:  undecided
    Component:  dev-infrastructure  |    Version:  1.10.0
   Resolution:                      |   Keywords:  docker security github
Launchpad Bug:                      |
------------------------------------+------------------------------------

Comment (by amontero):

 Replying to [comment:5 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.

 To achieve this, I've checked better and it happens that you need owner
 access to the organization repo (already granted). Simply delete the
 existing dockertahoe/tahoe-lafs and recreate it again, but selecting
 'tahoelafs' at the appropiate dropdown in the new automated build creation
 form.

 >
 > * 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?
 >
 ':latest' image tag is expected to point to latest stable release git tag.
 A ':devel' or something image tag could be set up to build from HEAD git
 branch.
 And a ':1.10.0' image tag pointing to 1.10.0 git tag and so on for other
 versions to allow people to base their derived images from specific image
 versions.
 But 'latest' and 'devel' tags are by no means a hard policy, just common
 practice. So, we can discuss here if you have other needs or intentions.

 > I think I need amontero to answer these two.

 Added to this, the name of the image could be tahoelafs/tahoe-lafs as you
 created or tahoelafs/base as I did. My intention with this was to have an
 unconfigured image with just the binaries and later create further images
 such as tahoelafs/introducer, tahoelafs/node and so on, all of them based
 from tahoelafs/base.
 It is recommended by Docker best practices to take advantage of Docker
 image layers as much as possible to save download time and size on disk.

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