tahoe-lafs/Dockerfile

FROM python:2.7

ADD . /tahoe-lafs
RUN \
  cd /tahoe-lafs && \
  git pull --depth=100 && \
  make && \
  ln -vs /tahoe-lafs/bin/tahoe /usr/local/bin/tahoe

WORKDIR /root
Base Dockerfile initial version. 2015-05-10 14:07:48 +02:00			`FROM python:2.7`

move Dockerfile back to root. DockerHub can't handle it elsewhere. It looks like DockerHub's automated builds only have access to the subtree of the source checkout at+below the Dockerfile. Putting the Dockerfile in misc/build_helpers/ meant that the build process only had access to misc/build_helpers/, not the full source tree. 2015-06-07 14:30:58 -07:00			`ADD . /tahoe-lafs`
Base Dockerfile initial version. 2015-05-10 14:07:48 +02:00			`RUN \`
			`cd /tahoe-lafs && \`
Dockerfile: git-pull more history, to get a version string The Docker build process seems to use 'git pull --depth=1', which doesn't fetch enough history to see a tag, which means tahoe's setup.py can't compute a version (then 'tahoe --version' reports "unknown"). Pulling a hundred commits should be enough to see a tag without making the resulting image unnecessarily large. If we go more than 100 commits between tags, we'll need to increase this, or come up with something smarter. 2015-06-15 14:40:19 -07:00			`git pull --depth=100 && \`
Base Dockerfile initial version. 2015-05-10 14:07:48 +02:00			`make && \`
			`ln -vs /tahoe-lafs/bin/tahoe /usr/local/bin/tahoe`

			`WORKDIR /root`