Attaching multiple network interfaces to Firecracker container about runtime

[tiri]

Show kata-collect-data.sh details

Meta details

Running kata-collect-data.sh version 1.13.0-alpha0 (commit cd63aacc9eaf6b59d32f900fe875d949a55e1b4d) at 2021-02-09.21:31:26.088274760+0000.

---

Runtime is /opt/kata/bin/kata-runtime.

kata-env

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

[Meta]
  Version = "1.0.24"

[Runtime]
  Debug = false
  Trace = false
  DisableGuestSeccomp = true
  DisableNewNetNs = false
  SandboxCgroupOnly = false
  Path = "/opt/kata/bin/kata-runtime"
  [Runtime.Version]
    OCI = "1.0.1-dev"
    [Runtime.Version.Version]
      Semver = "1.13.0-alpha0"
      Major = 1
      Minor = 13
      Patch = 0
      Commit = "cd63aacc9eaf6b59d32f900fe875d949a55e1b4d"
  [Runtime.Config]
    Path = "/opt/kata/share/defaults/kata-containers/configuration-qemu.toml"

[Hypervisor]
  MachineType = "pc"
  Version = "QEMU emulator version 5.0.0 (kata-static)\nCopyright (c) 2003-2020 Fabrice Bellard and the QEMU Project developers"
  Path = "/opt/kata/bin/qemu-system-x86_64"
  BlockDeviceDriver = "virtio-scsi"
  EntropySource = "/dev/urandom"
  SharedFS = "virtio-9p"
  VirtioFSDaemon = "/opt/kata/bin/virtiofsd"
  Msize9p = 8192
  MemorySlots = 10
  PCIeRootPort = 0
  HotplugVFIOOnRootBus = false
  Debug = false
  UseVSock = false

[Image]
  Path = "/opt/kata/share/kata-containers/kata-containers-image_clearlinux_1.13.0-alpha0_agent_27b90c2690.img"

[Kernel]
  Path = "/opt/kata/share/kata-containers/vmlinuz-5.4.60-91"
  Parameters = "systemd.unit=kata-containers.target systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket scsi_mod.scan=none"

[Initrd]
  Path = ""

[Proxy]
  Type = "kataProxy"
  Path = "/opt/kata/libexec/kata-containers/kata-proxy"
  Debug = false
  [Proxy.Version]
    Semver = "1.13.0-alpha0-5949d143613b7f40a5e59759bcea6cd9b79fd737"
    Major = 1
    Minor = 13
    Patch = 0
    Commit = "<<unknown>>"

[Shim]
  Type = "kataShim"
  Path = "/opt/kata/libexec/kata-containers/kata-shim"
  Debug = false
  [Shim.Version]
    Semver = "<<unknown>>"
    Major = 0
    Minor = 0
    Patch = 0
    Commit = "<<unknown>>"

[Agent]
  Type = "kata"
  Debug = false
  Trace = false
  TraceMode = ""
  TraceType = ""

[Host]
  Kernel = "4.15.0-135-generic"
  Architecture = "amd64"
  VMContainerCapable = true
  SupportVSocks = true
  [Host.Distro]
    Name = "Ubuntu"
    Version = "18.04"
  [Host.CPU]
    Vendor = "AuthenticAMD"
    Model = "AMD EPYC 7452 32-Core Processor"

[Netmon]
  Path = "/opt/kata/libexec/kata-containers/kata-netmon"
  Debug = false
  Enable = false
  [Netmon.Version]
    Semver = "1.13.0-alpha0"
    Major = 1
    Minor = 13
    Patch = 0
    Commit = "<<unknown>>"

---

Runtime config files

Runtime default config files

/etc/kata-containers/configuration.toml
/opt/kata/share/defaults/kata-containers/configuration.toml

Runtime config file contents

Config file /etc/kata-containers/configuration.toml not found
Output of "cat "/opt/kata/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 = "/opt/kata/bin/qemu-system-x86_64"
kernel = "/opt/kata/share/kata-containers/vmlinuz.container"
image = "/opt/kata/share/kata-containers/kata-containers.img"
machine_type = "pc"

# List of valid annotation names for the hypervisor
# Each member of the list is a regular expression, which is the base name
# of the annotation, e.g. "path" for io.katacontainers.config.hypervisor.path"
# The default if not set is empty (all annotations rejected.)
# Your distribution recommends: [".*"]
enable_annotations = [".*"]

# List of valid annotation values for the hypervisor path
# Each member of the list is a path pattern as described by glob(3).
# The default if not set is empty (all annotations rejected.)
# Your distribution recommends: ["/opt/kata/bin/qemu-system-x86_64"]
valid_hypervisor_paths = ["/opt/kata/bin/qemu-system-x86_64"]

# 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=""

# CPU features
# comma-separated list of cpu features to pass to the cpu
# For example, `cpu_features = "pmu=off,vmx=off"
cpu_features="pmu=off"

# 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.
# NOTICE: on arm platform with gicv2 interrupt controller, set it to 8.
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

# 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

# Specifies virtio-mem will be enabled or not.
# Please note that this option should be used with the command
# "echo 1 > /proc/sys/vm/overcommit_memory".
# Default false
#enable_virtio_mem = true

# 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

# Shared file system type:
#   - virtio-9p (default)
#   - virtio-fs
shared_fs = "virtio-9p"

# Path to vhost-user-fs daemon.
virtio_fs_daemon = "/opt/kata/bin/virtiofsd"

# List of valid annotation values for the virtiofs daemon path
# Each member of the list is a path pattern as described by glob(3).
# The default if not set is empty (all annotations rejected.)
# Your distribution recommends: ["/opt/kata/bin/virtiofsd"]
valid_virtio_fs_daemon_paths = ["/opt/kata/bin/virtiofsd"]

# Default size of DAX cache in MiB
virtio_fs_cache_size = 0

# Extra args for virtiofsd daemon
#
# Format example:
#   ["-o", "arg1=xxx,arg2", "-o", "hello world", "--arg3=yyy"]
#
# see `virtiofsd -h` for possible options.
virtio_fs_extra_args = []

# Cache mode:
#
#  - none
#    Metadata, data, and pathname lookup are not cached in guest. They are
#    always fetched from host and any changes are immediately pushed to host.
#
#  - auto
#    Metadata and pathname lookup cache expires after a configured amount of
#    time (default is 1 second). Data is cached while the file is open (close
#    to open consistency).
#
#  - always
#    Metadata, data, and pathname lookup are cached in guest and never expire.
virtio_fs_cache = "auto"

# 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 vhost-user storage device, default false
# Enabling this will result in some Linux reserved block type
# major range 240-254 being chosen to represent vhost-user devices.
enable_vhost_user_store = false

# The base directory specifically used for vhost-user devices.
# Its sub-path "block" is used for block devices; "block/sockets" is
# where we expect vhost-user sockets to live; "block/devices" is where
# simulated block device nodes for vhost-user devices to live.
vhost_user_store_path = "/var/run/kata-containers/vhost-user"

# Enable vIOMMU, default false
# Enabling this will result in the VM having a vIOMMU device
# This will also add the following options to the kernel's
# command line: intel_iommu=on,iommu=pt
#enable_iommu = true

# Enable IOMMU_PLATFORM, default false
# Enabling this will result in the VM device having iommu_platform=on set
#enable_iommu_platform = true

# List of valid annotation values for the vhost user store path
# Each member of the list is a path pattern as described by glob(3).
# The default if not set is empty (all annotations rejected.)
# Your distribution recommends: ["/var/run/kata-containers/vhost-user"]
valid_vhost_user_store_paths = ["/var/run/kata-containers/vhost-user"]

# Enable file based guest memory support. The default is an empty string which
# will disable this feature. In the case of virtio-fs, this is enabled
# automatically and '/dev/shm' is used as the backing folder.
# This option will be ignored if VM templating is enabled.
#file_mem_backend = ""

# List of valid annotation values for the file_mem_backend path
# Each member of the list is a path pattern as described by glob(3).
# The default if not set is empty (all annotations rejected.)
# Your distribution recommends: [""]
valid_file_mem_backends = [""]

# 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

# If false and nvdimm is supported, use nvdimm device to plug guest image.
# Otherwise virtio-block device is used.
# Default is false
#disable_image_nvdimm = 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

# Before hot plugging a PCIe device, you need to add a pcie_root_port device.
# Use this parameter when using some large PCI bar devices, such as Nvidia GPU
# The value means the number of pcie_root_port
# This value is valid when hotplug_vfio_on_root_bus is true and machine_type is "q35"
# Default 0
#pcie_root_port = 2

# If vhost-net backend for virtio-net is not desired, set to true. Default is false, which trades off
# security (vhost-net runs ring0) for network I/O performance.
#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

# Specifies the path of template.
#
# Default "/run/vc/vm/template"
#template_path = "/run/vc/vm/template"

# The number of caches of VMCache:
# unspecified or == 0   --> VMCache is disabled
# > 0                   --> will be set to the specified number
#
# VMCache is a function that creates VMs as caches before using it.
# It helps speed up new container creation.
# The function consists of a server and some clients communicating
# through Unix socket.  The protocol is gRPC in protocols/cache/cache.proto.
# The VMCache server will create some VMs and cache them by factory cache.
# It will convert the VM to gRPC format and transport it when gets
# requestion from clients.
# Factory grpccache is the VMCache client.  It will request gRPC format
# VM and convert it back to a VM.  If VMCache function is enabled,
# kata-runtime will request VM from factory grpccache when it creates
# a new sandbox.
#
# Default 0
#vm_cache_number = 0

# Specify the address of the Unix socket that is used by VMCache.
#
# Default /var/run/kata-containers/cache.sock
#vm_cache_endpoint = "/var/run/kata-containers/cache.sock"

# -pflash can add image file to VM. The arguments of it should be in format
# of ["/path/to/flash0.img", "/path/to/flash1.img"]
#pflashes = []

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

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

[shim.kata]
path = "/opt/kata/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]
# If enabled, make the agent display debug-level messages.
# (default: disabled)
#enable_debug = true

# Enable agent tracing.
#
# If enabled, the default trace mode is "dynamic" and the
# default trace type is "isolated". The trace mode and type are set
# explicity with the `trace_type=` and `trace_mode=` options.
#
# Notes:
#
# - Tracing is ONLY enabled when `enable_tracing` is set: explicitly
#   setting `trace_mode=` and/or `trace_type=` without setting `enable_tracing`
#   will NOT activate agent tracing.
#
# - See https://github.com/kata-containers/agent/blob/master/TRACING.md for
#   full details.
#
# (default: disabled)
#enable_tracing = true
#
#trace_mode = "dynamic"
#trace_type = "isolated"

# Comma separated list of kernel modules and their parameters.
# These modules will be loaded in the guest kernel using modprobe(8).
# The following example can be used to load two kernel modules with parameters
#  - kernel_modules=["e1000e InterruptThrottleRate=3000,3000,3000 EEE=1", "i915 enable_ppgtt=0"]
# The first word is considered as the module name and the rest as its parameters.
# Container will not be started when:
#  * A kernel module is specified and the modprobe command is not installed in the guest
#    or it fails loading the module.
#  * The module is not available in the guest or it doesn't met the guest kernel
#    requirements, like architecture and version.
#
kernel_modules=[]


[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 = "/opt/kata/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:
#
#   - 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="tcfilter"

# 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=tcfilter` 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

# if enabled, the runtime will add all the kata processes inside one dedicated cgroup.
# The container cgroups in the host are not created, just one single cgroup per sandbox.
# The runtime caller is free to restrict or collect cgroup stats of the overall Kata sandbox.
# The sandbox cgroup path is the parent cgroup of a container with the PodSandbox annotation.
# The sandbox cgroup is constrained if there is no container type annotation.
# See: https://godoc.org/github.com/kata-containers/runtime/virtcontainers#ContainerType
sandbox_cgroup_only=false

# Enabled experimental feature list, format: ["a", "b"].
# Experimental features are features not stable enough for production,
# they may break compatibility, and are prepared for a big version bump.
# Supported experimental features:
# (default: [])
experimental=[]


# If enabled, containers are allowed to join the pid namespace of the agent
# when the env variable KATA_AGENT_PIDNS is set for a container.
# Use this with caution and only when required, as this option allows the container
# to access the agent process. It is recommended to enable this option
# only in debug scenarios and with containers with lowered priveleges.
#enable_agent_pidns = true

Config file /usr/share/defaults/kata-containers/configuration.toml not found

---

KSM throttler

version

Output of " --version":

/opt/kata/bin/kata-collect-data.sh: line 178: --version: command not found

systemd service

Image details

---
osbuilder:
  url: "https://github.com/kata-containers/osbuilder"
  version: "unknown"
rootfs-creation-time: "2021-01-16T02:55:13.014961373+0000Z"
description: "osbuilder rootfs"
file-format-version: "0.0.2"
architecture: "x86_64"
base-distro:
  name: "Clear"
  version: "34170"
  packages:
    default:
      - "chrony"
      - "iptables-bin"
      - "kmod-bin"
      - "libudev0-shim"
      - "systemd"
      - "util-linux-bin"
    extra:

agent:
  url: "https://github.com/kata-containers/agent"
  name: "kata-agent"
  version: "1.13.0-alpha0-27b90c26909ba4b196b84156a4577a587c090285"
  agent-is-init-daemon: "no"

---

Initrd details

No initrd

---

Logfiles

Runtime logs

Recent runtime problems found in system journal:

time="2021-02-09T21:28:46.077852544Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.088215493Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.098580283Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.108849073Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.119291141Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.129677941Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.14004407Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.150485868Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.160989825Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.171319875Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.181686904Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.192094823Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.202456512Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.212768962Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.223133181Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.233461801Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.243763221Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.254193779Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.264634867Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.275072216Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.285496144Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.295954852Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.306374241Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.316800739Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.327246917Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.337681906Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.348112044Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.358540972Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.368963131Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.379418729Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.389857247Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.400277606Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.410714834Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.421148813Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.431591171Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.442151288Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.452708484Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.463142733Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.473527182Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.483873121Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.494178361Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.504485751Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.5148609Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.525296529Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.535770836Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:28:46.546181065Z" level=error msg="getting vm status failed" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="Get \"http://localhost/\": dial unix /run/vc/firecracker/74548f5a0e39059a483b483e3efcb6de/root/run/firecracker.socket: connect: connection refused" name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:29:01.59065252Z" level=warning msg="VM still running after waiting 15s" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d name=kata-runtime pid=19538 source=virtcontainers subsystem=firecracker
time="2021-02-09T21:29:01.689348597Z" level=warning msg="sandbox cgroups path is empty" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d name=kata-runtime pid=19538 sandbox=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d source=virtcontainers subsystem=sandbox
time="2021-02-09T21:29:01.877346735Z" level=warning msg="failed to cleanup netns" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d error="failed to get netns /var/run/netns/cnitest-adac7d1f-1ba7-5d0c-0417-4847109e4d94: failed to Statfs \"/var/run/netns/cnitest-adac7d1f-1ba7-5d0c-0417-4847109e4d94\": no such file or directory" name=kata-runtime path=/var/run/netns/cnitest-adac7d1f-1ba7-5d0c-0417-4847109e4d94 pid=19538 source=katautils
time="2021-02-09T21:29:01.877440954Z" level=error msg="Failed to connect to firecrackerinstance (timeout 10s)" arch=amd64 command=create container=74548f5a0e39059a483b483e3efcb6deab95501dd22eb6ba0dd995696dd92f8d name=kata-runtime pid=19538 source=runtime

Proxy logs

Recent proxy problems found in system journal:

time="2021-02-09T21:11:40.282758925Z" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/4776ee206f3d4ea49e3fa768e6710c24e61f8869c270a8fd9544831adb60a1e8/kata.sock: use of closed network connection" name=kata-proxy pid=13916 sandbox=4776ee206f3d4ea49e3fa768e6710c24e61f8869c270a8fd9544831adb60a1e8 source=proxy
time="2021-02-09T21:11:54.833250045Z" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/f22d8f0bd5cb1b31e1793b2eb2ad584011e57f98dcf1b3105fcc8434b70ceea3/kata.sock: use of closed network connection" name=kata-proxy pid=14414 sandbox=f22d8f0bd5cb1b31e1793b2eb2ad584011e57f98dcf1b3105fcc8434b70ceea3 source=proxy
time="2021-02-09T21:14:38.984166748Z" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/a1a3aa23185f8f603a985bdfde7a182eac9f2a813e7c6fabfd3654c1b4310045/kata.sock: use of closed network connection" name=kata-proxy pid=14913 sandbox=a1a3aa23185f8f603a985bdfde7a182eac9f2a813e7c6fabfd3654c1b4310045 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.3-ce
 API version:       1.38
 Go version:        go1.10.3
 Git commit:        d7080c1
 Built:             Wed Feb 20 02:28:10 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          18.06.3-ce
  API version:      1.38 (minimum version 1.12)
  Go version:       go1.10.3
  Git commit:       d7080c1
  Built:            Wed Feb 20 02:26:34 2019
  OS/Arch:          linux/amd64
  Experimental:     false

Output of "docker info":

Containers: 4
 Running: 2
 Paused: 0
 Stopped: 2
Images: 3
Server Version: 18.06.3-ce
Storage Driver: devicemapper
 Pool Name: docker-253:0-9568695-pool
 Pool Blocksize: 65.54kB
 Base Device Size: 10.74GB
 Backing Filesystem: xfs
 Udev Sync Supported: true
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Data Space Used: 176.2MB
 Data Space Total: 107.4GB
 Data Space Available: 107.2GB
 Metadata Space Used: 17.59MB
 Metadata Space Total: 2.147GB
 Metadata Space Available: 2.13GB
 Thin Pool Minimum Free Space: 10.74GB
 Deferred Removal Enabled: true
 Deferred Deletion Enabled: true
 Deferred Deleted Device Count: 0
 Library Version: 1.02.145 (2017-11-03)
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-fc kata-qemu runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 468a545b9edcd5932818eb9de8e72413e616e86e
runc version: a592beb5bc4c4092b1b1bac971afed27687340c5
init version: fec3683
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.15.0-135-generic
Operating System: Ubuntu 18.04.5 LTS
OSType: linux
Architecture: x86_64
CPUs: 64
Total Memory: 125.8GiB
Name: beast
ID: ZSLN:WQOB:RUI5:DJQG:A5RP:5UPV:AG4X:ZUDS:JKVP:M7KK:VERQ:7YDS
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

WARNING: devicemapper: usage of loopback devices is strongly discouraged for production use.
         Use `--storage-opt dm.thinpooldev` to specify a custom block storage device.
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=Tue 2021-02-09 21:03:34 UTC
WatchdogTimestampMonotonic=130273799
PermissionsStartOnly=no
RootDirectoryStartOnly=no
RemainAfterExit=no
GuessMainPID=yes
MainPID=1739
ControlPID=0
FileDescriptorStoreMax=0
NFileDescriptorStore=0
StatusErrno=0
Result=success
UID=[not set]
GID=[not set]
NRestarts=0
ExecMainStartTimestamp=Tue 2021-02-09 21:03:31 UTC
ExecMainStartTimestampMonotonic=127231069
ExecMainExitTimestampMonotonic=0
ExecMainPID=1739
ExecMainCode=0
ExecMainStatus=0
ExecStart={ path=/usr/bin/dockerd ; argv[]=/usr/bin/dockerd -H fd:// ; 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=134
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=67108864
LimitMEMLOCKSoft=67108864
LimitLOCKS=infinity
LimitLOCKSSoft=infinity
LimitSIGPENDING=514356
LimitSIGPENDINGSoft=514356
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
RestrictSUIDSGID=no
RestrictNamespaces=no
MountAPIVFS=no
KeyringMode=private
KillMode=process
KillSignal=15
SendSIGKILL=yes
SendSIGHUP=no
Id=docker.service
Names=docker.service
Requires=docker.socket sysinit.target system.slice
Wants=network-online.target
WantedBy=multi-user.target
ConsistsOf=docker.socket
Conflicts=shutdown.target
Before=shutdown.target multi-user.target
After=sysinit.target systemd-journald.socket system.slice basic.target firewalld.service docker.socket network-online.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
UnitFileState=enabled
UnitFilePreset=enabled
StateChangeTimestamp=Tue 2021-02-09 21:03:34 UTC
StateChangeTimestampMonotonic=130273801
InactiveExitTimestamp=Tue 2021-02-09 21:03:31 UTC
InactiveExitTimestampMonotonic=127231086
ActiveEnterTimestamp=Tue 2021-02-09 21:03:34 UTC
ActiveEnterTimestampMonotonic=130273801
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=Tue 2021-02-09 21:03:31 UTC
ConditionTimestampMonotonic=127230389
AssertTimestamp=Tue 2021-02-09 21:03:31 UTC
AssertTimestampMonotonic=127230389
Transient=no
Perpetual=no
StartLimitIntervalUSec=1min
StartLimitBurst=3
StartLimitAction=none
FailureAction=none
SuccessAction=none
InvocationID=6ff291b67d0a4a4baaa64dc9a9a94c05
CollectMode=inactive

No kubectl
No crio
Have containerd

containerd

Output of "containerd --version":

containerd containerd.io 1.4.3 269548fa27e0089a8b8278fc4fc781d7f65a939b

Output of "systemctl show containerd":

Type=notify
Restart=always
NotifyAccess=main
RestartUSec=5s
TimeoutStartUSec=1min 30s
TimeoutStopUSec=1min 30s
RuntimeMaxUSec=infinity
WatchdogUSec=0
WatchdogTimestamp=Tue 2021-02-09 21:03:32 UTC
WatchdogTimestampMonotonic=128411160
PermissionsStartOnly=no
RootDirectoryStartOnly=no
RemainAfterExit=no
GuessMainPID=yes
MainPID=1973
ControlPID=0
FileDescriptorStoreMax=0
NFileDescriptorStore=0
StatusErrno=0
Result=success
UID=[not set]
GID=[not set]
NRestarts=0
ExecMainStartTimestamp=Tue 2021-02-09 21:03:31 UTC
ExecMainStartTimestampMonotonic=127947177
ExecMainExitTimestampMonotonic=0
ExecMainPID=1973
ExecMainCode=0
ExecMainStatus=0
ExecStartPre={ path=/sbin/modprobe ; argv[]=/sbin/modprobe overlay ; ignore_errors=yes ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
ExecStart={ path=/usr/bin/containerd ; argv[]=/usr/bin/containerd ; ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
Slice=system.slice
ControlGroup=/system.slice/containerd.service
MemoryCurrent=[not set]
CPUUsageNSec=[not set]
TasksCurrent=22
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=67108864
LimitMEMLOCKSoft=67108864
LimitLOCKS=infinity
LimitLOCKSSoft=infinity
LimitSIGPENDING=514356
LimitSIGPENDINGSoft=514356
LimitMSGQUEUE=819200
LimitMSGQUEUESoft=819200
LimitNICE=0
LimitNICESoft=0
LimitRTPRIO=0
LimitRTPRIOSoft=0
LimitRTTIME=infinity
LimitRTTIMESoft=infinity
OOMScoreAdjust=-999
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
RestrictSUIDSGID=no
RestrictNamespaces=no
MountAPIVFS=no
KeyringMode=private
KillMode=process
KillSignal=15
SendSIGKILL=yes
SendSIGHUP=no
Id=containerd.service
Names=containerd.service
Requires=sysinit.target system.slice
WantedBy=multi-user.target
Conflicts=shutdown.target
Before=shutdown.target multi-user.target
After=network.target systemd-journald.socket basic.target sysinit.target system.slice local-fs.target
Documentation=https://containerd.io
Description=containerd container runtime
LoadState=loaded
ActiveState=active
SubState=running
FragmentPath=/lib/systemd/system/containerd.service
UnitFileState=enabled
UnitFilePreset=enabled
StateChangeTimestamp=Tue 2021-02-09 21:03:32 UTC
StateChangeTimestampMonotonic=128411161
InactiveExitTimestamp=Tue 2021-02-09 21:03:31 UTC
InactiveExitTimestampMonotonic=127263086
ActiveEnterTimestamp=Tue 2021-02-09 21:03:32 UTC
ActiveEnterTimestampMonotonic=128411161
ActiveExitTimestampMonotonic=0
InactiveEnterTimestampMonotonic=0
CanStart=yes
CanStop=yes
CanReload=no
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=Tue 2021-02-09 21:03:31 UTC
ConditionTimestampMonotonic=127262496
AssertTimestamp=Tue 2021-02-09 21:03:31 UTC
AssertTimestampMonotonic=127262497
Transient=no
Perpetual=no
StartLimitIntervalUSec=10s
StartLimitBurst=5
StartLimitAction=none
FailureAction=none
SuccessAction=none
InvocationID=e3b7b41859b44df598433bf30f7dc47b
CollectMode=inactive

Output of "cat /etc/containerd/config.toml":

#   Copyright 2018-2020 Docker Inc.

#   Licensed under the Apache License, Version 2.0 (the "License");
#   you may not use this file except in compliance with the License.
#   You may obtain a copy of the License at

#       http://www.apache.org/licenses/LICENSE-2.0

#   Unless required by applicable law or agreed to in writing, software
#   distributed under the License is distributed on an "AS IS" BASIS,
#   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
#   See the License for the specific language governing permissions and
#   limitations under the License.

disabled_plugins = ["cri"]

#root = "/var/lib/containerd"
#state = "/run/containerd"
#subreaper = true
#oom_score = 0

#[grpc]
#  address = "/run/containerd/containerd.sock"
#  uid = 0
#  gid = 0

#[debug]
#  address = "/run/containerd/debug.sock"
#  uid = 0
#  gid = 0
#  level = "info"

---

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-)"":

No rpm

---

[jodh-intel]

Hi @tiri - is this still an issue? What version of firecracker are you using? Can you confirm FC works with a single network interface? Have you tried Kata 2.x?

[tiri]

Hi @jodh-intel - thank you very much for paying attention to this issue.

I have tried the latest stable (1.12.1) and alpha (1.13.0) release assets, so for kata 1.13.0 it is firecracker 0.21.3. Everything works with a single interface, even QEMU runtime works with two interfaces. I did not attempt to use kata 2.x jet as Docker does not currently support the shim v2 interface.

[jodh-intel]

/cc @lifupan, @mcastelino for thoughts on FC + multiple NICs.

---

Docker does not currently support the shim v2 interface.

@tiri - That's true. However using Kata 2.x with containerd is quite similar to docker:

• Docker:

  $ sudo docker run -ti --runtime "kata-runtime" busybox sh
  

• Containerd:

  $ sudo ctr run -t --runtime "io.containerd.kata.v2" "docker.io/library/busybox:latest" foo sh

[fidencio]

---

This issue is being automatically closed as Kata Containers 1.x has now reached EOL (End of Life). This means it is no longer being maintained.

Important:

All users should switch to the latest Kata Containers 2.x release to ensure they are using a maintained release that contains the latest security fixes, performance improvements and new features.

This decision was discussed by the @kata-containers/architecture-committee and has been announced via the Kata Containers mailing list:

• http://lists.katacontainers.io/pipermail/kata-dev/2020-November/001601.html
• http://lists.katacontainers.io/pipermail/kata-dev/2021-April/001843.html
• http://lists.katacontainers.io/pipermail/kata-dev/2021-May/001896.html

If you believe this issue still applies to Kata Containers 2.x, please open an issue against the Kata Containers 2.x repository, pointing to this one, providing details to allow us to migrate it.

---