Update clear-containers-image

[jodh-intel]

• The latest OBS clear-containers-image packages are for release 19350.
• My dev boxes are using clear-containers-image release 19790.

This seems to be due to the revert we had to do for testing on:

• versions: downgrade clear containers image runtime#890

However, we're now in a situation where we're not testing with the same image version we're providing to users (bad).

I think that we should potentially have pushed out an update to clear-containers-image to force a downgrade to release 19350. But can we even do that I wonder?

But things have moved on...

• https://download.clearlinux.org/latest shows 20460 at time of writing.
• Running scripts/get-image-changes.sh 20460 does show differences that we need.

@jcvenegas, @erick0z, @chavafg - I think we have 2 problems here:

1. Fix the issue that required versions: downgrade clear containers image runtime#890.

   @chavafg - do you think it's worth adding a special clear_vm_image_version_k8s= if we can't solve this issue? That would allow us to test with two image versions: one specifically for k8s, the other for all other tests.

2. Understand why we have not updated clear-containers-image to a much newer version than 19790 for users.

   @jcvenegas - do we need to add details of scripts/get-image-changes.sh to:
   https://github.com/clearcontainers/runtime/wiki/Release-Checklist ?

/cc @sameo, @grahamwhaley.

[jcvenegas]

@jodh-intel:

Understand why we have not updated clear-containers-image to a much newer version than 19790 for users.

@jcvenegas - do we need to add details of scripts/get-image-changes.sh to:
https://github.com/clearcontainers/runtime/wiki/Release-Checklist ?

edit:
Yes, we should add details about it. We are almost ready to have most of the Release-Checklist automated, and so as part of the automation we will pull the latest image always. I wll modify the documentation to reflect the automated process.

Both kernel and image will be published in github/releases then when a new release is done we take the latest kernel and latest image in github releases and add set as recommend for the new release.

With regarding to the image:

We should always use the latest image so If something causes the image not properly working we should revert the changes:

Seems that to have an stable agent and update image again we need:

• revert : clearcontainers/agent@e30849c
• tests and merge:
  agent: Fix sync issues with exit code and stdout of a process agent#197