jcvenegas

#!/bin/bash
# Note containerd should be installed and running.
# Install kata
curl  -o kata.tar.xz -L https://github.com/kata-containers/kata-containers/releases/download/2.2.0-alpha1/kata-static-2.2.0-alpha1-x86_64.tar.xz
sudo tar -xf kata.tar.xz -C /
# Add kata binaries to path to allow containerd find them
for b in /opt/kata/bin/* ; do
 ln -sf $b  /usr/local/bin/$(basename $b)
done
# Configure containerd

jcvenegas

use std::sync::atomic::AtomicBool;
use std::sync::atomic::Ordering;
use std::thread;

struct Lock {
    lock: AtomicBool,
}

impl Lock {
    fn lock(&self) {

jcvenegas

kubectl run -i --tty --attach --rm --image=ubuntu --overrides='{ "spec": { "runtimeClassName": "kata" } }' ubuntu

jcvenegas

#!/bin/bash

set -e

export ghprbPullId
export ghprbTargetBranch
export DEBUG=true
export CI="true"
export CI_JOB="CRI_CONTAINERD_K8S"
export SHIMV2_TEST="true"

jcvenegas

# Enable debug of kata (kata-deploy or default path
sudo sed -i 's/#enable_debug = true/enable_debug = true/g' /opt/kata/share/defaults/kata-containers/configuration.toml
sudo sed -i 's/#enable_debug = true/enable_debug = true/g' /usr/share/defaults/kata-containers/configuration.toml
here=$(date +'%Y-%m-%d %H:%M:%S')
# Run what is not working
# Example: docker run ...
journalctl -t kata-hypervisor -t kata-runtime -t virtiofsd  --since "${here}" -f | tee container_log

jcvenegas

#!/bin/bash

set -o errexit
set -o nounset
set -o pipefail
set -o errtrace

#az login;
vm_name="${1:-}"
if [ "${vm_name}" == "" ]; then

jcvenegas

{
  "setup": "20%"
}

jcvenegas

diff --git a/.ci/run.sh b/.ci/run.sh
index 32d8217..caf00a7 100755
--- a/.ci/run.sh
+++ b/.ci/run.sh
@@ -69,12 +69,6 @@ case "${CI_JOB}" in
                sudo -E PATH="$PATH" bash -c "make crio"
                ;;
        "CLOUD-HYPERVISOR")
-               echo "INFO: Containerd checks"
-               sudo -E PATH="$PATH" bash -c "make cri-containerd"

jcvenegas

http://jenkins.katacontainers.io/job/kata-containers-runtime-clh-minimal-ubuntu-hypervisor-log-stability-testing/23/consoleText

Cause:

Probably long time took to boot and wrong validation if workload is running and workload is listening: I have seen that if the workload is not listening curl will hang and not work.

Possible fixes: I see curl failed, if that happend that means that kubectl wait deployment and kubectl get pods ... | grep Running where done, but I dont see why if are done the runtime logs still are at start stage. Probably was valid but because I dont get at what time curl was launched confuces me .

jcvenegas

// Kata runtime example:
//  sudo journalctl -t kata-runtime -o json -f  | jq .MESSAGE | grep DEBUG --color
import "runtime/debug"

func stackLogger(logger logrus.Entry) {
        stack_bytes := debug.Stack()
        stack := string(stack_bytes)

        for _, l := range strings.Split(stack, "\n") {
                logger.Warnf("DEBUG -> %s", l)