3 Commits (2c261eca0803c5eea2f1d1f1d6547304357e870f)

Author	SHA1	Message	Date
Martin Atkins	5c8ff928ba	build: scripted local build process for docker images ... #15596 set things up with the intent that the docker image build process would be handled by the automated build system on dockerhub, but after merging we found that it's impossible to change the source git repository for an existing dockerhub repository. To get away from the limitations of dockerhub, we intend to eventually automate these builds in a separate CI system. Here we add some scripts that would drive such an automated process. It's split into multiple steps to allow for situations where the new version should not be tagged as the latest, and to make it easier and safer to test the build script while doing development on it. Since this automated process doesn't yet exist, a wrapper script release.sh is included to help run a local, manual build and deploy process in the mean time. The README.md in the docker-release dir here contains details on the intended usage.	9 years ago
Martin Atkins	2b3b62dab5	build: documentation for the new docker image release process ... At the time of commit this file contains some things that are not yet true due to the dockerhub configuration not having been updated. This therefore remains aspirational until merged, after which the docherhub configuration will be updated.	9 years ago
Martin Atkins	0f9af4dfa9	build: configuration for building "release" docker images ... These are different than our "full" images because they include a binary already released to releases.hashicorp.com, whereas the root Dockerfile directly builds from the current work tree. This particular Dockerfile is not intended to be run manually, but rather exists only to drive the dockerhub automated build.	9 years ago