Skip to content

Instantly share code, notes, and snippets.

@enzian

enzian/kata-collect-data.txt

Created October 4, 2018 05:20
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save enzian/4678384ede11a21fe2d641320abbcaf0 to your computer and use it in GitHub Desktop.
Save enzian/4678384ede11a21fe2d641320abbcaf0 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
kata-collect-data.txt
# Meta details
Running `kata-collect-data.sh` version `1.3.0 (commit a786643)` at `2018-10-04.05:17:46.278359928+0000`.
---
Runtime is `/usr/bin/kata-runtime`.
# `kata-env`
Output of "`/usr/bin/kata-runtime kata-env`":
```toml
[Meta]
Version = "1.0.18"
[Runtime]
Debug = false
Path = "/usr/bin/kata-runtime"
[Runtime.Version]
Semver = "1.3.0"
Commit = "a786643"
OCI = "1.0.1"
[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 = false
UseVSock = false
[Image]
Path = "/usr/share/kata-containers/kata-containers-image_clearlinux_1.3.0_agent_042c3ebd71c.img"
[Kernel]
Path = "/usr/share/kata-containers/vmlinuz-4.14.67.12-138.container"
Parameters = ""
[Initrd]
Path = ""
[Proxy]
Type = "kataProxy"
Version = "kata-proxy version 1.3.0-6ddb006"
Path = "/usr/libexec/kata-containers/kata-proxy"
Debug = false
[Shim]
Type = "kataShim"
Version = "kata-shim version 1.3.0-5fbf1f0"
Path = "/usr/libexec/kata-containers/kata-shim"
Debug = false
[Agent]
Type = "kata"
[Host]
Kernel = "4.15.0-34-generic"
Architecture = "amd64"
VMContainerCapable = true
SupportVSocks = false
[Host.Distro]
Name = "Ubuntu"
Version = "18.04"
[Host.CPU]
Vendor = "GenuineIntel"
Model = "Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz"
[Netmon]
Version = "kata-netmon version 1.3.0"
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"`":
```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"
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 = ""
# 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"
[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.
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
```
---
# KSM throttler
## version
Output of "`/usr/libexec/kata-ksm-throttler/kata-ksm-throttler --version`":
```
kata-ksm-throttler version 1.3.0-6e903fb
```
## systemd service
# Image details
```yaml
---
osbuilder:
url: "https://github.com/kata-containers/osbuilder"
version: "unknown"
rootfs-creation-time: "2018-10-01T18:47:11.314336132+0000Z"
description: "osbuilder rootfs"
file-format-version: "0.0.2"
architecture: "x86_64"
base-distro:
name: "Clear"
version: "25180"
packages:
default:
- "iptables-bin"
- "libudev0-shim"
- "systemd"
extra:
agent:
url: "https://github.com/kata-containers/agent"
name: "kata-agent"
version: "1.3.0-042c3ebd71c2ca425aa0c70fadcbf6370116659b"
agent-is-init-daemon: "no"
```
---
# Initrd details
No initrd
---
# Logfiles
## Runtime logs
Recent runtime problems found in system journal:
```
time="2018-09-28T13:43:24.631982728Z" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=8f8b0e70e8290ada9831aad43e22dbec15d4591285e9d5892ffaca613658aaf6 error="open /run/vc/sbs/8f8b0e70e8290ada9831aad43e22dbec15d4591285e9d5892ffaca613658aaf6/devices.json: no such file or directory" name=kata-runtime pid=5218 sandbox=8f8b0e70e8290ada9831aad43e22dbec15d4591285e9d5892ffaca613658aaf6 sandboxid=8f8b0e70e8290ada9831aad43e22dbec15d4591285e9d5892ffaca613658aaf6 source=virtcontainers subsystem=sandbox
time="2018-09-28T13:43:24.840956933Z" level=error msg="Unable to launch qemu: exit status 1" arch=amd64 command=create container=8f8b0e70e8290ada9831aad43e22dbec15d4591285e9d5892ffaca613658aaf6 name=kata-runtime pid=5218 source=virtcontainers subsystem=qmp
time="2018-09-28T13:43:24.841047333Z" level=error msg="Could not access KVM kernel module: No such file or directory\nqemu-lite-system-x86_64: failed to initialize KVM: No such file or directory\n" arch=amd64 command=create container=8f8b0e70e8290ada9831aad43e22dbec15d4591285e9d5892ffaca613658aaf6 name=kata-runtime pid=5218 source=virtcontainers subsystem=qmp
time="2018-09-28T13:43:24.877495342Z" level=error msg="Could not access KVM kernel module: No such file or directory\nqemu-lite-system-x86_64: failed to initialize KVM: No such file or directory\n" arch=amd64 command=create container=8f8b0e70e8290ada9831aad43e22dbec15d4591285e9d5892ffaca613658aaf6 name=kata-runtime pid=5218 source=runtime
time="2018-09-28T13:48:30.572634196Z" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=0e974bf54f6a91f71df758f77e90ade8e94496b58350fd0a7ceaad8691d29d38 error="open /run/vc/sbs/0e974bf54f6a91f71df758f77e90ade8e94496b58350fd0a7ceaad8691d29d38/devices.json: no such file or directory" name=kata-runtime pid=1487 sandbox=0e974bf54f6a91f71df758f77e90ade8e94496b58350fd0a7ceaad8691d29d38 sandboxid=0e974bf54f6a91f71df758f77e90ade8e94496b58350fd0a7ceaad8691d29d38 source=virtcontainers subsystem=sandbox
time="2018-09-28T13:48:33.344033075Z" level=error msg="Container not ready, running or paused, impossible to signal the container" arch=amd64 command=kill container=0e974bf54f6a91f71df758f77e90ade8e94496b58350fd0a7ceaad8691d29d38 name=kata-runtime pid=1604 sandbox=0e974bf54f6a91f71df758f77e90ade8e94496b58350fd0a7ceaad8691d29d38 source=runtime
time="2018-09-28T13:48:33.424273943Z" level=error msg="Container 0e974bf54f6a91f71df758f77e90ade8e94496b58350fd0a7ceaad8691d29d38 not ready, running or paused, cannot send a signal" arch=amd64 command=kill container=0e974bf54f6a91f71df758f77e90ade8e94496b58350fd0a7ceaad8691d29d38 name=kata-runtime pid=1632 sandbox=0e974bf54f6a91f71df758f77e90ade8e94496b58350fd0a7ceaad8691d29d38 source=runtime
time="2018-09-28T13:56:32.15945001Z" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=3e149df97dd605c77108be66a2f84c3aac41baebf7e821181d7d18ee73e646c6 error="open /run/vc/sbs/3e149df97dd605c77108be66a2f84c3aac41baebf7e821181d7d18ee73e646c6/devices.json: no such file or directory" name=kata-runtime pid=1800 sandbox=3e149df97dd605c77108be66a2f84c3aac41baebf7e821181d7d18ee73e646c6 sandboxid=3e149df97dd605c77108be66a2f84c3aac41baebf7e821181d7d18ee73e646c6 source=virtcontainers subsystem=sandbox
time="2018-09-28T14:03:23.444088915Z" level=error msg="Container not ready, running or paused, impossible to signal the container" arch=amd64 command=kill container=3e149df97dd605c77108be66a2f84c3aac41baebf7e821181d7d18ee73e646c6 name=kata-runtime pid=1964 sandbox=3e149df97dd605c77108be66a2f84c3aac41baebf7e821181d7d18ee73e646c6 source=runtime
time="2018-09-28T14:03:23.485420103Z" level=error msg="Container 3e149df97dd605c77108be66a2f84c3aac41baebf7e821181d7d18ee73e646c6 not ready, running or paused, cannot send a signal" arch=amd64 command=kill container=3e149df97dd605c77108be66a2f84c3aac41baebf7e821181d7d18ee73e646c6 name=kata-runtime pid=1990 sandbox=3e149df97dd605c77108be66a2f84c3aac41baebf7e821181d7d18ee73e646c6 source=runtime
time="2018-09-28T14:06:11.468765093Z" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=f74ad8552767f55fca31c2acad1c03e1b8583d4594328ce7a492fa1344dcf11f error="open /run/vc/sbs/f74ad8552767f55fca31c2acad1c03e1b8583d4594328ce7a492fa1344dcf11f/devices.json: no such file or directory" name=kata-runtime pid=2055 sandbox=f74ad8552767f55fca31c2acad1c03e1b8583d4594328ce7a492fa1344dcf11f sandboxid=f74ad8552767f55fca31c2acad1c03e1b8583d4594328ce7a492fa1344dcf11f source=virtcontainers subsystem=sandbox
time="2018-09-28T14:06:20.67620588Z" level=error msg="Container not ready, running or paused, impossible to signal the container" arch=amd64 command=kill container=f74ad8552767f55fca31c2acad1c03e1b8583d4594328ce7a492fa1344dcf11f name=kata-runtime pid=2150 sandbox=f74ad8552767f55fca31c2acad1c03e1b8583d4594328ce7a492fa1344dcf11f source=runtime
time="2018-09-28T14:06:20.719143257Z" level=error msg="Container f74ad8552767f55fca31c2acad1c03e1b8583d4594328ce7a492fa1344dcf11f not ready, running or paused, cannot send a signal" arch=amd64 command=kill container=f74ad8552767f55fca31c2acad1c03e1b8583d4594328ce7a492fa1344dcf11f name=kata-runtime pid=2176 sandbox=f74ad8552767f55fca31c2acad1c03e1b8583d4594328ce7a492fa1344dcf11f source=runtime
time="2018-09-28T14:06:25.892082736Z" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=5087baa6bd107d9eb65cd447ae6b312f821d78e0025b8c4d546421a9376cc94a error="open /run/vc/sbs/5087baa6bd107d9eb65cd447ae6b312f821d78e0025b8c4d546421a9376cc94a/devices.json: no such file or directory" name=kata-runtime pid=2239 sandbox=5087baa6bd107d9eb65cd447ae6b312f821d78e0025b8c4d546421a9376cc94a sandboxid=5087baa6bd107d9eb65cd447ae6b312f821d78e0025b8c4d546421a9376cc94a source=virtcontainers subsystem=sandbox
time="2018-09-28T14:06:28.001635412Z" level=error msg="Container not ready, running or paused, impossible to signal the container" arch=amd64 command=kill container=5087baa6bd107d9eb65cd447ae6b312f821d78e0025b8c4d546421a9376cc94a name=kata-runtime pid=2331 sandbox=5087baa6bd107d9eb65cd447ae6b312f821d78e0025b8c4d546421a9376cc94a source=runtime
time="2018-09-28T14:06:28.046979807Z" level=error msg="Container 5087baa6bd107d9eb65cd447ae6b312f821d78e0025b8c4d546421a9376cc94a not ready, running or paused, cannot send a signal" arch=amd64 command=kill container=5087baa6bd107d9eb65cd447ae6b312f821d78e0025b8c4d546421a9376cc94a name=kata-runtime pid=2356 sandbox=5087baa6bd107d9eb65cd447ae6b312f821d78e0025b8c4d546421a9376cc94a source=runtime
time="2018-09-28T14:06:51.971985583Z" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=399932898dc5fb6b88bd43a6aa7a0b4ea93435a52042febf57a34c4825f839a3 error="open /run/vc/sbs/399932898dc5fb6b88bd43a6aa7a0b4ea93435a52042febf57a34c4825f839a3/devices.json: no such file or directory" name=kata-runtime pid=2418 sandbox=399932898dc5fb6b88bd43a6aa7a0b4ea93435a52042febf57a34c4825f839a3 sandboxid=399932898dc5fb6b88bd43a6aa7a0b4ea93435a52042febf57a34c4825f839a3 source=virtcontainers subsystem=sandbox
time="2018-09-28T14:06:53.737364893Z" level=info msg="{\"error\": {\"class\": \"GenericError\", \"desc\": \"Could not open '/dev/fd0': No such device or address\"}}" arch=amd64 command=create container=399932898dc5fb6b88bd43a6aa7a0b4ea93435a52042febf57a34c4825f839a3 name=kata-runtime pid=2418 source=virtcontainers subsystem=qmp
time="2018-09-28T14:06:53.824733075Z" level=error msg="QMP command failed" arch=amd64 command=create container=399932898dc5fb6b88bd43a6aa7a0b4ea93435a52042febf57a34c4825f839a3 name=kata-runtime pid=2418 source=runtime
time="2018-09-28T14:07:44.199669695Z" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=a807278057af5f6be3bf470a63015cd356e0f3add664902f7a299031781f92d6 error="open /run/vc/sbs/a807278057af5f6be3bf470a63015cd356e0f3add664902f7a299031781f92d6/devices.json: no such file or directory" name=kata-runtime pid=2505 sandbox=a807278057af5f6be3bf470a63015cd356e0f3add664902f7a299031781f92d6 sandboxid=a807278057af5f6be3bf470a63015cd356e0f3add664902f7a299031781f92d6 source=virtcontainers subsystem=sandbox
time="2018-09-28T14:07:59.681205239Z" level=info msg="{\"error\": {\"class\": \"GenericError\", \"desc\": \"Could not open '/dev/fd0': No such device or address\"}}" arch=amd64 command=create container=a807278057af5f6be3bf470a63015cd356e0f3add664902f7a299031781f92d6 name=kata-runtime pid=2505 source=virtcontainers subsystem=qmp
time="2018-09-28T14:07:59.78468967Z" level=error msg="QMP command failed" arch=amd64 command=create container=a807278057af5f6be3bf470a63015cd356e0f3add664902f7a299031781f92d6 name=kata-runtime pid=2505 source=runtime
time="2018-09-28T14:09:08.415810768Z" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=b77d1863ee992758e6f551748c01040a2cbae60c3771d27d7d1e15bace4fa47c error="open /run/vc/sbs/b77d1863ee992758e6f551748c01040a2cbae60c3771d27d7d1e15bace4fa47c/devices.json: no such file or directory" name=kata-runtime pid=2596 sandbox=b77d1863ee992758e6f551748c01040a2cbae60c3771d27d7d1e15bace4fa47c sandboxid=b77d1863ee992758e6f551748c01040a2cbae60c3771d27d7d1e15bace4fa47c source=virtcontainers subsystem=sandbox
time="2018-09-28T14:09:12.491938698Z" level=error msg="Container not ready, running or paused, impossible to signal the container" arch=amd64 command=kill container=b77d1863ee992758e6f551748c01040a2cbae60c3771d27d7d1e15bace4fa47c name=kata-runtime pid=2695 sandbox=b77d1863ee992758e6f551748c01040a2cbae60c3771d27d7d1e15bace4fa47c source=runtime
time="2018-09-28T14:09:12.529500251Z" level=error msg="Container b77d1863ee992758e6f551748c01040a2cbae60c3771d27d7d1e15bace4fa47c not ready, running or paused, cannot send a signal" arch=amd64 command=kill container=b77d1863ee992758e6f551748c01040a2cbae60c3771d27d7d1e15bace4fa47c name=kata-runtime pid=2723 sandbox=b77d1863ee992758e6f551748c01040a2cbae60c3771d27d7d1e15bace4fa47c source=runtime
time="2018-09-28T14:11:31.770354273Z" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=513a51d8cc51b9ee7b68683f96c87d041c2402c999830aa04cc9d58a9c34b2fe error="open /run/vc/sbs/513a51d8cc51b9ee7b68683f96c87d041c2402c999830aa04cc9d58a9c34b2fe/devices.json: no such file or directory" name=kata-runtime pid=2798 sandbox=513a51d8cc51b9ee7b68683f96c87d041c2402c999830aa04cc9d58a9c34b2fe sandboxid=513a51d8cc51b9ee7b68683f96c87d041c2402c999830aa04cc9d58a9c34b2fe source=virtcontainers subsystem=sandbox
time="2018-09-28T14:11:35.781578284Z" level=error msg="Container not ready, running or paused, impossible to signal the container" arch=amd64 command=kill container=513a51d8cc51b9ee7b68683f96c87d041c2402c999830aa04cc9d58a9c34b2fe name=kata-runtime pid=2891 sandbox=513a51d8cc51b9ee7b68683f96c87d041c2402c999830aa04cc9d58a9c34b2fe source=runtime
time="2018-09-28T14:11:35.825585626Z" level=error msg="Container 513a51d8cc51b9ee7b68683f96c87d041c2402c999830aa04cc9d58a9c34b2fe not ready, running or paused, cannot send a signal" arch=amd64 command=kill container=513a51d8cc51b9ee7b68683f96c87d041c2402c999830aa04cc9d58a9c34b2fe name=kata-runtime pid=2917 sandbox=513a51d8cc51b9ee7b68683f96c87d041c2402c999830aa04cc9d58a9c34b2fe source=runtime
time="2018-09-28T14:11:50.798557424Z" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=264b44b94a7d31b6c0f11c2b88398233db81daa194d5b1ad2c8022c6eccd2669 error="open /run/vc/sbs/264b44b94a7d31b6c0f11c2b88398233db81daa194d5b1ad2c8022c6eccd2669/devices.json: no such file or directory" name=kata-runtime pid=2993 sandbox=264b44b94a7d31b6c0f11c2b88398233db81daa194d5b1ad2c8022c6eccd2669 sandboxid=264b44b94a7d31b6c0f11c2b88398233db81daa194d5b1ad2c8022c6eccd2669 source=virtcontainers subsystem=sandbox
time="2018-09-28T14:11:52.361025785Z" level=info msg="{\"error\": {\"class\": \"GenericError\", \"desc\": \"Could not open '/dev/fd0': No such device or address\"}}" arch=amd64 command=create container=264b44b94a7d31b6c0f11c2b88398233db81daa194d5b1ad2c8022c6eccd2669 name=kata-runtime pid=2993 source=virtcontainers subsystem=qmp
time="2018-09-28T14:11:52.440729571Z" level=error msg="QMP command failed" arch=amd64 command=create container=264b44b94a7d31b6c0f11c2b88398233db81daa194d5b1ad2c8022c6eccd2669 name=kata-runtime pid=2993 source=runtime
time="2018-09-28T14:18:57.899665215Z" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=7d65a9c8fd61662157cd654d8c3a2a6aca167244bc213060a81ca2330c8209eb error="open /run/vc/sbs/7d65a9c8fd61662157cd654d8c3a2a6aca167244bc213060a81ca2330c8209eb/devices.json: no such file or directory" name=kata-runtime pid=3158 sandbox=7d65a9c8fd61662157cd654d8c3a2a6aca167244bc213060a81ca2330c8209eb sandboxid=7d65a9c8fd61662157cd654d8c3a2a6aca167244bc213060a81ca2330c8209eb source=virtcontainers subsystem=sandbox
time="2018-09-28T14:18:59.309038592Z" level=info msg="{\"error\": {\"class\": \"GenericError\", \"desc\": \"Could not open '/dev/fd0': No such device or address\"}}" arch=amd64 command=create container=7d65a9c8fd61662157cd654d8c3a2a6aca167244bc213060a81ca2330c8209eb name=kata-runtime pid=3158 source=virtcontainers subsystem=qmp
time="2018-09-28T14:18:59.376640377Z" level=error msg="QMP command failed" arch=amd64 command=create container=7d65a9c8fd61662157cd654d8c3a2a6aca167244bc213060a81ca2330c8209eb name=kata-runtime pid=3158 source=runtime
time="2018-09-28T14:24:33.233619676Z" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=a444e636cc86dc0e74d8e7b618e1e9e6eb31c50da4459d4b4f3ad961a4c999f2 error="open /run/vc/sbs/a444e636cc86dc0e74d8e7b618e1e9e6eb31c50da4459d4b4f3ad961a4c999f2/devices.json: no such file or directory" name=kata-runtime pid=3246 sandbox=a444e636cc86dc0e74d8e7b618e1e9e6eb31c50da4459d4b4f3ad961a4c999f2 sandboxid=a444e636cc86dc0e74d8e7b618e1e9e6eb31c50da4459d4b4f3ad961a4c999f2 source=virtcontainers subsystem=sandbox
time="2018-09-28T14:24:34.932168125Z" level=error msg="Container not ready, running or paused, impossible to signal the container" arch=amd64 command=kill container=a444e636cc86dc0e74d8e7b618e1e9e6eb31c50da4459d4b4f3ad961a4c999f2 name=kata-runtime pid=3343 sandbox=a444e636cc86dc0e74d8e7b618e1e9e6eb31c50da4459d4b4f3ad961a4c999f2 source=runtime
time="2018-09-28T14:24:35.018693715Z" level=error msg="Container a444e636cc86dc0e74d8e7b618e1e9e6eb31c50da4459d4b4f3ad961a4c999f2 not ready, running or paused, cannot send a signal" arch=amd64 command=kill container=a444e636cc86dc0e74d8e7b618e1e9e6eb31c50da4459d4b4f3ad961a4c999f2 name=kata-runtime pid=3370 sandbox=a444e636cc86dc0e74d8e7b618e1e9e6eb31c50da4459d4b4f3ad961a4c999f2 source=runtime
time="2018-09-28T14:24:46.143543653Z" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=14a9b78e50b3adf77415a93049859d6e9d4a1eacd0e4cedf7a634f757caceef6 error="open /run/vc/sbs/14a9b78e50b3adf77415a93049859d6e9d4a1eacd0e4cedf7a634f757caceef6/devices.json: no such file or directory" name=kata-runtime pid=3433 sandbox=14a9b78e50b3adf77415a93049859d6e9d4a1eacd0e4cedf7a634f757caceef6 sandboxid=14a9b78e50b3adf77415a93049859d6e9d4a1eacd0e4cedf7a634f757caceef6 source=virtcontainers subsystem=sandbox
time="2018-09-28T14:24:47.605134958Z" level=info msg="{\"error\": {\"class\": \"GenericError\", \"desc\": \"Could not open '/dev/fd0': No such device or address\"}}" arch=amd64 command=create container=14a9b78e50b3adf77415a93049859d6e9d4a1eacd0e4cedf7a634f757caceef6 name=kata-runtime pid=3433 source=virtcontainers subsystem=qmp
time="2018-09-28T14:24:47.660766409Z" level=error msg="QMP command failed" arch=amd64 command=create container=14a9b78e50b3adf77415a93049859d6e9d4a1eacd0e4cedf7a634f757caceef6 name=kata-runtime pid=3433 source=runtime
time="2018-10-04T05:15:40.193629789Z" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=16483e67efd75e4c1f071a7c3f4ee3759378b15a0b8f243bd72ad3f1454a8646 error="open /run/vc/sbs/16483e67efd75e4c1f071a7c3f4ee3759378b15a0b8f243bd72ad3f1454a8646/devices.json: no such file or directory" name=kata-runtime pid=50849 sandbox=16483e67efd75e4c1f071a7c3f4ee3759378b15a0b8f243bd72ad3f1454a8646 sandboxid=16483e67efd75e4c1f071a7c3f4ee3759378b15a0b8f243bd72ad3f1454a8646 source=virtcontainers subsystem=sandbox
time="2018-10-04T05:15:45.135043735Z" level=error msg="Container not ready, running or paused, impossible to signal the container" arch=amd64 command=kill container=16483e67efd75e4c1f071a7c3f4ee3759378b15a0b8f243bd72ad3f1454a8646 name=kata-runtime pid=50948 sandbox=16483e67efd75e4c1f071a7c3f4ee3759378b15a0b8f243bd72ad3f1454a8646 source=runtime
time="2018-10-04T05:15:45.229057884Z" level=error msg="Container 16483e67efd75e4c1f071a7c3f4ee3759378b15a0b8f243bd72ad3f1454a8646 not ready, running or paused, cannot send a signal" arch=amd64 command=kill container=16483e67efd75e4c1f071a7c3f4ee3759378b15a0b8f243bd72ad3f1454a8646 name=kata-runtime pid=50975 sandbox=16483e67efd75e4c1f071a7c3f4ee3759378b15a0b8f243bd72ad3f1454a8646 source=runtime
time="2018-10-04T05:16:28.916942798Z" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=dd2ba912937db4d120aca58556e17f2a7b69093cb33019d4f6ccca1d873d79e7 error="open /run/vc/sbs/dd2ba912937db4d120aca58556e17f2a7b69093cb33019d4f6ccca1d873d79e7/devices.json: no such file or directory" name=kata-runtime pid=51045 sandbox=dd2ba912937db4d120aca58556e17f2a7b69093cb33019d4f6ccca1d873d79e7 sandboxid=dd2ba912937db4d120aca58556e17f2a7b69093cb33019d4f6ccca1d873d79e7 source=virtcontainers subsystem=sandbox
time="2018-10-04T05:16:32.407544203Z" level=info msg="{\"error\": {\"class\": \"GenericError\", \"desc\": \"Could not open '/dev/fd0': No such device or address\"}}" arch=amd64 command=create container=dd2ba912937db4d120aca58556e17f2a7b69093cb33019d4f6ccca1d873d79e7 name=kata-runtime pid=51045 source=virtcontainers subsystem=qmp
time="2018-10-04T05:16:32.583344209Z" level=error msg="QMP command failed" arch=amd64 command=create container=dd2ba912937db4d120aca58556e17f2a7b69093cb33019d4f6ccca1d873d79e7 name=kata-runtime pid=51045 source=runtime
```
## Proxy logs
Recent proxy problems found in system journal:
```
time="2018-09-28T13:48:33.490287582Z" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/0e974bf54f6a91f71df758f77e90ade8e94496b58350fd0a7ceaad8691d29d38/kata.sock: use of closed network connection" name=kata-proxy pid=1537 sandbox=0e974bf54f6a91f71df758f77e90ade8e94496b58350fd0a7ceaad8691d29d38 source=proxy
time="2018-09-28T14:03:23.506537995Z" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/3e149df97dd605c77108be66a2f84c3aac41baebf7e821181d7d18ee73e646c6/kata.sock: use of closed network connection" name=kata-proxy pid=1836 sandbox=3e149df97dd605c77108be66a2f84c3aac41baebf7e821181d7d18ee73e646c6 source=proxy
time="2018-09-28T14:06:20.752902083Z" level=fatal msg="channel error" error="accept unix /run/vc/sbs/f74ad8552767f55fca31c2acad1c03e1b8583d4594328ce7a492fa1344dcf11f/proxy.sock: use of closed network connection" name=kata-proxy pid=2092 sandbox=f74ad8552767f55fca31c2acad1c03e1b8583d4594328ce7a492fa1344dcf11f source=proxy
time="2018-09-28T14:06:28.087968426Z" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/5087baa6bd107d9eb65cd447ae6b312f821d78e0025b8c4d546421a9376cc94a/kata.sock: use of closed network connection" name=kata-proxy pid=2277 sandbox=5087baa6bd107d9eb65cd447ae6b312f821d78e0025b8c4d546421a9376cc94a source=proxy
time="2018-09-28T14:06:53.787655201Z" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/399932898dc5fb6b88bd43a6aa7a0b4ea93435a52042febf57a34c4825f839a3/kata.sock: use of closed network connection" name=kata-proxy pid=2454 sandbox=399932898dc5fb6b88bd43a6aa7a0b4ea93435a52042febf57a34c4825f839a3 source=proxy
time="2018-09-28T14:07:59.742602015Z" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/a807278057af5f6be3bf470a63015cd356e0f3add664902f7a299031781f92d6/kata.sock: use of closed network connection" name=kata-proxy pid=2542 sandbox=a807278057af5f6be3bf470a63015cd356e0f3add664902f7a299031781f92d6 source=proxy
time="2018-09-28T14:09:12.562427308Z" level=fatal msg="channel error" error="accept unix /run/vc/sbs/b77d1863ee992758e6f551748c01040a2cbae60c3771d27d7d1e15bace4fa47c/proxy.sock: use of closed network connection" name=kata-proxy pid=2633 sandbox=b77d1863ee992758e6f551748c01040a2cbae60c3771d27d7d1e15bace4fa47c source=proxy
time="2018-09-28T14:11:35.862977998Z" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/513a51d8cc51b9ee7b68683f96c87d041c2402c999830aa04cc9d58a9c34b2fe/kata.sock: use of closed network connection" name=kata-proxy pid=2834 sandbox=513a51d8cc51b9ee7b68683f96c87d041c2402c999830aa04cc9d58a9c34b2fe source=proxy
time="2018-09-28T14:11:52.400661032Z" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/264b44b94a7d31b6c0f11c2b88398233db81daa194d5b1ad2c8022c6eccd2669/kata.sock: use of closed network connection" name=kata-proxy pid=3029 sandbox=264b44b94a7d31b6c0f11c2b88398233db81daa194d5b1ad2c8022c6eccd2669 source=proxy
time="2018-09-28T14:18:59.335008741Z" level=fatal msg="channel error" error="accept unix /run/vc/sbs/7d65a9c8fd61662157cd654d8c3a2a6aca167244bc213060a81ca2330c8209eb/proxy.sock: use of closed network connection" name=kata-proxy pid=3195 sandbox=7d65a9c8fd61662157cd654d8c3a2a6aca167244bc213060a81ca2330c8209eb source=proxy
time="2018-09-28T14:24:35.056297907Z" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/a444e636cc86dc0e74d8e7b618e1e9e6eb31c50da4459d4b4f3ad961a4c999f2/kata.sock: use of closed network connection" name=kata-proxy pid=3283 sandbox=a444e636cc86dc0e74d8e7b618e1e9e6eb31c50da4459d4b4f3ad961a4c999f2 source=proxy
time="2018-09-28T14:24:47.625452594Z" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/14a9b78e50b3adf77415a93049859d6e9d4a1eacd0e4cedf7a634f757caceef6/kata.sock: use of closed network connection" name=kata-proxy pid=3469 sandbox=14a9b78e50b3adf77415a93049859d6e9d4a1eacd0e4cedf7a634f757caceef6 source=proxy
time="2018-10-04T05:15:45.303560689Z" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/16483e67efd75e4c1f071a7c3f4ee3759378b15a0b8f243bd72ad3f1454a8646/kata.sock: use of closed network connection" name=kata-proxy pid=50887 sandbox=16483e67efd75e4c1f071a7c3f4ee3759378b15a0b8f243bd72ad3f1454a8646 source=proxy
time="2018-10-04T05:16:32.541938537Z" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/dd2ba912937db4d120aca58556e17f2a7b69093cb33019d4f6ccca1d873d79e7/kata.sock: use of closed network connection" name=kata-proxy pid=51082 sandbox=dd2ba912937db4d120aca58556e17f2a7b69093cb33019d4f6ccca1d873d79e7 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:51 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:15 2018
OS/Arch: linux/amd64
Experimental: false
```
Output of "`docker info`":
```
Containers: 5
Running: 0
Paused: 0
Stopped: 5
Images: 2
Server Version: 18.06.1-ce
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
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: 468a545b9edcd5932818eb9de8e72413e616e86e
runc version: a786643 (expected: 69663f0bd4b60df09991c08812a60108003fa340)
init version: fec3683
Security Options:
apparmor
seccomp
Profile: default
Kernel Version: 4.15.0-34-generic
Operating System: Ubuntu 18.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 3.861GiB
Name: gru
ID: 7UP2:4PID:EVP6:A2HK:NZ2S:NYZI:SIVH:WQ6V:6ZTY:NT6S:HNOU:UT4B
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
File Descriptors: 23
Goroutines: 44
System Time: 2018-10-04T05:17:46.75093368Z
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 2018-09-28 13:47:16 UTC
WatchdogTimestampMonotonic=27636147
PermissionsStartOnly=no
RootDirectoryStartOnly=no
RemainAfterExit=no
GuessMainPID=yes
MainPID=771
ControlPID=0
FileDescriptorStoreMax=0
NFileDescriptorStore=0
StatusErrno=0
Result=success
UID=[not set]
GID=[not set]
NRestarts=0
ExecMainStartTimestamp=Fri 2018-09-28 13:47:13 UTC
ExecMainStartTimestampMonotonic=24506783
ExecMainExitTimestampMonotonic=0
ExecMainPID=771
ExecMainCode=0
ExecMainStatus=0
ExecStart={ path=/usr/bin/dockerd ; argv[]=/usr/bin/dockerd -D --add-runtime kata-runtime=/usr/bin/kata-runtime --default-runtime=kata-runtime ; 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=[not set]
CPUUsageNSec=[not set]
TasksCurrent=34
IPIngressBytes=18446744073709551615
IPIngressPackets=18446744073709551615
IPEgressBytes=18446744073709551615
IPEgressPackets=18446744073709551615
Delegate=yes
DelegateControllers=cpu cpuacct io blkio memory devices pids
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=no
MemoryLow=0
MemoryHigh=infinity
MemoryMax=infinity
MemorySwapMax=infinity
MemoryLimit=infinity
DevicePolicy=auto
TasksAccounting=yes
TasksMax=infinity
IPAccounting=no
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=1048576
LimitNOFILESoft=1048576
LimitAS=infinity
LimitASSoft=infinity
LimitNPROC=infinity
LimitNPROCSoft=infinity
LimitMEMLOCK=16777216
LimitMEMLOCKSoft=16777216
LimitLOCKS=infinity
LimitLOCKSSoft=infinity
LimitSIGPENDING=7391
LimitSIGPENDINGSoft=7391
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
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
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
SendSIGKILL=yes
SendSIGHUP=no
Id=docker.service
Names=docker.service
Requires=docker.socket system.slice sysinit.target
Wants=network-online.target
WantedBy=multi-user.target
ConsistsOf=docker.socket
Conflicts=shutdown.target
Before=shutdown.target multi-user.target
After=firewalld.service system.slice systemd-journald.socket network-online.target docker.socket basic.target sysinit.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 2018-09-28 13:47:16 UTC
StateChangeTimestampMonotonic=27636150
InactiveExitTimestamp=Fri 2018-09-28 13:47:13 UTC
InactiveExitTimestampMonotonic=24506828
ActiveEnterTimestamp=Fri 2018-09-28 13:47:16 UTC
ActiveEnterTimestampMonotonic=27636150
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 2018-09-28 13:47:13 UTC
ConditionTimestampMonotonic=24505846
AssertTimestamp=Fri 2018-09-28 13:47:13 UTC
AssertTimestampMonotonic=24505847
Transient=no
Perpetual=no
StartLimitIntervalUSec=1min
StartLimitBurst=3
StartLimitAction=none
FailureAction=none
SuccessAction=none
InvocationID=bacdd76ae51f4aa1bc1c5d23af1cfa30
CollectMode=inactive
```
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.3.0-35 amd64 Kata containers image
ii kata-ksm-throttler 1.3.0.git+6e903fb-36 amd64
ii kata-linux-container 4.14.67.12-138 amd64 linux kernel optimised for container-like workloads.
ii kata-proxy 1.3.0+git.6ddb006-35 amd64
ii kata-runtime 1.3.0+git.a786643-50 amd64
ii kata-shim 1.3.0+git.5fbf1f0-36 amd64
ii qemu-lite 2.11.0+git.f886228056-51 amd64 linux kernel optimised for container-like workloads.
ii qemu-vanilla 2.11.2+git.0982a56a55-49 amd64 linux kernel optimised for container-like workloads.
```
No `rpm`
---
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment