versions: Update recommended golang version.

[jcvenegas]

Clear Containers CI uses go 1.9.4

Fixes: #1085

Signed-off-by: Jose Carlos Venegas Munoz jose.carlos.venegas.munoz@intel.com

[grahamwhaley]

Ubuntu CI failed - quick look at logs didn't show immediately why?

[jcvenegas]

@devimc ready to merge

[jodh-intel]

lgtm

[jodh-intel]

Actually, there are a couple of issues here:

• fwics we're building packages with go 1.7 fwics:

  https://github.com/clearcontainers/packaging/blob/master/.ci/setup.sh#L26

• The dev guide mention 1.8.3:

  https://github.com/clearcontainers/runtime/blob/master/docs/developers-clear-containers-install.md#requirements-to-build-individual-components

In summary:

• we're building packages with a very old version of go
• we're recommending developers build with an old version of go (but newer than the packaging version).
• we're testing with a newer (but not the latest) version of go.

We have a plan for how to resolve this for Kata but it's something we should be aware of I think:

• https://github.com/kata-containers/runtime/pull/114#issuecomment-376478713

/cc @sboeuf, @markdryan.

[jcvenegas]

@jodh-intel yes, that is one of the issues I see, first I want to reflect here the version we use to test. Today is not easy to test in the CI to a new golang version to check all works as expected. I added an script here https://github.com/clearcontainers/tests/pull/917/commits/af4ad939c2e60dab79b0f393f49ae355c8faef1f to allow change golang.

I require golang 1.10+ to allow cri-containerd in our CI.

[jodh-intel]

Nice - that would be useful in kata too. Let's merge this one then as a first-pass...