Description of problem

Kata container doesn't start under Clear Linux. I followed first this on Debian host: https://clearlinux.org/documentation/clear-linux/get-started/virtual-machine-install/kvm#kvm then continued with under Clear Linux VM: https://clearlinux.org/documentation/clear-linux/tutorials/kata

Expected result

I expected to get a shell inside nested Kata VM inside Clear Linux all running on Debian.

Actual result

docker run -ti busybox sh

docker: Error response from daemon: OCI runtime create failed: Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing: unknown.

Please ignore the "Cannot allocate memory" errors in journal below because these happened when I try to start Kata before killing stale qemu processes/VMs left handing by previous runs

Running kata-collect-data.sh version 1.5.1 (commit ) at 2019-03-22.00:51:32.871423066+0000.

Runtime is /usr/bin/kata-runtime.

`kata-env`

Output of "/usr/bin/kata-runtime kata-env":

[Meta]
  Version = "1.0.20"

[Runtime]
  Debug = false
  Trace = false
  DisableGuestSeccomp = true
  DisableNewNetNs = false
  Path = "/usr/bin/kata-runtime"
  [Runtime.Version]
    Semver = "1.5.1"
    Commit = ""
    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/kata-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/kata-containers-image_clearlinux_1.5.1_agent_656036e7570.img"

[Kernel]
  Path = "/usr/share/kata-containers/vmlinuz-4.14.107-18.container"
  Parameters = "init=/usr/lib/systemd/systemd systemd.unit=kata-containers.target systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket agent.log=debug initcall_debug"

[Initrd]
  Path = ""

[Proxy]
  Type = "kataProxy"
  Version = "kata-proxy version 1.5.1"
  Path = "/usr/libexec/kata-containers/kata-proxy"
  Debug = false

[Shim]
  Type = "kataShim"
  Version = "kata-shim version 1.5.1"
  Path = "/usr/libexec/kata-containers/kata-shim"
  Debug = false

[Agent]
  Type = "kata"

[Host]
  Kernel = "5.0.3-315.kvm"
  Architecture = "amd64"
  VMContainerCapable = true
  SupportVSocks = false
  [Host.Distro]
    Name = "Clear Linux OS"
    Version = "28420"
  [Host.CPU]
    Vendor = "GenuineIntel"
    Model = "Intel(R) Core(TM) i5-7260U CPU @ 2.20GHz"

[Netmon]
  Version = "kata-netmon version 1.5.1"
  Path = "/usr/libexec/kata-containers/kata-netmon"
  Debug = false
  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"":

# Copyright (c) 2017-2019 Intel Corporation
#
# SPDX-License-Identifier: Apache-2.0
#

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

[hypervisor.qemu]
path = "/usr/bin/kata-qemu-lite-system-x86_64"
kernel = "/usr/share/kata-containers/vmlinuz.container"
image = "/usr/share/kata-containers/kata-containers.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 = 712
#
# 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

# The size in MiB will be plused to max memory of hypervisor.
# It is the memory address space for the NVDIMM devie.
# If set block storage driver (block_device_driver) to "nvdimm",
# should set memory_offset to the size of block device.
# Default 0
#memory_offset = 0

# 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 virtio-scsi, virtio-blk
# or nvdimm.
block_device_driver = "virtio-scsi"

# Specifies cache-related options will be set to block devices or not.
# Default false
#block_device_cache_set = true

# Specifies cache-related options for block devices.
# Denotes whether use of O_DIRECT (bypass the host page cache) is enabled.
# Default false
#block_device_cache_direct = true

# Specifies cache-related options for block devices.
# Denotes whether flush requests for the device are ignored.
# Default false
#block_device_cache_noflush = true

# 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.
#
# Note: Requires "initrd=" to be set ("image=" is not supported).
#
# 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

# If enabled, the shim will create opentracing.io traces and spans.
# (See https://www.jaegertracing.io/docs/getting-started).
#
# Note: By default, the shim runs in a separate network namespace. Therefore,
# to allow it to send trace details to the Jaeger agent running on the host,
# it is necessary to set 'disable_new_netns=true' so that it runs in the host
# network namespace.
#
# (default: disabled)
#enable_tracing = 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"

# disable guest seccomp
# Determines whether container seccomp profiles are passed to the virtual
# machine and applied by the kata agent. If set to true, seccomp is not applied
# within the guest
# (default: true)
disable_guest_seccomp=true

# 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 "--version":

/usr/bin/kata-collect-data.sh: line 168: --version: command not found

systemd service

Image details

---
osbuilder:
  url: "https://github.com/kata-containers/osbuilder"
  version: "unknown"
rootfs-creation-time: "2019-03-01T12:22:58.072363409+0000Z"
description: "osbuilder rootfs"
file-format-version: "0.0.2"
architecture: "x86_64"
base-distro:
  name: "Clear"
  version: "28070"
  packages:
    default:
      - "iptables-bin"
      - "libudev0-shim"
      - "systemd"
    extra:

agent:
  url: "https://github.com/kata-containers/agent"
  name: "kata-agent"
  version: "1.5.1-656036e7570ee258dcb41d5b9fefad847643898e"
  agent-is-init-daemon: "no"

Initrd details

No initrd

Logfiles

Runtime logs

Recent runtime problems found in system journal:

time="2019-03-21T23:37:16.079610888Z" level=warning msg="VM memory (512MB) smaller than image \"/usr/share/kata-containers/kata-containers-image_clearlinux_1.5.1_agent_656036e7570.img\" size (512MB)" arch=amd64 command=create name=kata-runtime pid=2934 source=katautils
time="2019-03-21T23:37:16.172908184Z" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=68fa6f722cbfd70a3895da4c46d141bf5574b16cf068f7b5d71d264907f84596 error="open /run/vc/sbs/68fa6f722cbfd70a3895da4c46d141bf5574b16cf068f7b5d71d264907f84596/devices.json: no such file or directory" name=kata-runtime pid=2934 sandbox=68fa6f722cbfd70a3895da4c46d141bf5574b16cf068f7b5d71d264907f84596 sandboxid=68fa6f722cbfd70a3895da4c46d141bf5574b16cf068f7b5d71d264907f84596 source=virtcontainers subsystem=sandbox
time="2019-03-21T23:37:36.239734443Z" level=error msg="Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing" arch=amd64 command=create container=68fa6f722cbfd70a3895da4c46d141bf5574b16cf068f7b5d71d264907f84596 name=kata-runtime pid=2934 source=runtime
time="2019-03-21T23:41:40.615441421Z" level=warning msg="VM memory (512MB) smaller than image \"/usr/share/kata-containers/kata-containers-image_clearlinux_1.5.1_agent_656036e7570.img\" size (512MB)" arch=amd64 command=create name=kata-runtime pid=3028 source=katautils
time="2019-03-21T23:41:40.728107909Z" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=322dab55fa5c0a8efe75334d7ae9381cfbd41d20737d1f55712e1581792c71b7 error="open /run/vc/sbs/322dab55fa5c0a8efe75334d7ae9381cfbd41d20737d1f55712e1581792c71b7/devices.json: no such file or directory" name=kata-runtime pid=3028 sandbox=322dab55fa5c0a8efe75334d7ae9381cfbd41d20737d1f55712e1581792c71b7 sandboxid=322dab55fa5c0a8efe75334d7ae9381cfbd41d20737d1f55712e1581792c71b7 source=virtcontainers subsystem=sandbox
time="2019-03-21T23:42:00.825341625Z" level=error msg="Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing" arch=amd64 command=create container=322dab55fa5c0a8efe75334d7ae9381cfbd41d20737d1f55712e1581792c71b7 name=kata-runtime pid=3028 source=runtime
time="2019-03-21T23:48:50.964590995Z" level=warning msg="VM memory (512MB) smaller than image \"/usr/share/kata-containers/kata-containers-image_clearlinux_1.5.1_agent_656036e7570.img\" size (512MB)" arch=amd64 command=create name=kata-runtime pid=3303 source=katautils
time="2019-03-21T23:48:51.077442744Z" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=86b2155a56a8a06e4eeb022d337cacd8883b0d6a2625ef85986c328143cea3f7 error="open /run/vc/sbs/86b2155a56a8a06e4eeb022d337cacd8883b0d6a2625ef85986c328143cea3f7/devices.json: no such file or directory" name=kata-runtime pid=3303 sandbox=86b2155a56a8a06e4eeb022d337cacd8883b0d6a2625ef85986c328143cea3f7 sandboxid=86b2155a56a8a06e4eeb022d337cacd8883b0d6a2625ef85986c328143cea3f7 source=virtcontainers subsystem=sandbox
time="2019-03-21T23:49:11.202418355Z" level=error msg="Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing" arch=amd64 command=create container=86b2155a56a8a06e4eeb022d337cacd8883b0d6a2625ef85986c328143cea3f7 name=kata-runtime pid=3303 source=runtime
time="2019-03-21T23:55:25.48397075Z" level=warning msg="VM memory (512MB) smaller than image \"/usr/share/kata-containers/kata-containers-image_clearlinux_1.5.1_agent_656036e7570.img\" size (512MB)" arch=amd64 command=create name=kata-runtime pid=3410 source=katautils
time="2019-03-21T23:55:25.582509072Z" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=8b65d2f5b58b922b6687ec3793cefcdc7e4b4b0be2943122007877a66d303e1a error="open /run/vc/sbs/8b65d2f5b58b922b6687ec3793cefcdc7e4b4b0be2943122007877a66d303e1a/devices.json: no such file or directory" name=kata-runtime pid=3410 sandbox=8b65d2f5b58b922b6687ec3793cefcdc7e4b4b0be2943122007877a66d303e1a sandboxid=8b65d2f5b58b922b6687ec3793cefcdc7e4b4b0be2943122007877a66d303e1a source=virtcontainers subsystem=sandbox
time="2019-03-21T23:55:45.771792156Z" level=error msg="Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing" arch=amd64 command=create container=8b65d2f5b58b922b6687ec3793cefcdc7e4b4b0be2943122007877a66d303e1a name=kata-runtime pid=3410 source=runtime
time="2019-03-21T23:57:06.61483397Z" level=warning msg="VM memory (512MB) smaller than image \"/usr/share/kata-containers/kata-containers-image_clearlinux_1.5.1_agent_656036e7570.img\" size (512MB)" arch=amd64 command=create name=kata-runtime pid=3509 source=katautils
time="2019-03-21T23:57:06.70779725Z" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=e2cb1b5a5e2fda1ac19af8d9b6be5d859af3264189d8b5b0414d761239148a35 error="open /run/vc/sbs/e2cb1b5a5e2fda1ac19af8d9b6be5d859af3264189d8b5b0414d761239148a35/devices.json: no such file or directory" name=kata-runtime pid=3509 sandbox=e2cb1b5a5e2fda1ac19af8d9b6be5d859af3264189d8b5b0414d761239148a35 sandboxid=e2cb1b5a5e2fda1ac19af8d9b6be5d859af3264189d8b5b0414d761239148a35 source=virtcontainers subsystem=sandbox
time="2019-03-21T23:57:26.791427307Z" level=error msg="Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing" arch=amd64 command=create container=e2cb1b5a5e2fda1ac19af8d9b6be5d859af3264189d8b5b0414d761239148a35 name=kata-runtime pid=3509 source=runtime
time="2019-03-22T00:01:59.019154101Z" level=warning msg="VM memory (512MB) smaller than image \"/usr/share/kata-containers/kata-containers-image_clearlinux_1.5.1_agent_656036e7570.img\" size (512MB)" arch=amd64 command=create name=kata-runtime pid=3602 source=katautils
time="2019-03-22T00:01:59.099108793Z" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=d2b9d2b7db8413df3de1a39d48379810c6bb268b2cf74e74468dfaf042bc5a58 error="open /run/vc/sbs/d2b9d2b7db8413df3de1a39d48379810c6bb268b2cf74e74468dfaf042bc5a58/devices.json: no such file or directory" name=kata-runtime pid=3602 sandbox=d2b9d2b7db8413df3de1a39d48379810c6bb268b2cf74e74468dfaf042bc5a58 sandboxid=d2b9d2b7db8413df3de1a39d48379810c6bb268b2cf74e74468dfaf042bc5a58 source=virtcontainers subsystem=sandbox
time="2019-03-22T00:02:19.165619901Z" level=error msg="Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing" arch=amd64 command=create container=d2b9d2b7db8413df3de1a39d48379810c6bb268b2cf74e74468dfaf042bc5a58 name=kata-runtime pid=3602 source=runtime
time="2019-03-22T00:05:39.205044141Z" level=warning msg="VM memory (512MB) smaller than image \"/usr/share/kata-containers/kata-containers-image_clearlinux_1.5.1_agent_656036e7570.img\" size (512MB)" arch=amd64 command=create name=kata-runtime pid=3691 source=katautils
time="2019-03-22T00:05:39.282143027Z" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=c5f14093b968b6542d3060c05cb77366e1f518f107ae8fbbcc9cfa0b7a4d321c error="open /run/vc/sbs/c5f14093b968b6542d3060c05cb77366e1f518f107ae8fbbcc9cfa0b7a4d321c/devices.json: no such file or directory" name=kata-runtime pid=3691 sandbox=c5f14093b968b6542d3060c05cb77366e1f518f107ae8fbbcc9cfa0b7a4d321c sandboxid=c5f14093b968b6542d3060c05cb77366e1f518f107ae8fbbcc9cfa0b7a4d321c source=virtcontainers subsystem=sandbox
time="2019-03-22T00:05:59.362127339Z" level=error msg="Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing" arch=amd64 command=create container=c5f14093b968b6542d3060c05cb77366e1f518f107ae8fbbcc9cfa0b7a4d321c name=kata-runtime pid=3691 source=runtime
time="2019-03-22T00:06:06.435850932Z" level=warning msg="VM memory (512MB) smaller than image \"/usr/share/kata-containers/kata-containers-image_clearlinux_1.5.1_agent_656036e7570.img\" size (512MB)" arch=amd64 command=create name=kata-runtime pid=3764 source=katautils
time="2019-03-22T00:06:06.553808384Z" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=91fae3247e6e4a9aefa533d39f3efd82fdbda2515d227f73626fd9ad75275253 error="open /run/vc/sbs/91fae3247e6e4a9aefa533d39f3efd82fdbda2515d227f73626fd9ad75275253/devices.json: no such file or directory" name=kata-runtime pid=3764 sandbox=91fae3247e6e4a9aefa533d39f3efd82fdbda2515d227f73626fd9ad75275253 sandboxid=91fae3247e6e4a9aefa533d39f3efd82fdbda2515d227f73626fd9ad75275253 source=virtcontainers subsystem=sandbox
time="2019-03-22T00:06:06.565217034Z" level=error msg="Unable to launch /usr/bin/kata-qemu-lite-system-x86_64: exit status 1" arch=amd64 command=create container=91fae3247e6e4a9aefa533d39f3efd82fdbda2515d227f73626fd9ad75275253 name=kata-runtime pid=3764 source=virtcontainers subsystem=qmp
time="2019-03-22T00:06:06.565349726Z" level=error msg="kata-qemu-lite-system-x86_64: -object memory-backend-file,id=mem0,mem-path=/usr/share/kata-containers/kata-containers-image_clearlinux_1.5.1_agent_656036e7570.img,size=536870912: unable to map backing store for guest RAM: Cannot allocate memory\n" arch=amd64 command=create container=91fae3247e6e4a9aefa533d39f3efd82fdbda2515d227f73626fd9ad75275253 name=kata-runtime pid=3764 source=virtcontainers subsystem=qmp
time="2019-03-22T00:06:06.594194602Z" level=error msg="kata-qemu-lite-system-x86_64: -object memory-backend-file,id=mem0,mem-path=/usr/share/kata-containers/kata-containers-image_clearlinux_1.5.1_agent_656036e7570.img,size=536870912: unable to map backing store for guest RAM: Cannot allocate memory\n" arch=amd64 command=create container=91fae3247e6e4a9aefa533d39f3efd82fdbda2515d227f73626fd9ad75275253 name=kata-runtime pid=3764 source=runtime
time="2019-03-22T00:07:04.356811794Z" level=warning msg="VM memory (512MB) smaller than image \"/usr/share/kata-containers/kata-containers-image_clearlinux_1.5.1_agent_656036e7570.img\" size (512MB)" arch=amd64 command=create name=kata-runtime pid=3835 source=katautils
time="2019-03-22T00:07:04.464530669Z" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=374bc7387819e74fff254edef45ca8c907c1ed6fd5ba1303483af2299f5a28c7 error="open /run/vc/sbs/374bc7387819e74fff254edef45ca8c907c1ed6fd5ba1303483af2299f5a28c7/devices.json: no such file or directory" name=kata-runtime pid=3835 sandbox=374bc7387819e74fff254edef45ca8c907c1ed6fd5ba1303483af2299f5a28c7 sandboxid=374bc7387819e74fff254edef45ca8c907c1ed6fd5ba1303483af2299f5a28c7 source=virtcontainers subsystem=sandbox
time="2019-03-22T00:07:24.582956519Z" level=error msg="Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing" arch=amd64 command=create container=374bc7387819e74fff254edef45ca8c907c1ed6fd5ba1303483af2299f5a28c7 name=kata-runtime pid=3835 source=runtime
time="2019-03-22T00:16:03.482673237Z" level=warning msg="VM memory (512MB) smaller than image \"/usr/share/kata-containers/kata-containers-image_clearlinux_1.5.1_agent_656036e7570.img\" size (512MB)" arch=amd64 command=create name=kata-runtime pid=489 source=katautils
time="2019-03-22T00:16:03.633064785Z" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=43f03fb61d2ed2225434bf472917a82e3caeaa481f2967b66501b1955686df13 error="open /run/vc/sbs/43f03fb61d2ed2225434bf472917a82e3caeaa481f2967b66501b1955686df13/devices.json: no such file or directory" name=kata-runtime pid=489 sandbox=43f03fb61d2ed2225434bf472917a82e3caeaa481f2967b66501b1955686df13 sandboxid=43f03fb61d2ed2225434bf472917a82e3caeaa481f2967b66501b1955686df13 source=virtcontainers subsystem=sandbox
time="2019-03-22T00:16:23.76149288Z" level=error msg="Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing" arch=amd64 command=create container=43f03fb61d2ed2225434bf472917a82e3caeaa481f2967b66501b1955686df13 name=kata-runtime pid=489 source=runtime
time="2019-03-22T00:18:25.610619459Z" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=716ba7db14737774a4c32fc6ad8aa473a41bcdc71b838670f1c3ad5dfa49289a error="open /run/vc/sbs/716ba7db14737774a4c32fc6ad8aa473a41bcdc71b838670f1c3ad5dfa49289a/devices.json: no such file or directory" name=kata-runtime pid=570 sandbox=716ba7db14737774a4c32fc6ad8aa473a41bcdc71b838670f1c3ad5dfa49289a sandboxid=716ba7db14737774a4c32fc6ad8aa473a41bcdc71b838670f1c3ad5dfa49289a source=virtcontainers subsystem=sandbox
time="2019-03-22T00:18:25.6190351Z" level=error msg="Unable to launch /usr/bin/kata-qemu-lite-system-x86_64: exit status 1" arch=amd64 command=create container=716ba7db14737774a4c32fc6ad8aa473a41bcdc71b838670f1c3ad5dfa49289a name=kata-runtime pid=570 source=virtcontainers subsystem=qmp
time="2019-03-22T00:18:25.61910097Z" level=error msg="kata-qemu-lite-system-x86_64: cannot set up guest memory 'pc.ram': Cannot allocate memory\n" arch=amd64 command=create container=716ba7db14737774a4c32fc6ad8aa473a41bcdc71b838670f1c3ad5dfa49289a name=kata-runtime pid=570 source=virtcontainers subsystem=qmp
time="2019-03-22T00:18:25.633332897Z" level=error msg="kata-qemu-lite-system-x86_64: cannot set up guest memory 'pc.ram': Cannot allocate memory\n" arch=amd64 command=create container=716ba7db14737774a4c32fc6ad8aa473a41bcdc71b838670f1c3ad5dfa49289a name=kata-runtime pid=570 source=runtime
time="2019-03-22T00:19:02.753458513Z" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=1e52f4d26658a6d5b99402c80cd385128b2daec87e77b8411f6a0e90f7013515 error="open /run/vc/sbs/1e52f4d26658a6d5b99402c80cd385128b2daec87e77b8411f6a0e90f7013515/devices.json: no such file or directory" name=kata-runtime pid=641 sandbox=1e52f4d26658a6d5b99402c80cd385128b2daec87e77b8411f6a0e90f7013515 sandboxid=1e52f4d26658a6d5b99402c80cd385128b2daec87e77b8411f6a0e90f7013515 source=virtcontainers subsystem=sandbox
time="2019-03-22T00:19:22.857586762Z" level=error msg="Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing" arch=amd64 command=create container=1e52f4d26658a6d5b99402c80cd385128b2daec87e77b8411f6a0e90f7013515 name=kata-runtime pid=641 source=runtime
time="2019-03-22T00:28:35.885162375Z" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=1ecc2082ed54ca20987e80cdf11dc2c6d28de0b83b123fdd327d73542da091cc error="open /run/vc/sbs/1ecc2082ed54ca20987e80cdf11dc2c6d28de0b83b123fdd327d73542da091cc/devices.json: no such file or directory" name=kata-runtime pid=1414 sandbox=1ecc2082ed54ca20987e80cdf11dc2c6d28de0b83b123fdd327d73542da091cc sandboxid=1ecc2082ed54ca20987e80cdf11dc2c6d28de0b83b123fdd327d73542da091cc source=virtcontainers subsystem=sandbox
time="2019-03-22T00:28:35.89378708Z" level=error msg="Unable to launch /usr/bin/kata-qemu-lite-system-x86_64: exit status 1" arch=amd64 command=create container=1ecc2082ed54ca20987e80cdf11dc2c6d28de0b83b123fdd327d73542da091cc name=kata-runtime pid=1414 source=virtcontainers subsystem=qmp
time="2019-03-22T00:28:35.893859161Z" level=error msg="kata-qemu-lite-system-x86_64: cannot set up guest memory 'pc.ram': Cannot allocate memory\n" arch=amd64 command=create container=1ecc2082ed54ca20987e80cdf11dc2c6d28de0b83b123fdd327d73542da091cc name=kata-runtime pid=1414 source=virtcontainers subsystem=qmp
time="2019-03-22T00:28:35.91668829Z" level=error msg="kata-qemu-lite-system-x86_64: cannot set up guest memory 'pc.ram': Cannot allocate memory\n" arch=amd64 command=create container=1ecc2082ed54ca20987e80cdf11dc2c6d28de0b83b123fdd327d73542da091cc name=kata-runtime pid=1414 source=runtime
time="2019-03-22T00:29:01.0813226Z" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=bbc9186bf63aeda8a3d8f9a905261c2d7c39d8fe54cc99ac0204971a44fd581c error="open /run/vc/sbs/bbc9186bf63aeda8a3d8f9a905261c2d7c39d8fe54cc99ac0204971a44fd581c/devices.json: no such file or directory" name=kata-runtime pid=1478 sandbox=bbc9186bf63aeda8a3d8f9a905261c2d7c39d8fe54cc99ac0204971a44fd581c sandboxid=bbc9186bf63aeda8a3d8f9a905261c2d7c39d8fe54cc99ac0204971a44fd581c source=virtcontainers subsystem=sandbox
time="2019-03-22T00:29:21.174855201Z" level=error msg="Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing" arch=amd64 command=create container=bbc9186bf63aeda8a3d8f9a905261c2d7c39d8fe54cc99ac0204971a44fd581c name=kata-runtime pid=1478 source=runtime
time="2019-03-22T00:49:53.299263913Z" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=42e1dc10308a7635d9a75ee76c1f6c680b8ad6ea69dc8debb251b711bacc4330 error="open /run/vc/sbs/42e1dc10308a7635d9a75ee76c1f6c680b8ad6ea69dc8debb251b711bacc4330/devices.json: no such file or directory" name=kata-runtime pid=1697 sandbox=42e1dc10308a7635d9a75ee76c1f6c680b8ad6ea69dc8debb251b711bacc4330 sandboxid=42e1dc10308a7635d9a75ee76c1f6c680b8ad6ea69dc8debb251b711bacc4330 source=virtcontainers subsystem=sandbox
time="2019-03-22T00:49:53.309802407Z" level=error msg="Unable to launch /usr/bin/kata-qemu-lite-system-x86_64: exit status 1" arch=amd64 command=create container=42e1dc10308a7635d9a75ee76c1f6c680b8ad6ea69dc8debb251b711bacc4330 name=kata-runtime pid=1697 source=virtcontainers subsystem=qmp
time="2019-03-22T00:49:53.309881303Z" level=error msg="kata-qemu-lite-system-x86_64: cannot set up guest memory 'pc.ram': Cannot allocate memory\n" arch=amd64 command=create container=42e1dc10308a7635d9a75ee76c1f6c680b8ad6ea69dc8debb251b711bacc4330 name=kata-runtime pid=1697 source=virtcontainers subsystem=qmp
time="2019-03-22T00:49:53.321747842Z" level=error msg="kata-qemu-lite-system-x86_64: cannot set up guest memory 'pc.ram': Cannot allocate memory\n" arch=amd64 command=create container=42e1dc10308a7635d9a75ee76c1f6c680b8ad6ea69dc8debb251b711bacc4330 name=kata-runtime pid=1697 source=runtime
time="2019-03-22T00:50:46.026891796Z" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=d35716a665be321da29e695887769425bc65c386e535ca77b5b245f073428c21 error="open /run/vc/sbs/d35716a665be321da29e695887769425bc65c386e535ca77b5b245f073428c21/devices.json: no such file or directory" name=kata-runtime pid=453 sandbox=d35716a665be321da29e695887769425bc65c386e535ca77b5b245f073428c21 sandboxid=d35716a665be321da29e695887769425bc65c386e535ca77b5b245f073428c21 source=virtcontainers subsystem=sandbox
time="2019-03-22T00:51:06.20510213Z" level=error msg="Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing" arch=amd64 command=create container=d35716a665be321da29e695887769425bc65c386e535ca77b5b245f073428c21 name=kata-runtime pid=453 source=runtime

Proxy logs

Recent proxy problems found in system journal:

time="2019-03-21T23:37:36.221754964Z" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/68fa6f722cbfd70a3895da4c46d141bf5574b16cf068f7b5d71d264907f84596/kata.sock: use of closed network connection" name=kata-proxy pid=2967 sandbox=68fa6f722cbfd70a3895da4c46d141bf5574b16cf068f7b5d71d264907f84596 source=proxy
time="2019-03-21T23:42:00.770154946Z" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/322dab55fa5c0a8efe75334d7ae9381cfbd41d20737d1f55712e1581792c71b7/kata.sock: use of closed network connection" name=kata-proxy pid=3061 sandbox=322dab55fa5c0a8efe75334d7ae9381cfbd41d20737d1f55712e1581792c71b7 source=proxy
time="2019-03-21T23:42:00.770159949Z" level=fatal msg="channel error" error="accept unix /run/vc/sbs/322dab55fa5c0a8efe75334d7ae9381cfbd41d20737d1f55712e1581792c71b7/proxy.sock: use of closed network connection" name=kata-proxy pid=3061 sandbox=322dab55fa5c0a8efe75334d7ae9381cfbd41d20737d1f55712e1581792c71b7 source=proxy
time="2019-03-21T23:49:11.129911651Z" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/86b2155a56a8a06e4eeb022d337cacd8883b0d6a2625ef85986c328143cea3f7/kata.sock: use of closed network connection" name=kata-proxy pid=3337 sandbox=86b2155a56a8a06e4eeb022d337cacd8883b0d6a2625ef85986c328143cea3f7 source=proxy
time="2019-03-21T23:55:45.708183555Z" level=fatal msg="channel error" error="accept unix /run/vc/sbs/8b65d2f5b58b922b6687ec3793cefcdc7e4b4b0be2943122007877a66d303e1a/proxy.sock: use of closed network connection" name=kata-proxy pid=3445 sandbox=8b65d2f5b58b922b6687ec3793cefcdc7e4b4b0be2943122007877a66d303e1a source=proxy
time="2019-03-22T00:02:19.145810425Z" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/d2b9d2b7db8413df3de1a39d48379810c6bb268b2cf74e74468dfaf042bc5a58/kata.sock: use of closed network connection" name=kata-proxy pid=3635 sandbox=d2b9d2b7db8413df3de1a39d48379810c6bb268b2cf74e74468dfaf042bc5a58 source=proxy
time="2019-03-22T00:05:59.331411294Z" level=fatal msg="channel error" error="accept unix /run/vc/sbs/c5f14093b968b6542d3060c05cb77366e1f518f107ae8fbbcc9cfa0b7a4d321c/proxy.sock: use of closed network connection" name=kata-proxy pid=3726 sandbox=c5f14093b968b6542d3060c05cb77366e1f518f107ae8fbbcc9cfa0b7a4d321c source=proxy
time="2019-03-22T00:07:24.514668062Z" level=fatal msg="channel error" error="accept unix /run/vc/sbs/374bc7387819e74fff254edef45ca8c907c1ed6fd5ba1303483af2299f5a28c7/proxy.sock: use of closed network connection" name=kata-proxy pid=3870 sandbox=374bc7387819e74fff254edef45ca8c907c1ed6fd5ba1303483af2299f5a28c7 source=proxy
time="2019-03-22T00:16:23.723737491Z" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/43f03fb61d2ed2225434bf472917a82e3caeaa481f2967b66501b1955686df13/kata.sock: use of closed network connection" name=kata-proxy pid=524 sandbox=43f03fb61d2ed2225434bf472917a82e3caeaa481f2967b66501b1955686df13 source=proxy
time="2019-03-22T00:19:22.845791518Z" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/1e52f4d26658a6d5b99402c80cd385128b2daec87e77b8411f6a0e90f7013515/kata.sock: use of closed network connection" name=kata-proxy pid=676 sandbox=1e52f4d26658a6d5b99402c80cd385128b2daec87e77b8411f6a0e90f7013515 source=proxy
time="2019-03-22T00:29:21.127952045Z" level=fatal msg="channel error" error="accept unix /run/vc/sbs/bbc9186bf63aeda8a3d8f9a905261c2d7c39d8fe54cc99ac0204971a44fd581c/proxy.sock: use of closed network connection" name=kata-proxy pid=1511 sandbox=bbc9186bf63aeda8a3d8f9a905261c2d7c39d8fe54cc99ac0204971a44fd581c source=proxy
time="2019-03-22T00:51:06.142258644Z" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/d35716a665be321da29e695887769425bc65c386e535ca77b5b245f073428c21/kata.sock: use of closed network connection" name=kata-proxy pid=488 sandbox=d35716a665be321da29e695887769425bc65c386e535ca77b5b245f073428c21 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.2
 API version:       1.38
 Go version:        go1.11.5
 Git commit:        e68fc7a215d7133c34aa18e3b72b4a21fd0c6136
 Built:             Tue Feb 26 01:43:07 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          18.06.2
  API version:      1.38 (minimum version 1.12)
  Go version:       go1.11.5
  Git commit:       e68fc7a215d7133c34aa18e3b72b4a21fd0c6136
  Built:            Tue Feb 26 01:43:19 2019
  OS/Arch:          linux/amd64
  Experimental:     false

Output of "docker info":

Containers: 18
 Running: 0
 Paused: 0
 Stopped: 18
Images: 2
Server Version: 18.06.2
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: false
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-runtime runc
Default Runtime: kata-runtime
Init Binary: docker-init
containerd version: 1.2.2 (expected: 468a545b9edcd5932818eb9de8e72413e616e86e)
runc version: <<unknown>> (expected: 69663f0bd4b60df09991c08812a60108003fa340)
init version: N/A (expected: )
Kernel Version: 5.0.3-315.kvm
Operating System: Clear Linux OS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 981.3MiB
Name: clr-b903587bb8714aaaa43f0b89836d44d7
ID: FXY2:EYJ6:VQEG:VGS5:53AN:N4IV:SOOF:UA77:74E4:GEWE:Y4VN:XKY6
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

Output of "systemctl show docker":

Type=notify
Restart=on-failure
NotifyAccess=main
RestartUSec=100ms
TimeoutStartUSec=infinity
TimeoutStopUSec=1min 30s
RuntimeMaxUSec=infinity
WatchdogUSec=0
WatchdogTimestampMonotonic=0
RootDirectoryStartOnly=no
RemainAfterExit=no
GuessMainPID=yes
MainPID=259
ControlPID=0
FileDescriptorStoreMax=0
NFileDescriptorStore=0
StatusErrno=0
Result=success
UID=[not set]
GID=[not set]
NRestarts=0
ExecMainStartTimestamp=Fri 2019-03-22 00:50:42 UTC
ExecMainStartTimestampMonotonic=32713270
ExecMainExitTimestampMonotonic=0
ExecMainPID=259
ExecMainCode=0
ExecMainStatus=0
ExecStart={ path=/usr/bin/dockerd ; argv[]=/usr/bin/dockerd $DOCKER_EXTRA_RUNTIMES $DOCKER_DEFAULT_RUNTIME $DOCKER_EXTRA_OPTS --storage-driver=overlay2 ; ignore_errors=no ; start_time=[Fri 2019-03-22 00:50:42 UTC] ; stop_time=[n/a] ; pid=259 ; 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=393814016
CPUUsageNSec=[not set]
TasksCurrent=48
IPIngressBytes=18446744073709551615
IPIngressPackets=18446744073709551615
IPEgressBytes=18446744073709551615
IPEgressPackets=18446744073709551615
Delegate=yes
DelegateControllers=cpu cpuacct io blkio memory devices pids bpf-firewall bpf-devices
CPUAccounting=no
CPUWeight=[not set]
StartupCPUWeight=[not set]
CPUShares=[not set]
StartupCPUShares=[not set]
CPUQuotaPerSecUSec=infinity
IOAccounting=no
IOWeight=[not set]
StartupIOWeight=[not set]
BlockIOAccounting=no
BlockIOWeight=[not set]
StartupBlockIOWeight=[not set]
MemoryAccounting=yes
MemoryMin=0
MemoryLow=0
MemoryHigh=infinity
MemoryMax=infinity
MemorySwapMax=infinity
MemoryLimit=infinity
DevicePolicy=auto
TasksAccounting=yes
TasksMax=1172
IPAccounting=no
Environment=[unprintable] [unprintable]
UMask=0022
LimitCPU=infinity
LimitCPUSoft=infinity
LimitFSIZE=infinity
LimitFSIZESoft=infinity
LimitDATA=infinity
LimitDATASoft=infinity
LimitSTACK=infinity
LimitSTACKSoft=8388608
LimitCORE=infinity
LimitCORESoft=infinity
LimitRSS=infinity
LimitRSSSoft=infinity
LimitNOFILE=infinity
LimitNOFILESoft=infinity
LimitAS=infinity
LimitASSoft=infinity
LimitNPROC=infinity
LimitNPROCSoft=infinity
LimitMEMLOCK=65536
LimitMEMLOCKSoft=65536
LimitLOCKS=infinity
LimitLOCKSSoft=infinity
LimitSIGPENDING=3908
LimitSIGPENDINGSoft=3908
LimitMSGQUEUE=819200
LimitMSGQUEUESoft=819200
LimitNICE=0
LimitNICESoft=0
LimitRTPRIO=0
LimitRTPRIOSoft=0
LimitRTTIME=infinity
LimitRTTIMESoft=infinity
OOMScoreAdjust=0
Nice=0
IOSchedulingClass=0
IOSchedulingPriority=0
CPUSchedulingPolicy=0
CPUSchedulingPriority=0
TimerSlackNSec=50000
CPUSchedulingResetOnFork=no
NonBlocking=no
StandardInput=null
StandardInputData=
StandardOutput=journal
StandardError=inherit
TTYReset=no
TTYVHangup=no
TTYVTDisallocate=no
SyslogPriority=30
SyslogLevelPrefix=yes
SyslogLevel=6
SyslogFacility=3
LogLevelMax=-1
LogRateLimitIntervalUSec=0
LogRateLimitBurst=0
SecureBits=0
CapabilityBoundingSet=cap_chown cap_dac_override cap_dac_read_search cap_fowner cap_fsetid cap_kill cap_setgid cap_setuid cap_setpcap cap_linux_immutable cap_net_bind_service cap_net_broadcast cap_net_admin cap_net_raw cap_ipc_lock cap_ipc_owner cap_sys_module cap_sys_rawio cap_sys_chroot cap_sys_ptrace cap_sys_pacct cap_sys_admin cap_sys_boot cap_sys_nice cap_sys_resource cap_sys_time cap_sys_tty_config cap_mknod cap_lease cap_audit_write cap_audit_control cap_setfcap cap_mac_override cap_mac_admin cap_syslog cap_wake_alarm cap_block_suspend
AmbientCapabilities=
DynamicUser=no
RemoveIPC=no
MountFlags=
PrivateTmp=no
PrivateDevices=no
ProtectKernelTunables=no
ProtectKernelModules=no
ProtectControlGroups=no
PrivateNetwork=no
PrivateUsers=no
PrivateMounts=no
ProtectHome=no
ProtectSystem=no
SameProcessGroup=no
UtmpMode=init
IgnoreSIGPIPE=yes
NoNewPrivileges=no
SystemCallErrorNumber=0
LockPersonality=no
RuntimeDirectoryPreserve=no
RuntimeDirectoryMode=0755
StateDirectoryMode=0755
CacheDirectoryMode=0755
LogsDirectoryMode=0755
ConfigurationDirectoryMode=0755
MemoryDenyWriteExecute=no
RestrictRealtime=no
RestrictNamespaces=no
MountAPIVFS=no
KeyringMode=private
KillMode=process
KillSignal=15
FinalKillSignal=9
SendSIGKILL=yes
SendSIGHUP=no
WatchdogSignal=6
Id=docker.service
Names=docker.service
Requires=sysinit.target system.slice
Wants=docker-set-runtime.service network-online.target
Conflicts=shutdown.target
Before=shutdown.target
After=basic.target system.slice docker-set-runtime.service firewalld.service systemd-journald.socket sysinit.target network-online.target
Documentation=https://docs.docker.com
Description=Docker Application Container Engine
LoadState=loaded
ActiveState=active
SubState=running
FragmentPath=/usr/lib/systemd/system/docker.service
DropInPaths=/etc/systemd/system/docker.service.d/50-runtime.conf /etc/systemd/system/docker.service.d/51-runtime.conf /usr/lib/systemd/system/docker.service.d/clearlinux.conf
UnitFileState=disabled
UnitFilePreset=disabled
StateChangeTimestamp=Fri 2019-03-22 00:50:43 UTC
StateChangeTimestampMonotonic=34117770
InactiveExitTimestamp=Fri 2019-03-22 00:50:42 UTC
InactiveExitTimestampMonotonic=32713523
ActiveEnterTimestamp=Fri 2019-03-22 00:50:43 UTC
ActiveEnterTimestampMonotonic=34117770
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
JobRunningTimeoutUSec=infinity
JobTimeoutAction=none
ConditionResult=yes
AssertResult=yes
ConditionTimestamp=Fri 2019-03-22 00:50:42 UTC
ConditionTimestampMonotonic=32712736
AssertTimestamp=Fri 2019-03-22 00:50:42 UTC
AssertTimestampMonotonic=32712736
Transient=no
Perpetual=no
StartLimitIntervalUSec=1min
StartLimitBurst=3
StartLimitAction=none
FailureAction=none
FailureActionExitStatus=-1
SuccessAction=none
SuccessActionExitStatus=-1
InvocationID=f797eb7f83474fba86c74657c52b57ff
CollectMode=inactive

No kubectl

Packages

No dpkg No rpm

kata-containers / runtime

Kata container doesn't start under Clear Linux (nested) #1408