[Meta] Hashicorp and Official Docker Images

[jason-riddle]

So as of today (7/29), there are an assortment of docker images for various tools.

Hashicorp Docker Images

• hashicorp/packer
  • This is an automated build.
  • This lives in https://github.com/hashicorp/docker-hub-images.
  • This has a full, latest, 0.10.0, and light tag.
• hashicorp/consul
  • This is an automated build.
  • This lives in https://github.com/hashicorp/docker-consul (the same repo as the official docker image).
  • This has a 0.6.4, v0.6.4, 0.6, and latest tag.
• hashicorp/terraform
  • This is an automated build.
  • This lives in https://github.com/hashicorp/docker-hub-images.
  • This has a full, latest, 0.6.14, and light tag.
• hashicorp/vault
  • This is NOT an automated build.
  • This does not link to a github repo.
  • This has no tags.

Official Docker Images

• library/consul
  • This is NOT an automated build.
  • This lives in https://github.com/hashicorp/docker-consul.
  • This has a latest and v0.6.4 tag.
• library/vault
  • This is NOT an automated build.
  • This lives in https://github.com/hashicorp/docker-vault.
  • This has a latest and v0.6.0 tag.

Also, nomad appears to be missing completely which I guess makes sense since if you decide to run a docker task within a docker container that might be a bit odd.

So is the plan to eventually have each tool live as an official docker image? Or will the hashicorp images still be maintained with the docker official images? I only ask because it looks certain efforts are being duplicated and other things are not consistent.

[n8behavior]

$ docker run -i -t hashicorp/terraform:light terraform
standard_init_linux.go:175: exec user process caused "no such file or directory"

My system

$ docker info
Containers: 4
 Running: 0
 Paused: 0
 Stopped: 4
Images: 23
Server Version: 1.12.0
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 33
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: null host bridge overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: apparmor seccomp
Kernel Version: 4.4.0-31-generic
Operating System: Ubuntu 16.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 15.57 GiB
Name: jackbox
ID: NWSH:ZHPA:KETS:UIKE:AMTZ:G2HJ:NOS3:TUKP:CUM3:Q4OD:W3GO:DDEJ
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Insecure Registries:
 127.0.0.0/8

This a physical machine. Also, same error using Macbook and Docker for Mac

Opened issue #13

[timfallmk]

@jason-riddle I can try and provide some context here as I was the one who created this project when I was at Hashi.

The original aim was to provide binary-equivalent access to HashiCorp tools for use on non-natively supported systems and for portability (and a number of other classic container use cases). Since most HashiCorp tools are not designed to run in a container environment, this would provide a bridge for that use case.

I tried to make the setup as automated as possible (since the design was quite simple, at least for the first pass), but was limited by the current HashiCorp deployment infrastructure. Everything is therefore done in this repo to centralize things.

The basic design for most apps is as you described. There are two versions, a build tagged version which simply pulls the source and builds the binary, and a light tagged version that pulls the pre-compiled binary for use. The light version was also tagged with it's version number for consistency and pinning. The one caveat (again, because of the way HashiCorp's build and release system is designed) was that new versions of each tool would need to be tagged by hand, along with triggering a new build. Hence someone has to manually touch this repo for each new release of any tool.

With the exception of the https://github.com/hashicorp/docker-consul image, which is in the official Docker repository and dutifully maintained by @slackpad , the images in this repo are rarely touched. I'm no longer at HashiCorp, so I can't bump them myself unfortunately. If you want to keep a more up to date pace, I would highly suggest forking this repo and triggering the automated Docker Hub builds yourself. I'm not sure HashiCorp is committed to accounting for container use.

While there are some major limitations to using nomad and vault in containers, you should be able to follow the process with the binaries to get them in containers if needed.

Hope that helps clear things up. Feel free to ping me if you have more questions.

[n8behavior]

That makes sense. I'll fork and give it a go. My team is shooting for a completely "install-less" toolset based on Docker. Thanks for the context!

[slackpad]

Hey everyone - we are definitely committed to supporting containers for our tools, and have been actively working on this on several fronts (we recently got an official image for Vault approved and published). I've been working to make the different teams aware that they need to bump this repo when official releases are cut, and we will work to clean up the consistency/overlap issues soon. Sorry for any confusion!

[acdha]

Has there been any update on version tracking? It's not clear from https://hub.docker.com/r/hashicorp/terraform/tags why the full/light versions are not the current release or when that will change.