You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 6, 2020. It is now read-only.
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:
From: @jodh-intel in clearcontainers/runtime#1086
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:
kata-containers/runtime#114 (comment)
To reduce this gap we should consider add to our ci an script that installs a go version defined in versions.txt file from runtime.