# Meta details

Running `kata-collect-data.sh` version `1.4.1 (commit 45ea48e)` at `2019-02-07.09:55:57.859973091+0100`.

---

Runtime is `/usr/bin/kata-runtime`.

# `kata-env`

Output of "`/usr/bin/kata-runtime kata-env`":
```toml
[Meta]
  Version = "1.0.19"

[Runtime]
  Debug = true
  DisableNewNetNs = false
  Path = "/usr/bin/kata-runtime"
  [Runtime.Version]
    Semver = "1.4.1"
    Commit = "45ea48e"
    OCI = "1.0.1-dev"
  [Runtime.Config]
    Path = "/usr/share/defaults/kata-containers/configuration.toml"

[Hypervisor]
  MachineType = "pc"
  Version = "QEMU emulator version 2.11.0\nCopyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers"
  Path = "/usr/bin/qemu-lite-system-x86_64"
  BlockDeviceDriver = "virtio-scsi"
  EntropySource = "/dev/urandom"
  Msize9p = 8192
  MemorySlots = 10
  Debug = true
  UseVSock = false

[Image]
  Path = "/usr/share/kata-containers/ubuntu-tuan.img"

[Kernel]
  Path = "/usr/share/kata-containers/vmlinuz-4.14.67.22-6.container"
  Parameters = "agent.log=debug initcall_debug"

[Initrd]
  Path = ""

[Proxy]
  Type = "kataProxy"
  Version = "kata-proxy version 1.4.1-6553b83"
  Path = "/usr/libexec/kata-containers/kata-proxy"
  Debug = true

[Shim]
  Type = "kataShim"
  Version = "kata-shim version 1.4.1-6346110"
  Path = "/usr/libexec/kata-containers/kata-shim"
  Debug = true

[Agent]
  Type = "kata"

[Host]
  Kernel = "4.4.0-116-generic"
  Architecture = "amd64"
  VMContainerCapable = true
  SupportVSocks = false
  [Host.Distro]
    Name = "Ubuntu"
    Version = "16.04"
  [Host.CPU]
    Vendor = "GenuineIntel"
    Model = "Intel Core Processor (Skylake, IBRS)"

[Netmon]
  Version = "kata-netmon version 1.4.1"
  Path = "/usr/libexec/kata-containers/kata-netmon"
  Debug = true
  Enable = false
```

---


# Runtime config files


## Runtime default config files

```
/etc/kata-containers/configuration.toml
/usr/share/defaults/kata-containers/configuration.toml
```

## Runtime config file contents

Config file `/etc/kata-containers/configuration.toml` not found
Output of "`cat "/usr/share/defaults/kata-containers/configuration.toml"`":
```toml
# Copyright (c) 2017-2018 Intel Corporation
#
# SPDX-License-Identifier: Apache-2.0
#

# XXX: WARNING: this file is auto-generated.
# XXX:
# XXX: Source file: "cli/config/configuration.toml.in"
# XXX: Project:
# XXX:   Name: Kata Containers
# XXX:   Type: kata

[hypervisor.qemu]
path = "/usr/bin/qemu-lite-system-x86_64"
kernel = "/usr/share/kata-containers/vmlinuz.container"
#image = "/usr/share/kata-containers/kata-containers.img"
image = "/usr/share/kata-containers/ubuntu-tuan.img"
machine_type = "pc"

# Optional space-separated list of options to pass to the guest kernel.
# For example, use `kernel_params = "vsyscall=emulate"` if you are having
# trouble running pre-2.15 glibc.
#
# WARNING: - any parameter specified here will take priority over the default
# parameter value of the same name used to start the virtual machine.
# Do not set values here unless you understand the impact of doing so as you
# may stop the virtual machine from booting.
# To see the list of default parameters, enable hypervisor debug, create a
# container and look for 'default-kernel-parameters' log entries.
kernel_params = " agent.log=debug initcall_debug"

# Path to the firmware.
# If you want that qemu uses the default firmware leave this option empty
firmware = ""

# Machine accelerators
# comma-separated list of machine accelerators to pass to the hypervisor.
# For example, `machine_accelerators = "nosmm,nosmbus,nosata,nopit,static-prt,nofw"`
machine_accelerators=""

# Default number of vCPUs per SB/VM:
# unspecified or 0                --> will be set to 1
# < 0                             --> will be set to the actual number of physical cores
# > 0 <= number of physical cores --> will be set to the specified number
# > number of physical cores      --> will be set to the actual number of physical cores
default_vcpus = 1

# Default maximum number of vCPUs per SB/VM:
# unspecified or == 0             --> will be set to the actual number of physical cores or to the maximum number
#                                     of vCPUs supported by KVM if that number is exceeded
# > 0 <= number of physical cores --> will be set to the specified number
# > number of physical cores      --> will be set to the actual number of physical cores or to the maximum number
#                                     of vCPUs supported by KVM if that number is exceeded
# WARNING: Depending of the architecture, the maximum number of vCPUs supported by KVM is used when
# the actual number of physical cores is greater than it.
# WARNING: Be aware that this value impacts the virtual machine's memory footprint and CPU
# the hotplug functionality. For example, `default_maxvcpus = 240` specifies that until 240 vCPUs
# can be added to a SB/VM, but the memory footprint will be big. Another example, with
# `default_maxvcpus = 8` the memory footprint will be small, but 8 will be the maximum number of
# vCPUs supported by the SB/VM. In general, we recommend that you do not edit this variable,
# unless you know what are you doing.
default_maxvcpus = 0

# Bridges can be used to hot plug devices.
# Limitations:
# * Currently only pci bridges are supported
# * Until 30 devices per bridge can be hot plugged.
# * Until 5 PCI bridges can be cold plugged per VM.
#   This limitation could be a bug in qemu or in the kernel
# Default number of bridges per SB/VM:
# unspecified or 0   --> will be set to 1
# > 1 <= 5           --> will be set to the specified number
# > 5                --> will be set to 5
default_bridges = 1

# Default memory size in MiB for SB/VM.
# If unspecified then it will be set 2048 MiB.
default_memory = 2048
#
# Default memory slots per SB/VM.
# If unspecified then it will be set 10.
# This is will determine the times that memory will be hotadded to sandbox/VM.
#memory_slots = 10

# Disable block device from being used for a container's rootfs.
# In case of a storage driver like devicemapper where a container's 
# root file system is backed by a block device, the block device is passed
# directly to the hypervisor for performance reasons. 
# This flag prevents the block device from being passed to the hypervisor, 
# 9pfs is used instead to pass the rootfs.
disable_block_device_use = false

# Block storage driver to be used for the hypervisor in case the container
# rootfs is backed by a block device. This is either virtio-scsi or 
# virtio-blk.
block_device_driver = "virtio-scsi"

# Enable iothreads (data-plane) to be used. This causes IO to be
# handled in a separate IO thread. This is currently only implemented
# for SCSI.
#
enable_iothreads = false

# Enable pre allocation of VM RAM, default false
# Enabling this will result in lower container density
# as all of the memory will be allocated and locked
# This is useful when you want to reserve all the memory
# upfront or in the cases where you want memory latencies
# to be very predictable
# Default false
#enable_mem_prealloc = true

# Enable huge pages for VM RAM, default false
# Enabling this will result in the VM memory
# being allocated using huge pages.
# This is useful when you want to use vhost-user network
# stacks within the container. This will automatically 
# result in memory pre allocation
#enable_hugepages = true

# Enable swap of vm memory. Default false.
# The behaviour is undefined if mem_prealloc is also set to true
#enable_swap = true

# This option changes the default hypervisor and kernel parameters
# to enable debug output where available. This extra output is added
# to the proxy logs, but only when proxy debug is also enabled.
# 
# Default false
enable_debug = true

# Disable the customizations done in the runtime when it detects
# that it is running on top a VMM. This will result in the runtime
# behaving as it would when running on bare metal.
# 
#disable_nesting_checks = true

# This is the msize used for 9p shares. It is the number of bytes 
# used for 9p packet payload.
#msize_9p = 8192

# If true and vsocks are supported, use vsocks to communicate directly
# with the agent and no proxy is started, otherwise use unix
# sockets and start a proxy to communicate with the agent.
# Default false
#use_vsock = true

# VFIO devices are hotplugged on a bridge by default. 
# Enable hotplugging on root bus. This may be required for devices with
# a large PCI bar, as this is a current limitation with hotplugging on 
# a bridge. This value is valid for "pc" machine type.
# Default false
#hotplug_vfio_on_root_bus = true

# If host doesn't support vhost_net, set to true. Thus we won't create vhost fds for nics.
# Default false
#disable_vhost_net = true
#
# Default entropy source.
# The path to a host source of entropy (including a real hardware RNG)
# /dev/urandom and /dev/random are two main options.
# Be aware that /dev/random is a blocking source of entropy.  If the host
# runs out of entropy, the VMs boot time will increase leading to get startup
# timeouts.
# The source of entropy /dev/urandom is non-blocking and provides a
# generally acceptable source of entropy. It should work well for pretty much
# all practical purposes.
#entropy_source= "/dev/urandom"

# Path to OCI hook binaries in the *guest rootfs*.
# This does not affect host-side hooks which must instead be added to
# the OCI spec passed to the runtime.
#
# You can create a rootfs with hooks by customizing the osbuilder scripts:
# https://github.com/kata-containers/osbuilder
#
# Hooks must be stored in a subdirectory of guest_hook_path according to their
# hook type, i.e. "guest_hook_path/{prestart,postart,poststop}".
# The agent will scan these directories for executable files and add them, in
# lexicographical order, to the lifecycle of the guest container.
# Hooks are executed in the runtime namespace of the guest. See the official documentation:
# https://github.com/opencontainers/runtime-spec/blob/v1.0.1/config.md#posix-platform-hooks
# Warnings will be logged if any error is encountered will scanning for hooks,
# but it will not abort container execution.
#guest_hook_path = "/usr/share/oci/hooks"

[factory]
# VM templating support. Once enabled, new VMs are created from template
# using vm cloning. They will share the same initial kernel, initramfs and
# agent memory by mapping it readonly. It helps speeding up new container
# creation and saves a lot of memory if there are many kata containers running
# on the same host.
#
# When disabled, new VMs are created from scratch.
#
# Default false
#enable_template = true

[proxy.kata]
path = "/usr/libexec/kata-containers/kata-proxy"

# If enabled, proxy messages will be sent to the system log
# (default: disabled)
enable_debug = true

[shim.kata]
path = "/usr/libexec/kata-containers/kata-shim"

# If enabled, shim messages will be sent to the system log
# (default: disabled)
enable_debug = true

[agent.kata]
# There is no field for this section. The goal is only to be able to
# specify which type of agent the user wants to use.

[netmon]
# If enabled, the network monitoring process gets started when the
# sandbox is created. This allows for the detection of some additional
# network being added to the existing network namespace, after the
# sandbox has been created.
# (default: disabled)
#enable_netmon = true

# Specify the path to the netmon binary.
path = "/usr/libexec/kata-containers/kata-netmon"

# If enabled, netmon messages will be sent to the system log
# (default: disabled)
enable_debug = true

[runtime]
# If enabled, the runtime will log additional debug messages to the
# system log
# (default: disabled)
enable_debug = true
#
# Internetworking model
# Determines how the VM should be connected to the
# the container network interface
# Options:
#
#   - bridged
#     Uses a linux bridge to interconnect the container interface to
#     the VM. Works for most cases except macvlan and ipvlan.
#
#   - macvtap
#     Used when the Container network interface can be bridged using
#     macvtap.
#
#   - none
#     Used when customize network. Only creates a tap device. No veth pair.
#
#   - tcfilter
#     Uses tc filter rules to redirect traffic from the network interface
#     provided by plugin to a tap interface connected to the VM.
#
internetworking_model="macvtap"

# If enabled, the runtime will create opentracing.io traces and spans.
# (See https://www.jaegertracing.io/docs/getting-started).
# (default: disabled)
#enable_tracing = true

# If enabled, the runtime will not create a network namespace for shim and hypervisor processes.
# This option may have some potential impacts to your host. It should only be used when you know what you're doing.
# `disable_new_netns` conflicts with `enable_netmon`
# `disable_new_netns` conflicts with `internetworking_model=bridged` and `internetworking_model=macvtap`. It works only
# with `internetworking_model=none`. The tap device will be in the host network namespace and can connect to a bridge
# (like OVS) directly.
# If you are using docker, `disable_new_netns` only works with `docker run --net=none`
# (default: false)
#disable_new_netns = true
```

---


# KSM throttler


## version

Output of "`/usr/libexec/kata-ksm-throttler/kata-ksm-throttler --version`":
```
kata-ksm-throttler version 1.5.0-rc2-d70af5c
```

## systemd service


# Image details

```yaml
---
osbuilder:
  url: "https://github.com/kata-containers/osbuilder"
  version: "unknown"
rootfs-creation-time: "2019-02-06T14:47:52.982859595+0000Z"
description: "osbuilder rootfs"
file-format-version: "0.0.2"
architecture: "x86_64"
base-distro:
  name: "bionic"
  version: "18.04"
  packages:
    default:
      - "systemd,iptables,init,bash"
    extra:
      - "bash"
agent:
  url: "https://github.com/kata-containers/agent"
  name: "kata-agent"
  version: "1.5.0-17192be88b2725b0e7f482a8b7616935e1b1ddf4"
  agent-is-init-daemon: "no"
```

---


# Initrd details

No initrd

---


# Logfiles


## Runtime logs

Recent runtime problems found in system journal:
```
time="2019-02-04T16:46:17.24219002+01:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=e175f92153f6313b167e4fd80ae40218e8138b4d0d3f202d8d06aa0418c0df47 error="open /run/vc/sbs/e175f92153f6313b167e4fd80ae40218e8138b4d0d3f202d8d06aa0418c0df47/devices.json: no such file or directory" name=kata-runtime pid=11672 sandbox=e175f92153f6313b167e4fd80ae40218e8138b4d0d3f202d8d06aa0418c0df47 sandboxid=e175f92153f6313b167e4fd80ae40218e8138b4d0d3f202d8d06aa0418c0df47 source=virtcontainers subsystem=sandbox
time="2019-02-04T16:57:04.651025699+01:00" level=warning msg="Cannot hotplug 2 CPUs, currently this SB has 3 CPUs and the maximum amount of CPUs is 4" arch=amd64 command=update container=e175f92153f6313b167e4fd80ae40218e8138b4d0d3f202d8d06aa0418c0df47 name=kata-runtime pid=12109 sandbox=e175f92153f6313b167e4fd80ae40218e8138b4d0d3f202d8d06aa0418c0df47 source=virtcontainers subsystem=qemu
time="2019-02-05T12:37:53.921532916+01:00" level=error msg="Container e175f92153f6313b167e4fd80ae40218e8138b4d0d3f202d8d06aa0418c0df47 not ready, running or paused, cannot send a signal" arch=amd64 command=kill container=e175f92153f6313b167e4fd80ae40218e8138b4d0d3f202d8d06aa0418c0df47 name=kata-runtime pid=14751 sandbox=e175f92153f6313b167e4fd80ae40218e8138b4d0d3f202d8d06aa0418c0df47 source=runtime
time="2019-02-05T12:37:54.021156251+01:00" level=error msg="Container e175f92153f6313b167e4fd80ae40218e8138b4d0d3f202d8d06aa0418c0df47 not ready, running or paused, cannot send a signal" arch=amd64 command=kill container=e175f92153f6313b167e4fd80ae40218e8138b4d0d3f202d8d06aa0418c0df47 name=kata-runtime pid=14783 sandbox=e175f92153f6313b167e4fd80ae40218e8138b4d0d3f202d8d06aa0418c0df47 source=runtime
time="2019-02-05T12:38:00.616090738+01:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=2237dc195901dc7177472a667b7b0247c1d782261c9fe238957651ef6f770fde error="open /run/vc/sbs/2237dc195901dc7177472a667b7b0247c1d782261c9fe238957651ef6f770fde/devices.json: no such file or directory" name=kata-runtime pid=14981 sandbox=2237dc195901dc7177472a667b7b0247c1d782261c9fe238957651ef6f770fde sandboxid=2237dc195901dc7177472a667b7b0247c1d782261c9fe238957651ef6f770fde source=virtcontainers subsystem=sandbox
time="2019-02-05T12:39:02.166273874+01:00" level=warning msg="Cannot hotplug 4 CPUs, currently this SB has 1 CPUs and the maximum amount of CPUs is 4" arch=amd64 command=update container=2237dc195901dc7177472a667b7b0247c1d782261c9fe238957651ef6f770fde name=kata-runtime pid=15159 sandbox=2237dc195901dc7177472a667b7b0247c1d782261c9fe238957651ef6f770fde source=virtcontainers subsystem=qemu
time="2019-02-05T12:55:04.371985467+01:00" level=error msg="Container 2237dc195901dc7177472a667b7b0247c1d782261c9fe238957651ef6f770fde not ready, running or paused, cannot send a signal" arch=amd64 command=kill container=2237dc195901dc7177472a667b7b0247c1d782261c9fe238957651ef6f770fde name=kata-runtime pid=15270 sandbox=2237dc195901dc7177472a667b7b0247c1d782261c9fe238957651ef6f770fde source=runtime
time="2019-02-05T12:55:04.444065503+01:00" level=error msg="Container 2237dc195901dc7177472a667b7b0247c1d782261c9fe238957651ef6f770fde not ready, running or paused, cannot send a signal" arch=amd64 command=kill container=2237dc195901dc7177472a667b7b0247c1d782261c9fe238957651ef6f770fde name=kata-runtime pid=15309 sandbox=2237dc195901dc7177472a667b7b0247c1d782261c9fe238957651ef6f770fde source=runtime
time="2019-02-05T12:55:13.635708572+01:00" level=error msg="flag provided but not defined: -ti" arch=amd64 command=run name=kata-runtime pid=15367 source=runtime
time="2019-02-05T13:40:35.401075536+01:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=bd5032790a43ffca172e549ffcd0a765546b9c5a4cb9dbc27e3dc2d966727ca1 error="open /run/vc/sbs/bd5032790a43ffca172e549ffcd0a765546b9c5a4cb9dbc27e3dc2d966727ca1/devices.json: no such file or directory" name=kata-runtime pid=16348 sandbox=bd5032790a43ffca172e549ffcd0a765546b9c5a4cb9dbc27e3dc2d966727ca1 sandboxid=bd5032790a43ffca172e549ffcd0a765546b9c5a4cb9dbc27e3dc2d966727ca1 source=virtcontainers subsystem=sandbox
time="2019-02-05T16:11:47.3368131+01:00" level=error msg="Failed to connect to QEMU instance" arch=amd64 command=kill container=bd5032790a43ffca172e549ffcd0a765546b9c5a4cb9dbc27e3dc2d966727ca1 error="Lost connection to VM" name=kata-runtime pid=20282 source=virtcontainers subsystem=qemu
time="2019-02-05T16:11:47.33770613+01:00" level=error msg="Failed to unplug block device" arch=amd64 command=kill container=bd5032790a43ffca172e549ffcd0a765546b9c5a4cb9dbc27e3dc2d966727ca1 error="Lost connection to VM" name=kata-runtime pid=20282 source=virtcontainers subsystem=device
time="2019-02-05T16:11:47.339001814+01:00" level=error msg="Lost connection to VM" arch=amd64 command=kill container=bd5032790a43ffca172e549ffcd0a765546b9c5a4cb9dbc27e3dc2d966727ca1 name=kata-runtime pid=20282 source=runtime
time="2019-02-05T16:12:17.409410404+01:00" level=error msg="context deadline exceeded" arch=amd64 command=state container=bd5032790a43ffca172e549ffcd0a765546b9c5a4cb9dbc27e3dc2d966727ca1 name=kata-runtime pid=20316 source=runtime
time="2019-02-05T16:13:02.438458505+01:00" level=error msg="context deadline exceeded" arch=amd64 command=kill container=bd5032790a43ffca172e549ffcd0a765546b9c5a4cb9dbc27e3dc2d966727ca1 name=kata-runtime pid=20340 source=runtime
time="2019-02-05T16:13:47.466069563+01:00" level=error msg="context deadline exceeded" arch=amd64 command=delete container=bd5032790a43ffca172e549ffcd0a765546b9c5a4cb9dbc27e3dc2d966727ca1 name=kata-runtime pid=20382 source=runtime
time="2019-02-06T15:39:32.129356286+01:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=22ac4e7f3e6fbffc9ebd4560da00380d520eac816b086372c0d106421de2ca91 error="open /run/vc/sbs/22ac4e7f3e6fbffc9ebd4560da00380d520eac816b086372c0d106421de2ca91/devices.json: no such file or directory" name=kata-runtime pid=17399 sandbox=22ac4e7f3e6fbffc9ebd4560da00380d520eac816b086372c0d106421de2ca91 sandboxid=22ac4e7f3e6fbffc9ebd4560da00380d520eac816b086372c0d106421de2ca91 source=virtcontainers subsystem=sandbox
time="2019-02-06T15:39:52.268369473+01:00" level=error msg="Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing" arch=amd64 command=create container=22ac4e7f3e6fbffc9ebd4560da00380d520eac816b086372c0d106421de2ca91 name=kata-runtime pid=17399 source=runtime
time="2019-02-06T15:40:14.593225119+01:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=a7d55b22f39f4b34a2a4f6cc246db4e5ad5bcbb2158182b4f7fb955fd7dfebd5 error="open /run/vc/sbs/a7d55b22f39f4b34a2a4f6cc246db4e5ad5bcbb2158182b4f7fb955fd7dfebd5/devices.json: no such file or directory" name=kata-runtime pid=17691 sandbox=a7d55b22f39f4b34a2a4f6cc246db4e5ad5bcbb2158182b4f7fb955fd7dfebd5 sandboxid=a7d55b22f39f4b34a2a4f6cc246db4e5ad5bcbb2158182b4f7fb955fd7dfebd5 source=virtcontainers subsystem=sandbox
time="2019-02-06T15:40:34.728395956+01:00" level=error msg="Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing" arch=amd64 command=create container=a7d55b22f39f4b34a2a4f6cc246db4e5ad5bcbb2158182b4f7fb955fd7dfebd5 name=kata-runtime pid=17691 source=runtime
time="2019-02-06T15:53:17.270320125+01:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=db20c46ec9ad3854de96cba3ee088e30af4b046e8a2e744111dabf8073af23c0 error="open /run/vc/sbs/db20c46ec9ad3854de96cba3ee088e30af4b046e8a2e744111dabf8073af23c0/devices.json: no such file or directory" name=kata-runtime pid=26794 sandbox=db20c46ec9ad3854de96cba3ee088e30af4b046e8a2e744111dabf8073af23c0 sandboxid=db20c46ec9ad3854de96cba3ee088e30af4b046e8a2e744111dabf8073af23c0 source=virtcontainers subsystem=sandbox
time="2019-02-06T15:53:37.396379498+01:00" level=error msg="Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing" arch=amd64 command=create container=db20c46ec9ad3854de96cba3ee088e30af4b046e8a2e744111dabf8073af23c0 name=kata-runtime pid=26794 source=runtime
time="2019-02-06T16:01:28.425627092+01:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=3b1606142071581885f4d98288552dca152ab2d69e5292a88b545f000f8cf7a3 error="open /run/vc/sbs/3b1606142071581885f4d98288552dca152ab2d69e5292a88b545f000f8cf7a3/devices.json: no such file or directory" name=kata-runtime pid=27394 sandbox=3b1606142071581885f4d98288552dca152ab2d69e5292a88b545f000f8cf7a3 sandboxid=3b1606142071581885f4d98288552dca152ab2d69e5292a88b545f000f8cf7a3 source=virtcontainers subsystem=sandbox
time="2019-02-06T16:01:48.568325512+01:00" level=error msg="Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing" arch=amd64 command=create container=3b1606142071581885f4d98288552dca152ab2d69e5292a88b545f000f8cf7a3 name=kata-runtime pid=27394 source=runtime
time="2019-02-06T16:04:13.791602058+01:00" level=debug msg="Could not retrieve anything from storage" arch=amd64 command=create container=9a11ea34f2599b0a5aa7d81e0a8c913712533ec309dd5c808abebb6b97cb64bf name=kata-runtime pid=27635 source=virtcontainers subsystem=kata_agent
time="2019-02-06T16:04:13.794797911+01:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=9a11ea34f2599b0a5aa7d81e0a8c913712533ec309dd5c808abebb6b97cb64bf error="open /run/vc/sbs/9a11ea34f2599b0a5aa7d81e0a8c913712533ec309dd5c808abebb6b97cb64bf/devices.json: no such file or directory" name=kata-runtime pid=27635 sandbox=9a11ea34f2599b0a5aa7d81e0a8c913712533ec309dd5c808abebb6b97cb64bf sandboxid=9a11ea34f2599b0a5aa7d81e0a8c913712533ec309dd5c808abebb6b97cb64bf source=virtcontainers subsystem=sandbox
time="2019-02-06T16:04:13.799793236+01:00" level=debug arch=amd64 command=create container=9a11ea34f2599b0a5aa7d81e0a8c913712533ec309dd5c808abebb6b97cb64bf default-kernel-parameters="tsc=reliable no_timer_check rcupdate.rcu_expedited=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp reboot=k console=hvc0 console=hvc1 iommu=off cryptomgr.notests net.ifnames=0 pci=lastbus=0 root=/dev/pmem0p1 rootflags=dax,data=ordered,errors=remount-ro rw rootfstype=ext4 debug systemd.show_status=true systemd.log_level=debug" name=kata-runtime pid=27635 source=virtcontainers subsystem=qemu
time="2019-02-06T16:04:33.932339783+01:00" level=error msg="Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing" arch=amd64 command=create container=9a11ea34f2599b0a5aa7d81e0a8c913712533ec309dd5c808abebb6b97cb64bf name=kata-runtime pid=27635 source=runtime
time="2019-02-06T16:32:15.555281706+01:00" level=debug msg="Could not retrieve anything from storage" arch=amd64 command=create container=0b0652b7da928ff0f9bbdb27cc173cc76fb89a6e6075e6e9d923310071bb1127 name=kata-runtime pid=27938 source=virtcontainers subsystem=kata_agent
time="2019-02-06T16:32:15.558230397+01:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=0b0652b7da928ff0f9bbdb27cc173cc76fb89a6e6075e6e9d923310071bb1127 error="open /run/vc/sbs/0b0652b7da928ff0f9bbdb27cc173cc76fb89a6e6075e6e9d923310071bb1127/devices.json: no such file or directory" name=kata-runtime pid=27938 sandbox=0b0652b7da928ff0f9bbdb27cc173cc76fb89a6e6075e6e9d923310071bb1127 sandboxid=0b0652b7da928ff0f9bbdb27cc173cc76fb89a6e6075e6e9d923310071bb1127 source=virtcontainers subsystem=sandbox
time="2019-02-06T16:32:15.561004655+01:00" level=debug arch=amd64 command=create container=0b0652b7da928ff0f9bbdb27cc173cc76fb89a6e6075e6e9d923310071bb1127 default-kernel-parameters="tsc=reliable no_timer_check rcupdate.rcu_expedited=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp reboot=k console=hvc0 console=hvc1 iommu=off cryptomgr.notests net.ifnames=0 pci=lastbus=0 root=/dev/pmem0p1 rootflags=dax,data=ordered,errors=remount-ro rw rootfstype=ext4 debug systemd.show_status=true systemd.log_level=debug" name=kata-runtime pid=27938 source=virtcontainers subsystem=qemu
time="2019-02-06T16:32:15.579717444+01:00" level=error msg="Unable to launch /usr/bin/qemu-lite-system-x86_64: exit status 1" arch=amd64 command=create container=0b0652b7da928ff0f9bbdb27cc173cc76fb89a6e6075e6e9d923310071bb1127 name=kata-runtime pid=27938 source=virtcontainers subsystem=qmp
time="2019-02-06T16:32:15.580328611+01:00" level=error msg="qemu-lite-system-x86_64: cannot set up guest memory 'pc.ram': Cannot allocate memory\n" arch=amd64 command=create container=0b0652b7da928ff0f9bbdb27cc173cc76fb89a6e6075e6e9d923310071bb1127 name=kata-runtime pid=27938 source=virtcontainers subsystem=qmp
time="2019-02-06T16:32:15.624408496+01:00" level=error msg="qemu-lite-system-x86_64: cannot set up guest memory 'pc.ram': Cannot allocate memory\n" arch=amd64 command=create container=0b0652b7da928ff0f9bbdb27cc173cc76fb89a6e6075e6e9d923310071bb1127 name=kata-runtime pid=27938 source=runtime
time="2019-02-06T16:32:35.19660104+01:00" level=debug msg="Could not retrieve anything from storage" arch=amd64 command=create container=2a419001603f54edd9f71103b49d40cf2ceab6d08cb75ff9ebf5985320ad0098 name=kata-runtime pid=28163 source=virtcontainers subsystem=kata_agent
time="2019-02-06T16:32:35.200051229+01:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=2a419001603f54edd9f71103b49d40cf2ceab6d08cb75ff9ebf5985320ad0098 error="open /run/vc/sbs/2a419001603f54edd9f71103b49d40cf2ceab6d08cb75ff9ebf5985320ad0098/devices.json: no such file or directory" name=kata-runtime pid=28163 sandbox=2a419001603f54edd9f71103b49d40cf2ceab6d08cb75ff9ebf5985320ad0098 sandboxid=2a419001603f54edd9f71103b49d40cf2ceab6d08cb75ff9ebf5985320ad0098 source=virtcontainers subsystem=sandbox
time="2019-02-06T16:32:35.204920143+01:00" level=debug arch=amd64 command=create container=2a419001603f54edd9f71103b49d40cf2ceab6d08cb75ff9ebf5985320ad0098 default-kernel-parameters="tsc=reliable no_timer_check rcupdate.rcu_expedited=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp reboot=k console=hvc0 console=hvc1 iommu=off cryptomgr.notests net.ifnames=0 pci=lastbus=0 root=/dev/pmem0p1 rootflags=dax,data=ordered,errors=remount-ro rw rootfstype=ext4 debug systemd.show_status=true systemd.log_level=debug" name=kata-runtime pid=28163 source=virtcontainers subsystem=qemu
time="2019-02-06T16:32:55.344374829+01:00" level=error msg="Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing" arch=amd64 command=create container=2a419001603f54edd9f71103b49d40cf2ceab6d08cb75ff9ebf5985320ad0098 name=kata-runtime pid=28163 source=runtime
```

## Proxy logs

Recent proxy problems found in system journal:
```
time="2019-02-05T12:37:53.849568391+01:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/e175f92153f6313b167e4fd80ae40218e8138b4d0d3f202d8d06aa0418c0df47/kata.sock: use of closed network connection" name=kata-proxy pid=11724 sandbox=e175f92153f6313b167e4fd80ae40218e8138b4d0d3f202d8d06aa0418c0df47 source=proxy
time="2019-02-05T12:55:04.490456755+01:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/2237dc195901dc7177472a667b7b0247c1d782261c9fe238957651ef6f770fde/proxy.sock: use of closed network connection" name=kata-proxy pid=15022 sandbox=2237dc195901dc7177472a667b7b0247c1d782261c9fe238957651ef6f770fde source=proxy
time="2019-02-05T13:43:13.511504148+01:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/foo/proxy.sock: use of closed network connection" name=kata-proxy pid=16175 sandbox=foo source=proxy
time="2019-02-05T16:05:21.261897702+01:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/foo/proxy.sock: use of closed network connection" name=kata-proxy pid=16500 sandbox=foo source=proxy
time="2019-02-05T16:08:05.32477221+01:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/foo2/proxy.sock: use of closed network connection" name=kata-proxy pid=20069 sandbox=foo2 source=proxy
time="2019-02-05T16:11:47.403995405+01:00" level=fatal msg="channel error" error="session shutdown" name=kata-proxy pid=16390 sandbox=bd5032790a43ffca172e549ffcd0a765546b9c5a4cb9dbc27e3dc2d966727ca1 source=proxy
time="2019-02-06T13:55:59.675746405+01:00" level=fatal msg="failed to dial channel" channel=/run/vc/vm/foo3/kata.sock error="dial unix /run/vc/vm/foo3/kata.sock: connect: no such file or directory" name=kata-proxy pid=27345 sandbox=foo3 source=proxy
time="2019-02-06T14:04:40.366139529+01:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/foo1/kata.sock: use of closed network connection" name=kata-proxy pid=27434 sandbox=foo1 source=proxy
time="2019-02-06T14:10:21.576453776+01:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/foo2/kata.sock: use of closed network connection" name=kata-proxy pid=27502 sandbox=foo2 source=proxy
time="2019-02-06T14:24:43.387407743+01:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/foo4/kata.sock: use of closed network connection" name=kata-proxy pid=27685 sandbox=foo4 source=proxy
time="2019-02-06T14:36:31.525122926+01:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/foo5/proxy.sock: use of closed network connection" name=kata-proxy pid=27752 sandbox=foo5 source=proxy
time="2019-02-06T15:38:56.181282442+01:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/foo6/kata.sock: use of closed network connection" name=kata-proxy pid=27812 sandbox=foo6 source=proxy
time="2019-02-06T15:39:52.228678005+01:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/22ac4e7f3e6fbffc9ebd4560da00380d520eac816b086372c0d106421de2ca91/proxy.sock: use of closed network connection" name=kata-proxy pid=17447 sandbox=22ac4e7f3e6fbffc9ebd4560da00380d520eac816b086372c0d106421de2ca91 source=proxy
time="2019-02-06T15:40:34.685987901+01:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/a7d55b22f39f4b34a2a4f6cc246db4e5ad5bcbb2158182b4f7fb955fd7dfebd5/proxy.sock: use of closed network connection" name=kata-proxy pid=17734 sandbox=a7d55b22f39f4b34a2a4f6cc246db4e5ad5bcbb2158182b4f7fb955fd7dfebd5 source=proxy
time="2019-02-06T15:40:34.686029723+01:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/a7d55b22f39f4b34a2a4f6cc246db4e5ad5bcbb2158182b4f7fb955fd7dfebd5/kata.sock: use of closed network connection" name=kata-proxy pid=17734 sandbox=a7d55b22f39f4b34a2a4f6cc246db4e5ad5bcbb2158182b4f7fb955fd7dfebd5 source=proxy
time="2019-02-06T15:44:28.629695408+01:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/alpine37tuan/proxy.sock: use of closed network connection" name=kata-proxy pid=17994 sandbox=alpine37tuan source=proxy
time="2019-02-06T15:53:37.361006075+01:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/db20c46ec9ad3854de96cba3ee088e30af4b046e8a2e744111dabf8073af23c0/proxy.sock: use of closed network connection" name=kata-proxy pid=26837 sandbox=db20c46ec9ad3854de96cba3ee088e30af4b046e8a2e744111dabf8073af23c0 source=proxy
time="2019-02-06T16:01:48.532904259+01:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/3b1606142071581885f4d98288552dca152ab2d69e5292a88b545f000f8cf7a3/proxy.sock: use of closed network connection" name=kata-proxy pid=27441 sandbox=3b1606142071581885f4d98288552dca152ab2d69e5292a88b545f000f8cf7a3 source=proxy
time="2019-02-06T16:04:15.328379101+01:00" level=info msg="[    0.744863] EXT4-fs (pmem0p1): DAX enabled. Warning: EXPERIMENTAL, use at your own risk\n" name=kata-proxy pid=27686 sandbox=9a11ea34f2599b0a5aa7d81e0a8c913712533ec309dd5c808abebb6b97cb64bf source=agent
time="2019-02-06T16:04:15.331692703+01:00" level=info msg="[    0.747998] EXT4-fs (pmem0p1): mounted filesystem with ordered data mode. Opts: dax,data=ordered,errors=remount-ro\n" name=kata-proxy pid=27686 sandbox=9a11ea34f2599b0a5aa7d81e0a8c913712533ec309dd5c808abebb6b97cb64bf source=agent
time="2019-02-06T16:04:15.54277571+01:00" level=info msg="[\x1b[0;1;31m!!!!!!\x1b[0m] Failed to isolate default target, freezing.\n" name=kata-proxy pid=27686 sandbox=9a11ea34f2599b0a5aa7d81e0a8c913712533ec309dd5c808abebb6b97cb64bf source=agent
time="2019-02-06T16:04:33.892620568+01:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/9a11ea34f2599b0a5aa7d81e0a8c913712533ec309dd5c808abebb6b97cb64bf/proxy.sock: use of closed network connection" name=kata-proxy pid=27686 sandbox=9a11ea34f2599b0a5aa7d81e0a8c913712533ec309dd5c808abebb6b97cb64bf source=proxy
time="2019-02-06T16:32:36.667736789+01:00" level=info msg="[    0.657086] EXT4-fs (pmem0p1): DAX enabled. Warning: EXPERIMENTAL, use at your own risk\n" name=kata-proxy pid=28208 sandbox=2a419001603f54edd9f71103b49d40cf2ceab6d08cb75ff9ebf5985320ad0098 source=agent
time="2019-02-06T16:32:36.670962767+01:00" level=info msg="[    0.660258] EXT4-fs (pmem0p1): mounted filesystem with ordered data mode. Opts: dax,data=ordered,errors=remount-ro\n" name=kata-proxy pid=28208 sandbox=2a419001603f54edd9f71103b49d40cf2ceab6d08cb75ff9ebf5985320ad0098 source=agent
time="2019-02-06T16:32:36.902444584+01:00" level=info msg="[\x1b[0;1;31m!!!!!!\x1b[0m] Failed to isolate default target, freezing.\n" name=kata-proxy pid=28208 sandbox=2a419001603f54edd9f71103b49d40cf2ceab6d08cb75ff9ebf5985320ad0098 source=agent
time="2019-02-06T16:32:55.309919349+01:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/2a419001603f54edd9f71103b49d40cf2ceab6d08cb75ff9ebf5985320ad0098/proxy.sock: use of closed network connection" name=kata-proxy pid=28208 sandbox=2a419001603f54edd9f71103b49d40cf2ceab6d08cb75ff9ebf5985320ad0098 source=proxy
```

## Shim logs

No recent shim problems found in system journal.

## Throttler logs

No recent throttler problems found in system journal.

---


# Container manager details

Have `docker`

## Docker

Output of "`docker version`":
```
Client:
 Version:           18.06.1-ce
 API version:       1.38
 Go version:        go1.10.3
 Git commit:        e68fc7a
 Built:             Tue Aug 21 17:24:56 2018
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          18.06.1-ce
  API version:      1.38 (minimum version 1.12)
  Go version:       go1.10.3
  Git commit:       e68fc7a
  Built:            Tue Aug 21 17:23:21 2018
  OS/Arch:          linux/amd64
  Experimental:     false
```
Output of "`docker info`":
```
Containers: 12
 Running: 0
 Paused: 0
 Stopped: 12
Images: 14
Server Version: 18.06.1-ce
Storage Driver: devicemapper
 Pool Name: docker-thinpool
 Pool Blocksize: 524.3kB
 Base Device Size: 10.74GB
 Backing Filesystem: xfs
 Udev Sync Supported: true
 Data Space Used: 2.536GB
 Data Space Total: 10.2GB
 Data Space Available: 7.66GB
 Metadata Space Used: 446.5kB
 Metadata Space Total: 104.9MB
 Metadata Space Available: 104.4MB
 Thin Pool Minimum Free Space: 1.019GB
 Deferred Removal Enabled: true
 Deferred Deletion Enabled: true
 Deferred Deleted Device Count: 0
 Library Version: 1.02.110 (2015-10-30)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: kata runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 468a545b9edcd5932818eb9de8e72413e616e86e
runc version: 69663f0bd4b60df09991c08812a60108003fa340
init version: fec3683
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.4.0-116-generic
Operating System: Ubuntu 16.04.5 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 3.859GiB
Name: xzkvm33
ID: 636F:DWV7:KN3I:M6CY:KUVF:3ZNU:S4LH:FOLC:QOUS:DJEE:43KM:RDGU
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 24
 Goroutines: 45
 System Time: 2019-02-07T09:55:58.47285384+01:00
 EventsListeners: 0
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

WARNING: No swap limit support
```
Output of "`systemctl show docker`":
```
Type=notify
Restart=on-failure
NotifyAccess=main
RestartUSec=100ms
TimeoutStartUSec=infinity
TimeoutStopUSec=1min 30s
RuntimeMaxUSec=infinity
WatchdogUSec=0
WatchdogTimestamp=Fri 2019-02-01 14:44:22 CET
WatchdogTimestampMonotonic=6868353
FailureAction=none
PermissionsStartOnly=no
RootDirectoryStartOnly=no
RemainAfterExit=no
GuessMainPID=yes
MainPID=1050
ControlPID=0
FileDescriptorStoreMax=0
NFileDescriptorStore=0
StatusErrno=0
Result=success
ExecMainStartTimestamp=Fri 2019-02-01 14:44:19 CET
ExecMainStartTimestampMonotonic=4418638
ExecMainExitTimestampMonotonic=0
ExecMainPID=1050
ExecMainCode=0
ExecMainStatus=0
ExecStart={ path=/usr/bin/dockerd ; argv[]=/usr/bin/dockerd -D ; ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
ExecReload={ path=/bin/kill ; argv[]=/bin/kill -s HUP $MAINPID ; ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
Slice=system.slice
ControlGroup=/system.slice/docker.service
MemoryCurrent=245325824
CPUUsageNSec=2272263158163
TasksCurrent=55
Delegate=yes
CPUAccounting=no
CPUShares=18446744073709551615
StartupCPUShares=18446744073709551615
CPUQuotaPerSecUSec=infinity
BlockIOAccounting=no
BlockIOWeight=18446744073709551615
StartupBlockIOWeight=18446744073709551615
MemoryAccounting=no
MemoryLimit=18446744073709551615
DevicePolicy=auto
TasksAccounting=no
TasksMax=18446744073709551615
UMask=0022
LimitCPU=18446744073709551615
LimitCPUSoft=18446744073709551615
LimitFSIZE=18446744073709551615
LimitFSIZESoft=18446744073709551615
LimitDATA=18446744073709551615
LimitDATASoft=18446744073709551615
LimitSTACK=18446744073709551615
LimitSTACKSoft=8388608
LimitCORE=18446744073709551615
LimitCORESoft=18446744073709551615
LimitRSS=18446744073709551615
LimitRSSSoft=18446744073709551615
LimitNOFILE=1048576
LimitNOFILESoft=1048576
LimitAS=18446744073709551615
LimitASSoft=18446744073709551615
LimitNPROC=18446744073709551615
LimitNPROCSoft=18446744073709551615
LimitMEMLOCK=65536
LimitMEMLOCKSoft=65536
LimitLOCKS=18446744073709551615
LimitLOCKSSoft=18446744073709551615
LimitSIGPENDING=15646
LimitSIGPENDINGSoft=15646
LimitMSGQUEUE=819200
LimitMSGQUEUESoft=819200
LimitNICE=0
LimitNICESoft=0
LimitRTPRIO=0
LimitRTPRIOSoft=0
LimitRTTIME=18446744073709551615
LimitRTTIMESoft=18446744073709551615
OOMScoreAdjust=0
Nice=0
IOScheduling=0
CPUSchedulingPolicy=0
CPUSchedulingPriority=0
TimerSlackNSec=50000
CPUSchedulingResetOnFork=no
NonBlocking=no
StandardInput=null
StandardOutput=journal
StandardError=inherit
TTYReset=no
TTYVHangup=no
TTYVTDisallocate=no
SyslogPriority=30
SyslogLevelPrefix=yes
SyslogLevel=6
SyslogFacility=3
SecureBits=0
CapabilityBoundingSet=18446744073709551615
AmbientCapabilities=0
MountFlags=0
PrivateTmp=no
PrivateNetwork=no
PrivateDevices=no
ProtectHome=no
ProtectSystem=no
SameProcessGroup=no
UtmpMode=init
IgnoreSIGPIPE=yes
NoNewPrivileges=no
SystemCallErrorNumber=0
RuntimeDirectoryMode=0755
KillMode=process
KillSignal=15
SendSIGKILL=yes
SendSIGHUP=no
Id=docker.service
Names=docker.service
Requires=system.slice docker.socket sysinit.target
Wants=network-online.target
WantedBy=multi-user.target
ConsistsOf=docker.socket
Conflicts=shutdown.target
Before=shutdown.target multi-user.target
After=network-online.target systemd-journald.socket system.slice sysinit.target firewalld.service docker.socket basic.target
TriggeredBy=docker.socket
Documentation=https://docs.docker.com
Description=Docker Application Container Engine
LoadState=loaded
ActiveState=active
SubState=running
FragmentPath=/lib/systemd/system/docker.service
DropInPaths=/etc/systemd/system/docker.service.d/kata-containers.conf
UnitFileState=enabled
UnitFilePreset=enabled
StateChangeTimestamp=Fri 2019-02-01 14:44:22 CET
StateChangeTimestampMonotonic=6868355
InactiveExitTimestamp=Fri 2019-02-01 14:44:19 CET
InactiveExitTimestampMonotonic=4418672
ActiveEnterTimestamp=Fri 2019-02-01 14:44:22 CET
ActiveEnterTimestampMonotonic=6868355
ActiveExitTimestampMonotonic=0
InactiveEnterTimestampMonotonic=0
CanStart=yes
CanStop=yes
CanReload=yes
CanIsolate=no
StopWhenUnneeded=no
RefuseManualStart=no
RefuseManualStop=no
AllowIsolate=no
DefaultDependencies=yes
OnFailureJobMode=replace
IgnoreOnIsolate=no
NeedDaemonReload=no
JobTimeoutUSec=infinity
JobTimeoutAction=none
ConditionResult=yes
AssertResult=yes
ConditionTimestamp=Fri 2019-02-01 14:44:19 CET
ConditionTimestampMonotonic=4417741
AssertTimestamp=Fri 2019-02-01 14:44:19 CET
AssertTimestampMonotonic=4417741
Transient=no
StartLimitInterval=60000000
StartLimitBurst=3
StartLimitAction=none
```
No `kubectl`

---


# Packages

Have `dpkg`
Output of "`dpkg -l|egrep "(cc-oci-runtimecc-runtimerunv|kata-proxy|kata-runtime|kata-shim|kata-ksm-throttler|kata-containers-image|linux-container|qemu-)"`":
```
ii  kata-containers-image               1.4.2-5                                    amd64        Kata containers image
ii  kata-ksm-throttler                  1.4.2.git+d70af5c-5                        amd64        
ii  kata-linux-container                4.14.67.22-6                               amd64        linux kernel optimised for container-like workloads.
ii  kata-proxy                          1.4.1+git.6553b83-4                        amd64        
ii  kata-runtime                        1.4.1+git.45ea48e-4                        amd64        
ii  kata-shim                           1.4.1+git.6346110-4                        amd64        
ii  qemu-block-extra:amd64              1:2.5+dfsg-5ubuntu10.34                    amd64        extra block backend modules for qemu-system and qemu-utils
ii  qemu-kvm                            1:2.5+dfsg-5ubuntu10.34                    amd64        QEMU Full virtualization
ii  qemu-lite                           2.11.0+git.87517afd72-5                    amd64        linux kernel optimised for container-like workloads.
ii  qemu-slof                           20151103+dfsg-1ubuntu1.1                   all          Slimline Open Firmware -- QEMU PowerPC version
ii  qemu-system                         1:2.5+dfsg-5ubuntu10.34                    amd64        QEMU full system emulation binaries
ii  qemu-system-arm                     1:2.5+dfsg-5ubuntu10.34                    amd64        QEMU full system emulation binaries (arm)
ii  qemu-system-common                  1:2.5+dfsg-5ubuntu10.34                    amd64        QEMU full system emulation binaries (common files)
ii  qemu-system-mips                    1:2.5+dfsg-5ubuntu10.34                    amd64        QEMU full system emulation binaries (mips)
ii  qemu-system-misc                    1:2.5+dfsg-5ubuntu10.34                    amd64        QEMU full system emulation binaries (miscelaneous)
ii  qemu-system-ppc                     1:2.5+dfsg-5ubuntu10.34                    amd64        QEMU full system emulation binaries (ppc)
ii  qemu-system-sparc                   1:2.5+dfsg-5ubuntu10.34                    amd64        QEMU full system emulation binaries (sparc)
ii  qemu-system-x86                     1:2.5+dfsg-5ubuntu10.34                    amd64        QEMU full system emulation binaries (x86)
ii  qemu-user                           1:2.5+dfsg-5ubuntu10.34                    amd64        QEMU user mode emulation binaries
ii  qemu-user-binfmt                    1:2.5+dfsg-5ubuntu10.34                    amd64        QEMU user mode binfmt registration for qemu-user
ii  qemu-utils                          1:2.5+dfsg-5ubuntu10.34                    amd64        QEMU utilities
ii  qemu-vanilla                        2.11.2+git.0982a56a55-5                    amd64        linux kernel optimised for container-like workloads.
```
No `rpm`

---