Cloudop's tooling for working with Docker images assumes adherence to https://github.com/mozilla-services/dockerflow . One component of is a file on disk at /app/version.json that adheres to this format: https://github.com/mozilla-services/Dockerflow/blob/master/docs/version_object.md. Please create this as part of your build process.

HI bstack, I just circled back to this.

Checking a sample version.json, I see

{"version": "v16.2.0", "commit": "bb08a08d5aa050680b22cd6fe227ac0339dd03ad", "source": "https://github.com/taskcluster/taskcluster", "build": "NONE"}

This won't work because the build field is empty. It needs to contain the URL of the build task on circleci or taskcluster so we can get the image digest from there.

You can see the code at https://github.com/mozilla-services/cloudops-infra-deploylib/blob/master/deploylib/docker.py

It isn't built in circle or tc at the moment, just manually. It looks like if we don't have build in the version.json it will just skip that step. Is that maybe the best plan or should we get working on making this build artifacts in tc?

Oh!

In that case for now we can just skip verification.

But definitely automating the image build somewhere is a win from numerous angles, like security and toil-reduction.