Description of problem

I have a pause container for sharing network namespaces

[root@gh-hulk-k8s-ep14 ~]# docker ps f93a7990757f registry-hulk.sankuai.com/google_containers/pause-amd64:3.0 "/pause" 21 hours ago Up 21 hours k8s_POD_my-app_default_ae4a5115-3ff5-11e9-b735-0022dfb3e5ab_0

Try to join the shared network namespace with --net=container but it will fail

[root@gh-hulk-k8s-ep14 ~]# docker run --runtime kata-runtime -tid --net=container:f93a7990757f centos:7 bash 6e0a9047e037cb427dc210c1cfc2bc66cf2e63250f1c7074313e558c4787fd0a /usr/bin/docker-current: Error response from daemon: oci runtime error: Error bridging virtual endpoint.

Running with runc is successful, but kata-runtime will fail
I see https://github.com/kata-containers/documentation/blob/master/Limitations.md#support-for-joining-an-existing-vm-network

Doesn't support joining to a shared network namespace? Is there any way to solve this problem?

Expected result

Run successfully

Actual result

[root@gh-hulk-k8s-ep14 ~]# docker run --runtime kata-runtime -tid --net=container:f93a7990757f centos:7 bash 6e0a9047e037cb427dc210c1cfc2bc66cf2e63250f1c7074313e558c4787fd0a /usr/bin/docker-current: Error response from daemon: oci runtime error: Error bridging virtual endpoint.

Meta details

Running kata-collect-data.sh version 1.5.0 (commit 5f7fcd7) at 2019-03-07.15:28:12.540947188+0800.

Runtime is /bin/kata-runtime.

`kata-env`

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

[Meta]
  Version = "1.0.20"

[Runtime]
  Debug = false
  Trace = false
  DisableGuestSeccomp = true
  DisableNewNetNs = false
  Path = "/usr/bin/kata-runtime"
  [Runtime.Version]
    Semver = "1.5.0"
    Commit = "5f7fcd7"
    OCI = "1.0.1-dev"
  [Runtime.Config]
    Path = "/usr/share/defaults/kata-containers/configuration.toml"

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

[Image]
  Path = "/usr/share/kata-containers/kata-containers-image_clearlinux_1.5.0_agent_a581aebf473.img"

[Kernel]
  Path = "/usr/share/kata-containers/vmlinuz-4.14.67.22-18.1.container"
  Parameters = "init=/usr/lib/systemd/systemd systemd.unit=kata-containers.target systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket"

[Initrd]
  Path = ""

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

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

[Agent]
  Type = "kata"

[Host]
  Kernel = "3.10.0-862.mt20181225.115.el7.x86_64"
  Architecture = "amd64"
  VMContainerCapable = true
  SupportVSocks = false
  [Host.Distro]
    Name = "CentOS Linux"
    Version = "7"
  [Host.CPU]
    Vendor = "GenuineIntel"
    Model = "Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz"

[Netmon]
  Version = "kata-netmon version 1.5.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"":

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

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

[hypervisor.qemu]
path = "/usr/bin/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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

KSM throttler

version

Output of "/usr/libexec/kata-ksm-throttler/kata-ksm-throttler --version":

kata-ksm-throttler version 1.5.0-3dd4c9f

Output of "/usr/lib/systemd/system/kata-ksm-throttler.service --version":

/bin/kata-collect-data.sh: line 168: /usr/lib/systemd/system/kata-ksm-throttler.service: Permission denied

systemd service

Image details

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

agent:
  url: "https://github.com/kata-containers/agent"
  name: "kata-agent"
  version: "1.5.0-a581aebf47386df570f796cb835bd23820448b9b"
  agent-is-init-daemon: "no"

Initrd details

No initrd

Logfiles

Runtime logs

Recent runtime problems found in system journal:

time="2019-03-06T17:53:56.725946722+08:00" level=error msg="Container ID (8728e4cc73a89a225bf422e0f690f535fc7bb295f5cc5a5a1bacf5cb85dbdc68) does not exist" arch=amd64 command=delete container=8728e4cc73a89a225bf422e0f690f535fc7bb295f5cc5a5a1bacf5cb85dbdc68 name=kata-runtime pid=293843 source=runtime
time="2019-03-06T17:53:57.01589143+08:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=48dd73390955d83807f5bbf0e1ebbd635387c214f4fce0569f2a21c40e88b733 error="open /run/vc/sbs/48dd73390955d83807f5bbf0e1ebbd635387c214f4fce0569f2a21c40e88b733/devices.json: no such file or directory" name=kata-runtime pid=293891 sandbox=48dd73390955d83807f5bbf0e1ebbd635387c214f4fce0569f2a21c40e88b733 sandboxid=48dd73390955d83807f5bbf0e1ebbd635387c214f4fce0569f2a21c40e88b733 source=virtcontainers subsystem=sandbox
time="2019-03-06T18:06:43.832792157+08:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=f93a7990757f8e325b888e15d3b4c53993460def30166d315a6ccdc0ca51523f error="open /run/vc/sbs/f93a7990757f8e325b888e15d3b4c53993460def30166d315a6ccdc0ca51523f/devices.json: no such file or directory" name=kata-runtime pid=300920 sandbox=f93a7990757f8e325b888e15d3b4c53993460def30166d315a6ccdc0ca51523f sandboxid=f93a7990757f8e325b888e15d3b4c53993460def30166d315a6ccdc0ca51523f source=virtcontainers subsystem=sandbox
time="2019-03-06T18:12:38.839818597+08:00" level=error msg="rpc error: code = Internal desc = Could not run process: container_linux.go:348: starting container process caused \"exec: \\\"bash\\\": executable file not found in $PATH\"" arch=amd64 command=exec container=f93a7990757f8e325b888e15d3b4c53993460def30166d315a6ccdc0ca51523f name=kata-runtime pid=304187 sandbox=f93a7990757f8e325b888e15d3b4c53993460def30166d315a6ccdc0ca51523f source=runtime
time="2019-03-06T18:12:43.749962198+08:00" level=error msg="rpc error: code = Internal desc = Could not run process: container_linux.go:348: starting container process caused \"exec: \\\"uname\\\": executable file not found in $PATH\"" arch=amd64 command=exec container=f93a7990757f8e325b888e15d3b4c53993460def30166d315a6ccdc0ca51523f name=kata-runtime pid=304230 sandbox=f93a7990757f8e325b888e15d3b4c53993460def30166d315a6ccdc0ca51523f source=runtime
time="2019-03-06T18:15:04.631095079+08:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=f3029e3ae9375b6192a03348a19d2c642793aa5b16bd773cb18e07d3519f3e69 error="open /run/vc/sbs/f3029e3ae9375b6192a03348a19d2c642793aa5b16bd773cb18e07d3519f3e69/devices.json: no such file or directory" name=kata-runtime pid=305731 sandbox=f3029e3ae9375b6192a03348a19d2c642793aa5b16bd773cb18e07d3519f3e69 sandboxid=f3029e3ae9375b6192a03348a19d2c642793aa5b16bd773cb18e07d3519f3e69 source=virtcontainers subsystem=sandbox
time="2019-03-06T18:15:05.573986255+08:00" level=warning msg="unsupported address" address="fe80::90b9:45ff:fe5b:c4a8/64" arch=amd64 command=create container=f3029e3ae9375b6192a03348a19d2c642793aa5b16bd773cb18e07d3519f3e69 name=kata-runtime pid=305731 source=virtcontainers subsystem=network unsupported-address-type=ipv6
time="2019-03-06T18:15:05.574154181+08:00" level=warning msg="unsupported route" arch=amd64 command=create container=f3029e3ae9375b6192a03348a19d2c642793aa5b16bd773cb18e07d3519f3e69 destination="fe80::/64" name=kata-runtime pid=305731 source=virtcontainers subsystem=network unsupported-route-type=ipv6
time="2019-03-06T18:15:05.796974243+08:00" level=error msg="rpc error: code = Internal desc = Could not run process: container_linux.go:348: starting container process caused \"exec: \\\"-v\\\": executable file not found in $PATH\"" arch=amd64 command=create container=f3029e3ae9375b6192a03348a19d2c642793aa5b16bd773cb18e07d3519f3e69 name=kata-runtime pid=305731 source=runtime
time="2019-03-06T18:15:05.845807576+08:00" level=error msg="Container ID (f3029e3ae9375b6192a03348a19d2c642793aa5b16bd773cb18e07d3519f3e69) does not exist" arch=amd64 command=delete container=f3029e3ae9375b6192a03348a19d2c642793aa5b16bd773cb18e07d3519f3e69 name=kata-runtime pid=305806 source=runtime
time="2019-03-06T18:15:05.897918731+08:00" level=error msg="Container ID (f3029e3ae9375b6192a03348a19d2c642793aa5b16bd773cb18e07d3519f3e69) does not exist" arch=amd64 command=delete container=f3029e3ae9375b6192a03348a19d2c642793aa5b16bd773cb18e07d3519f3e69 name=kata-runtime pid=305826 source=runtime
time="2019-03-06T18:15:27.244909792+08:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=acd4832457652b20979945ae1306932320372c4eef44353872fcf2492cf84670 error="open /run/vc/sbs/acd4832457652b20979945ae1306932320372c4eef44353872fcf2492cf84670/devices.json: no such file or directory" name=kata-runtime pid=305911 sandbox=acd4832457652b20979945ae1306932320372c4eef44353872fcf2492cf84670 sandboxid=acd4832457652b20979945ae1306932320372c4eef44353872fcf2492cf84670 source=virtcontainers subsystem=sandbox
time="2019-03-06T18:15:27.247302786+08:00" level=error msg="Error bridging virtual endpoint" arch=amd64 command=create container=acd4832457652b20979945ae1306932320372c4eef44353872fcf2492cf84670 error="Could not create TAP interface: LinkAdd() failed for macvtap name tap0_kata: file exists" name=kata-runtime pid=305911 source=virtcontainers subsystem=network
time="2019-03-06T18:15:27.266813571+08:00" level=error msg="Could not create TAP interface: LinkAdd() failed for macvtap name tap0_kata: file exists" arch=amd64 command=create container=acd4832457652b20979945ae1306932320372c4eef44353872fcf2492cf84670 name=kata-runtime pid=305911 source=runtime
time="2019-03-06T18:15:27.299092415+08:00" level=error msg="Container ID (acd4832457652b20979945ae1306932320372c4eef44353872fcf2492cf84670) does not exist" arch=amd64 command=delete container=acd4832457652b20979945ae1306932320372c4eef44353872fcf2492cf84670 name=kata-runtime pid=305946 source=runtime
time="2019-03-06T18:15:27.360352905+08:00" level=error msg="Container ID (acd4832457652b20979945ae1306932320372c4eef44353872fcf2492cf84670) does not exist" arch=amd64 command=delete container=acd4832457652b20979945ae1306932320372c4eef44353872fcf2492cf84670 name=kata-runtime pid=305963 source=runtime
time="2019-03-06T18:15:39.601862987+08:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=ebaca5b7c646300b016ca57ff96ab55b340d13d801cf790325bbba8b2b88893e error="open /run/vc/sbs/ebaca5b7c646300b016ca57ff96ab55b340d13d801cf790325bbba8b2b88893e/devices.json: no such file or directory" name=kata-runtime pid=306025 sandbox=ebaca5b7c646300b016ca57ff96ab55b340d13d801cf790325bbba8b2b88893e sandboxid=ebaca5b7c646300b016ca57ff96ab55b340d13d801cf790325bbba8b2b88893e source=virtcontainers subsystem=sandbox
time="2019-03-06T18:15:39.604067517+08:00" level=error msg="Error bridging virtual endpoint" arch=amd64 command=create container=ebaca5b7c646300b016ca57ff96ab55b340d13d801cf790325bbba8b2b88893e error="Could not create TAP interface: LinkAdd() failed for macvtap name tap0_kata: file exists" name=kata-runtime pid=306025 source=virtcontainers subsystem=network
time="2019-03-06T18:15:39.619767899+08:00" level=error msg="Could not create TAP interface: LinkAdd() failed for macvtap name tap0_kata: file exists" arch=amd64 command=create container=ebaca5b7c646300b016ca57ff96ab55b340d13d801cf790325bbba8b2b88893e name=kata-runtime pid=306025 source=runtime
time="2019-03-06T18:15:39.65532646+08:00" level=error msg="Container ID (ebaca5b7c646300b016ca57ff96ab55b340d13d801cf790325bbba8b2b88893e) does not exist" arch=amd64 command=delete container=ebaca5b7c646300b016ca57ff96ab55b340d13d801cf790325bbba8b2b88893e name=kata-runtime pid=306063 source=runtime
time="2019-03-06T18:15:39.716742903+08:00" level=error msg="Container ID (ebaca5b7c646300b016ca57ff96ab55b340d13d801cf790325bbba8b2b88893e) does not exist" arch=amd64 command=delete container=ebaca5b7c646300b016ca57ff96ab55b340d13d801cf790325bbba8b2b88893e name=kata-runtime pid=306082 source=runtime
time="2019-03-06T18:17:12.996291761+08:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=32d83f44d35fec304182d7aabbff1906d4a7b8344ab79566ca4bc3f6358e5927 error="open /run/vc/sbs/32d83f44d35fec304182d7aabbff1906d4a7b8344ab79566ca4bc3f6358e5927/devices.json: no such file or directory" name=kata-runtime pid=307171 sandbox=32d83f44d35fec304182d7aabbff1906d4a7b8344ab79566ca4bc3f6358e5927 sandboxid=32d83f44d35fec304182d7aabbff1906d4a7b8344ab79566ca4bc3f6358e5927 source=virtcontainers subsystem=sandbox
time="2019-03-06T18:17:13.001321292+08:00" level=error msg="Error bridging virtual endpoint" arch=amd64 command=create container=32d83f44d35fec304182d7aabbff1906d4a7b8344ab79566ca4bc3f6358e5927 error="Could not create TAP interface: LinkAdd() failed for macvtap name tap0_kata: file exists" name=kata-runtime pid=307171 source=virtcontainers subsystem=network
time="2019-03-06T18:17:13.018938657+08:00" level=error msg="Could not create TAP interface: LinkAdd() failed for macvtap name tap0_kata: file exists" arch=amd64 command=create container=32d83f44d35fec304182d7aabbff1906d4a7b8344ab79566ca4bc3f6358e5927 name=kata-runtime pid=307171 source=runtime
time="2019-03-06T18:17:13.052821677+08:00" level=error msg="Container ID (32d83f44d35fec304182d7aabbff1906d4a7b8344ab79566ca4bc3f6358e5927) does not exist" arch=amd64 command=delete container=32d83f44d35fec304182d7aabbff1906d4a7b8344ab79566ca4bc3f6358e5927 name=kata-runtime pid=307202 source=runtime
time="2019-03-06T18:17:13.11444974+08:00" level=error msg="Container ID (32d83f44d35fec304182d7aabbff1906d4a7b8344ab79566ca4bc3f6358e5927) does not exist" arch=amd64 command=delete container=32d83f44d35fec304182d7aabbff1906d4a7b8344ab79566ca4bc3f6358e5927 name=kata-runtime pid=307224 source=runtime
time="2019-03-07T03:30:02.001537768+08:00" level=error msg="rpc error: code = Internal desc = Could not run process: container_linux.go:348: starting container process caused \"exec: \\\"logrotate\\\": executable file not found in $PATH\"" arch=amd64 command=exec container=48dd73390955d83807f5bbf0e1ebbd635387c214f4fce0569f2a21c40e88b733 name=kata-runtime pid=260971 sandbox=48dd73390955d83807f5bbf0e1ebbd635387c214f4fce0569f2a21c40e88b733 source=runtime
time="2019-03-07T03:30:02.114998283+08:00" level=error msg="rpc error: code = Internal desc = Could not run process: container_linux.go:348: starting container process caused \"exec: \\\"logrotate\\\": executable file not found in $PATH\"" arch=amd64 command=exec container=f93a7990757f8e325b888e15d3b4c53993460def30166d315a6ccdc0ca51523f name=kata-runtime pid=261011 sandbox=f93a7990757f8e325b888e15d3b4c53993460def30166d315a6ccdc0ca51523f source=runtime
time="2019-03-07T03:30:02.282769219+08:00" level=error msg="rpc error: code = Internal desc = Could not run process: container_linux.go:348: starting container process caused \"exec: \\\"logrotate\\\": executable file not found in $PATH\"" arch=amd64 command=exec container=c58fa05d0188a0700bc3f0576282876ae78f9e515809ac2461e53898cb494822 name=kata-runtime pid=261053 sandbox=c58fa05d0188a0700bc3f0576282876ae78f9e515809ac2461e53898cb494822 source=runtime
time="2019-03-07T14:24:48.794937351+08:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=b47dfd76e0ce1a641d1c28286c942d2af77cd92b067b365aac1be61a86766a05 error="open /run/vc/sbs/b47dfd76e0ce1a641d1c28286c942d2af77cd92b067b365aac1be61a86766a05/devices.json: no such file or directory" name=kata-runtime pid=268118 sandbox=b47dfd76e0ce1a641d1c28286c942d2af77cd92b067b365aac1be61a86766a05 sandboxid=b47dfd76e0ce1a641d1c28286c942d2af77cd92b067b365aac1be61a86766a05 source=virtcontainers subsystem=sandbox
time="2019-03-07T14:24:48.797413836+08:00" level=error msg="Error bridging virtual endpoint" arch=amd64 command=create container=b47dfd76e0ce1a641d1c28286c942d2af77cd92b067b365aac1be61a86766a05 error="Could not create TAP interface: LinkAdd() failed for macvtap name tap0_kata: file exists" name=kata-runtime pid=268118 source=virtcontainers subsystem=network
time="2019-03-07T14:24:48.815860123+08:00" level=error msg="Could not create TAP interface: LinkAdd() failed for macvtap name tap0_kata: file exists" arch=amd64 command=create container=b47dfd76e0ce1a641d1c28286c942d2af77cd92b067b365aac1be61a86766a05 name=kata-runtime pid=268118 source=runtime
time="2019-03-07T14:24:48.84826082+08:00" level=error msg="Container ID (b47dfd76e0ce1a641d1c28286c942d2af77cd92b067b365aac1be61a86766a05) does not exist" arch=amd64 command=delete container=b47dfd76e0ce1a641d1c28286c942d2af77cd92b067b365aac1be61a86766a05 name=kata-runtime pid=268152 source=runtime
time="2019-03-07T14:24:48.907864172+08:00" level=error msg="Container ID (b47dfd76e0ce1a641d1c28286c942d2af77cd92b067b365aac1be61a86766a05) does not exist" arch=amd64 command=delete container=b47dfd76e0ce1a641d1c28286c942d2af77cd92b067b365aac1be61a86766a05 name=kata-runtime pid=268171 source=runtime
time="2019-03-07T14:45:25.134733626+08:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=f344eed9a5fa4b5bf0f45d492fbc24193c3a4e3e9e47b74c0bb2af5fe2225601 error="open /run/vc/sbs/f344eed9a5fa4b5bf0f45d492fbc24193c3a4e3e9e47b74c0bb2af5fe2225601/devices.json: no such file or directory" name=kata-runtime pid=280312 sandbox=f344eed9a5fa4b5bf0f45d492fbc24193c3a4e3e9e47b74c0bb2af5fe2225601 sandboxid=f344eed9a5fa4b5bf0f45d492fbc24193c3a4e3e9e47b74c0bb2af5fe2225601 source=virtcontainers subsystem=sandbox
time="2019-03-07T14:45:25.137695009+08:00" level=error msg="Error bridging virtual endpoint" arch=amd64 command=create container=f344eed9a5fa4b5bf0f45d492fbc24193c3a4e3e9e47b74c0bb2af5fe2225601 error="Could not create TAP interface: LinkAdd() failed for macvtap name tap0_kata: file exists" name=kata-runtime pid=280312 source=virtcontainers subsystem=network
time="2019-03-07T14:45:25.164813514+08:00" level=error msg="Could not create TAP interface: LinkAdd() failed for macvtap name tap0_kata: file exists" arch=amd64 command=create container=f344eed9a5fa4b5bf0f45d492fbc24193c3a4e3e9e47b74c0bb2af5fe2225601 name=kata-runtime pid=280312 source=runtime
time="2019-03-07T14:45:25.199483645+08:00" level=error msg="Container ID (f344eed9a5fa4b5bf0f45d492fbc24193c3a4e3e9e47b74c0bb2af5fe2225601) does not exist" arch=amd64 command=delete container=f344eed9a5fa4b5bf0f45d492fbc24193c3a4e3e9e47b74c0bb2af5fe2225601 name=kata-runtime pid=280344 source=runtime
time="2019-03-07T14:45:25.252986351+08:00" level=error msg="Container ID (f344eed9a5fa4b5bf0f45d492fbc24193c3a4e3e9e47b74c0bb2af5fe2225601) does not exist" arch=amd64 command=delete container=f344eed9a5fa4b5bf0f45d492fbc24193c3a4e3e9e47b74c0bb2af5fe2225601 name=kata-runtime pid=280364 source=runtime
time="2019-03-07T15:09:51.820615387+08:00" level=error msg="Container ID (c58fa05d0188a0700bc3f0576282876ae78f9e515809ac2461e53898cb494822) does not exist" arch=amd64 command=delete container=c58fa05d0188a0700bc3f0576282876ae78f9e515809ac2461e53898cb494822 name=kata-runtime pid=294104 source=runtime
time="2019-03-07T15:22:30.784802131+08:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=5e0da7d685063369fa36b2c382e2dd4e484cd8fe496e1d5edea24c95e8afaf17 error="open /run/vc/sbs/5e0da7d685063369fa36b2c382e2dd4e484cd8fe496e1d5edea24c95e8afaf17/devices.json: no such file or directory" name=kata-runtime pid=299860 sandbox=5e0da7d685063369fa36b2c382e2dd4e484cd8fe496e1d5edea24c95e8afaf17 sandboxid=5e0da7d685063369fa36b2c382e2dd4e484cd8fe496e1d5edea24c95e8afaf17 source=virtcontainers subsystem=sandbox
time="2019-03-07T15:22:30.786964799+08:00" level=error msg="Error bridging virtual endpoint" arch=amd64 command=create container=5e0da7d685063369fa36b2c382e2dd4e484cd8fe496e1d5edea24c95e8afaf17 error="Could not create TAP interface: LinkAdd() failed for macvtap name tap0_kata: file exists" name=kata-runtime pid=299860 source=virtcontainers subsystem=network
time="2019-03-07T15:22:30.80691707+08:00" level=error msg="Could not create TAP interface: LinkAdd() failed for macvtap name tap0_kata: file exists" arch=amd64 command=create container=5e0da7d685063369fa36b2c382e2dd4e484cd8fe496e1d5edea24c95e8afaf17 name=kata-runtime pid=299860 source=runtime
time="2019-03-07T15:22:30.839260324+08:00" level=error msg="Container ID (5e0da7d685063369fa36b2c382e2dd4e484cd8fe496e1d5edea24c95e8afaf17) does not exist" arch=amd64 command=delete container=5e0da7d685063369fa36b2c382e2dd4e484cd8fe496e1d5edea24c95e8afaf17 name=kata-runtime pid=299894 source=runtime
time="2019-03-07T15:22:30.902473443+08:00" level=error msg="Container ID (5e0da7d685063369fa36b2c382e2dd4e484cd8fe496e1d5edea24c95e8afaf17) does not exist" arch=amd64 command=delete container=5e0da7d685063369fa36b2c382e2dd4e484cd8fe496e1d5edea24c95e8afaf17 name=kata-runtime pid=299912 source=runtime
time="2019-03-07T15:22:35.800968451+08:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=6e0a9047e037cb427dc210c1cfc2bc66cf2e63250f1c7074313e558c4787fd0a error="open /run/vc/sbs/6e0a9047e037cb427dc210c1cfc2bc66cf2e63250f1c7074313e558c4787fd0a/devices.json: no such file or directory" name=kata-runtime pid=299985 sandbox=6e0a9047e037cb427dc210c1cfc2bc66cf2e63250f1c7074313e558c4787fd0a sandboxid=6e0a9047e037cb427dc210c1cfc2bc66cf2e63250f1c7074313e558c4787fd0a source=virtcontainers subsystem=sandbox
time="2019-03-07T15:22:35.805885431+08:00" level=error msg="Error bridging virtual endpoint" arch=amd64 command=create container=6e0a9047e037cb427dc210c1cfc2bc66cf2e63250f1c7074313e558c4787fd0a error="Could not create TAP interface: LinkAdd() failed for macvtap name tap0_kata: file exists" name=kata-runtime pid=299985 source=virtcontainers subsystem=network
time="2019-03-07T15:22:35.827906537+08:00" level=error msg="Could not create TAP interface: LinkAdd() failed for macvtap name tap0_kata: file exists" arch=amd64 command=create container=6e0a9047e037cb427dc210c1cfc2bc66cf2e63250f1c7074313e558c4787fd0a name=kata-runtime pid=299985 source=runtime
time="2019-03-07T15:22:35.861495718+08:00" level=error msg="Container ID (6e0a9047e037cb427dc210c1cfc2bc66cf2e63250f1c7074313e558c4787fd0a) does not exist" arch=amd64 command=delete container=6e0a9047e037cb427dc210c1cfc2bc66cf2e63250f1c7074313e558c4787fd0a name=kata-runtime pid=300014 source=runtime
time="2019-03-07T15:22:35.922428836+08:00" level=error msg="Container ID (6e0a9047e037cb427dc210c1cfc2bc66cf2e63250f1c7074313e558c4787fd0a) does not exist" arch=amd64 command=delete container=6e0a9047e037cb427dc210c1cfc2bc66cf2e63250f1c7074313e558c4787fd0a name=kata-runtime pid=300029 source=runtime

Proxy logs

Recent proxy problems found in system journal:

time="2019-03-06T17:32:52.217306164+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/96bfcfd18e32783d69e24989a48d17028d7558b3972a5051c179fa60b488a151/kata.sock: use of closed network connection" name=kata-proxy pid=269024 sandbox=96bfcfd18e32783d69e24989a48d17028d7558b3972a5051c179fa60b488a151 source=proxy
time="2019-03-06T17:32:55.986242027+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/960565509e1c914a715e29f824e80f44aea7dbc8bbc8f82f7f35e5922b973522/kata.sock: use of closed network connection" name=kata-proxy pid=271844 sandbox=960565509e1c914a715e29f824e80f44aea7dbc8bbc8f82f7f35e5922b973522 source=proxy
time="2019-03-06T17:32:59.166948206+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/1c2af7018e36c05010cd28cb528f8b4d6f8c909019c770361bf8dd14392b3041/proxy.sock: use of closed network connection" name=kata-proxy pid=272202 sandbox=1c2af7018e36c05010cd28cb528f8b4d6f8c909019c770361bf8dd14392b3041 source=proxy
time="2019-03-06T17:33:02.326715324+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/ddaafda19801121ccdf3872ca7f9e15bb91bc28e7034510ae265015104a02172/proxy.sock: use of closed network connection" name=kata-proxy pid=272458 sandbox=ddaafda19801121ccdf3872ca7f9e15bb91bc28e7034510ae265015104a02172 source=proxy
time="2019-03-06T17:33:05.454079866+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/060f2f723366f36bded0b8ea36c4b320f44e43840917a01756732a0ef838cd68/kata.sock: use of closed network connection" name=kata-proxy pid=273054 sandbox=060f2f723366f36bded0b8ea36c4b320f44e43840917a01756732a0ef838cd68 source=proxy
time="2019-03-06T17:33:08.651471167+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/f741a0a57cfe402ebd14c8b514d19962e55dbddfe0eb1a6093517bb566e11126/proxy.sock: use of closed network connection" name=kata-proxy pid=273313 sandbox=f741a0a57cfe402ebd14c8b514d19962e55dbddfe0eb1a6093517bb566e11126 source=proxy
time="2019-03-06T17:33:11.838085426+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/b33c5105259dc33bc4d05aadf392855dada74d182fee3971d0ad0d2f05f84907/kata.sock: use of closed network connection" name=kata-proxy pid=273578 sandbox=b33c5105259dc33bc4d05aadf392855dada74d182fee3971d0ad0d2f05f84907 source=proxy
time="2019-03-06T17:33:15.02244651+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/9d239639124a5f3c013cd9ea1a997d2a190f772f65354e336aa2cf5dca654239/kata.sock: use of closed network connection" name=kata-proxy pid=273814 sandbox=9d239639124a5f3c013cd9ea1a997d2a190f772f65354e336aa2cf5dca654239 source=proxy
time="2019-03-06T17:33:18.125512215+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/517876a697b3773f468da381550b07705d5ae576fe02070ba0e87fd2376ef24f/proxy.sock: use of closed network connection" name=kata-proxy pid=274056 sandbox=517876a697b3773f468da381550b07705d5ae576fe02070ba0e87fd2376ef24f source=proxy
time="2019-03-06T17:33:21.224013471+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/ee45673cbca66c24b0e293f76a53e51fdbf8a0f895b7e90b36cf2a9194dc380b/kata.sock: use of closed network connection" name=kata-proxy pid=274301 sandbox=ee45673cbca66c24b0e293f76a53e51fdbf8a0f895b7e90b36cf2a9194dc380b source=proxy
time="2019-03-06T17:33:24.382900158+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/6692931e108d452f8fd9d7d5e452a8277f955c092802711c21ecd027ff11774c/kata.sock: use of closed network connection" name=kata-proxy pid=274559 sandbox=6692931e108d452f8fd9d7d5e452a8277f955c092802711c21ecd027ff11774c source=proxy
time="2019-03-06T17:33:27.538538675+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/1450a52b80e3b27a5b3e80f5bd027d7648cabf89e4d312275b1307f28a9e827d/proxy.sock: use of closed network connection" name=kata-proxy pid=274793 sandbox=1450a52b80e3b27a5b3e80f5bd027d7648cabf89e4d312275b1307f28a9e827d source=proxy
time="2019-03-06T17:33:30.657078535+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/036e2e4039ed5063167acbc0f18ada7f65b4e3bff8e02d09efdbfd5a16b9da7b/kata.sock: use of closed network connection" name=kata-proxy pid=275035 sandbox=036e2e4039ed5063167acbc0f18ada7f65b4e3bff8e02d09efdbfd5a16b9da7b source=proxy
time="2019-03-06T17:33:34.855323732+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/46164c53d0efc94a454504e07ed3ba5a9d8b64dc715a0518cc8045104127684f/kata.sock: use of closed network connection" name=kata-proxy pid=275305 sandbox=46164c53d0efc94a454504e07ed3ba5a9d8b64dc715a0518cc8045104127684f source=proxy
time="2019-03-06T17:33:39.059160501+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/0a043ae1507945533aec191dfd70a85b514ba929b798a75659fafd345d0f9368/kata.sock: use of closed network connection" name=kata-proxy pid=275549 sandbox=0a043ae1507945533aec191dfd70a85b514ba929b798a75659fafd345d0f9368 source=proxy
time="2019-03-06T17:33:42.284849703+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/ddde2d8dfd430406384bb8b0572ec037b1fcb76a14544439fa75b6739ce51949/kata.sock: use of closed network connection" name=kata-proxy pid=275814 sandbox=ddde2d8dfd430406384bb8b0572ec037b1fcb76a14544439fa75b6739ce51949 source=proxy
time="2019-03-06T17:33:45.399542216+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/8a4d42f68be9d03be07741225001c6562958defa7b88272fcc81f6b8b8915f71/kata.sock: use of closed network connection" name=kata-proxy pid=276059 sandbox=8a4d42f68be9d03be07741225001c6562958defa7b88272fcc81f6b8b8915f71 source=proxy
time="2019-03-06T17:33:48.535565371+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/e5b6fab443072e5ad995f12b8bfabe2ec1302bfaf94dd35503ec9e22f7fdce3b/kata.sock: use of closed network connection" name=kata-proxy pid=276292 sandbox=e5b6fab443072e5ad995f12b8bfabe2ec1302bfaf94dd35503ec9e22f7fdce3b source=proxy
time="2019-03-06T17:33:51.678608889+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/d4f48c4d8e2ae42407d09fd771de7339690de1fed8a1b7172fbde11915e5ed1b/kata.sock: use of closed network connection" name=kata-proxy pid=276529 sandbox=d4f48c4d8e2ae42407d09fd771de7339690de1fed8a1b7172fbde11915e5ed1b source=proxy
time="2019-03-06T17:33:54.795768064+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/b6aeac64907520442e1034331b514f5bc02e598ac3534a4afeace100ef00064d/proxy.sock: use of closed network connection" name=kata-proxy pid=276792 sandbox=b6aeac64907520442e1034331b514f5bc02e598ac3534a4afeace100ef00064d source=proxy
time="2019-03-06T17:33:58.018078133+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/018cce975accf014a842010c3859e72a11b4734318ee1d01873e4eb1de7e655b/kata.sock: use of closed network connection" name=kata-proxy pid=277036 sandbox=018cce975accf014a842010c3859e72a11b4734318ee1d01873e4eb1de7e655b source=proxy
time="2019-03-06T17:34:01.156862965+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/a0baae35a2d9c45e3381f45009d3c1525826e179a37d686c189a8adbde7cc402/kata.sock: use of closed network connection" name=kata-proxy pid=277397 sandbox=a0baae35a2d9c45e3381f45009d3c1525826e179a37d686c189a8adbde7cc402 source=proxy
time="2019-03-06T17:34:04.413874923+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/26a88883b0e1524b82437e9fa473c22da7ed672a287df62d8cbb24873822ca31/kata.sock: use of closed network connection" name=kata-proxy pid=277997 sandbox=26a88883b0e1524b82437e9fa473c22da7ed672a287df62d8cbb24873822ca31 source=proxy
time="2019-03-06T17:34:07.679174554+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/acdb9fc8e0c5365e04c3c887147d18348a9ec59fd80d2618f32585627854372b/kata.sock: use of closed network connection" name=kata-proxy pid=278242 sandbox=acdb9fc8e0c5365e04c3c887147d18348a9ec59fd80d2618f32585627854372b source=proxy
time="2019-03-06T17:34:10.937650791+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/85304cd2b4fa7b486797e3516b53e2310de9e72b459d175a414bcabfac21d30b/kata.sock: use of closed network connection" name=kata-proxy pid=278493 sandbox=85304cd2b4fa7b486797e3516b53e2310de9e72b459d175a414bcabfac21d30b source=proxy
time="2019-03-06T17:34:14.032749242+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/7bc110c25c863b313ed7907622c41c3c6abf6052e2328750cec062df98db7e0c/proxy.sock: use of closed network connection" name=kata-proxy pid=278755 sandbox=7bc110c25c863b313ed7907622c41c3c6abf6052e2328750cec062df98db7e0c source=proxy
time="2019-03-06T17:34:17.256194151+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/6f9a75e56eb8f01876b4172be98b5951b4aa926523f8d63c7b8e92a8f993cf50/proxy.sock: use of closed network connection" name=kata-proxy pid=279004 sandbox=6f9a75e56eb8f01876b4172be98b5951b4aa926523f8d63c7b8e92a8f993cf50 source=proxy
time="2019-03-06T17:34:19.068440469+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/efba988ff50a685a198cefc21f022c17d4aba830297d5c19bb18a3187e07e522/proxy.sock: use of closed network connection" name=kata-proxy pid=279244 sandbox=efba988ff50a685a198cefc21f022c17d4aba830297d5c19bb18a3187e07e522 source=proxy
time="2019-03-06T17:35:53.484394475+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/9c57de81362e7913d0f000905844d03724140fdcbb321e303ecda540962dc940/proxy.sock: use of closed network connection" name=kata-proxy pid=280387 sandbox=9c57de81362e7913d0f000905844d03724140fdcbb321e303ecda540962dc940 source=proxy
time="2019-03-06T17:35:55.120599915+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/9103e4b96e0e9a5e8f8dcd9adbb7660884316c21d2117557eb1c458b6c7ed71f/kata.sock: use of closed network connection" name=kata-proxy pid=280252 sandbox=9103e4b96e0e9a5e8f8dcd9adbb7660884316c21d2117557eb1c458b6c7ed71f source=proxy
time="2019-03-06T17:35:58.924200686+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/eec4120fa34dc515b31ed1da0f09d2494a17d0cb6eeb4864dfc2448cbd6b4e08/proxy.sock: use of closed network connection" name=kata-proxy pid=280923 sandbox=eec4120fa34dc515b31ed1da0f09d2494a17d0cb6eeb4864dfc2448cbd6b4e08 source=proxy
time="2019-03-06T17:35:59.539901687+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/8d65ffe2733aad02dca50e1672491b3ab39dfbee6097c37b31c3d59a92e79621/kata.sock: use of closed network connection" name=kata-proxy pid=280690 sandbox=8d65ffe2733aad02dca50e1672491b3ab39dfbee6097c37b31c3d59a92e79621 source=proxy
time="2019-03-06T17:36:03.414206142+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/bae066d0a9456c6ab9a87d90aac30b50a5f3c9acaa9e364e05824c0e09360933/proxy.sock: use of closed network connection" name=kata-proxy pid=281174 sandbox=bae066d0a9456c6ab9a87d90aac30b50a5f3c9acaa9e364e05824c0e09360933 source=proxy
time="2019-03-06T17:36:06.549109377+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/344602ddc4d36c3fed12b058d3db2b1203b42151c933ba40fb97e9bdae9ef87f/kata.sock: use of closed network connection" name=kata-proxy pid=281793 sandbox=344602ddc4d36c3fed12b058d3db2b1203b42151c933ba40fb97e9bdae9ef87f source=proxy
time="2019-03-06T17:36:09.722878752+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/92b425d24709206a636342297cb9f277d469abea1f0c45248427da0188eca510/kata.sock: use of closed network connection" name=kata-proxy pid=282196 sandbox=92b425d24709206a636342297cb9f277d469abea1f0c45248427da0188eca510 source=proxy
time="2019-03-06T17:36:10.401179575+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/b3c57b1fe8ba895e92b0f7433d58767b8e116b40872f786835587a0486c2752c/kata.sock: use of closed network connection" name=kata-proxy pid=282050 sandbox=b3c57b1fe8ba895e92b0f7433d58767b8e116b40872f786835587a0486c2752c source=proxy
time="2019-03-06T17:53:27.081246974+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/3acaa6c1d6c6f678cd8d9514145d396ae7ef3140e7b5482ca607203204692001/kata.sock: use of closed network connection" name=kata-proxy pid=291042 sandbox=3acaa6c1d6c6f678cd8d9514145d396ae7ef3140e7b5482ca607203204692001 source=proxy
time="2019-03-06T17:53:28.448124563+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/f93a7990757f8e325b888e15d3b4c53993460def30166d315a6ccdc0ca51523f/proxy.sock: use of closed network connection" name=kata-proxy pid=290885 sandbox=f93a7990757f8e325b888e15d3b4c53993460def30166d315a6ccdc0ca51523f source=proxy
time="2019-03-06T17:53:32.348284201+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/3acaa6c1d6c6f678cd8d9514145d396ae7ef3140e7b5482ca607203204692001/kata.sock: use of closed network connection" name=kata-proxy pid=291509 sandbox=3acaa6c1d6c6f678cd8d9514145d396ae7ef3140e7b5482ca607203204692001 source=proxy
time="2019-03-06T17:53:32.693736351+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/d804a49d86b3f1217ccc8662f589c41d7fe9b8905e5f8165bc107d3ec495ea5c/kata.sock: use of closed network connection" name=kata-proxy pid=291375 sandbox=d804a49d86b3f1217ccc8662f589c41d7fe9b8905e5f8165bc107d3ec495ea5c source=proxy
time="2019-03-06T17:53:36.603687062+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/ffb8fb28daf61a7718afeedef3c0d152d419acbd5e1fb62f592a00c8210d756a/proxy.sock: use of closed network connection" name=kata-proxy pid=291836 sandbox=ffb8fb28daf61a7718afeedef3c0d152d419acbd5e1fb62f592a00c8210d756a source=proxy
time="2019-03-06T17:53:39.708365151+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/b3f863578d1206369b19d7a1c959c1772d507b18fb885a485e7293b64ffe507d/kata.sock: use of closed network connection" name=kata-proxy pid=292092 sandbox=b3f863578d1206369b19d7a1c959c1772d507b18fb885a485e7293b64ffe507d source=proxy
time="2019-03-06T17:53:42.811321236+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/1627dd3c967e307d594668f52b91c27c02a65b79e92d8d5bad04068db5093f03/proxy.sock: use of closed network connection" name=kata-proxy pid=292341 sandbox=1627dd3c967e307d594668f52b91c27c02a65b79e92d8d5bad04068db5093f03 source=proxy
time="2019-03-06T17:53:46.000306454+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/3acaa6c1d6c6f678cd8d9514145d396ae7ef3140e7b5482ca607203204692001/proxy.sock: use of closed network connection" name=kata-proxy pid=292711 sandbox=3acaa6c1d6c6f678cd8d9514145d396ae7ef3140e7b5482ca607203204692001 source=proxy
time="2019-03-06T17:53:46.344171909+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/6f984c1ddf3f61557e7b7bc5a4f7287385106c3a917f667d38c61c45c12f6311/proxy.sock: use of closed network connection" name=kata-proxy pid=292576 sandbox=6f984c1ddf3f61557e7b7bc5a4f7287385106c3a917f667d38c61c45c12f6311 source=proxy
time="2019-03-06T17:53:50.312556742+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/2c1b01222e5fa870e811c041aca3ab1d885ca7e9c698f52cd79d7f1082df372b/proxy.sock: use of closed network connection" name=kata-proxy pid=293053 sandbox=2c1b01222e5fa870e811c041aca3ab1d885ca7e9c698f52cd79d7f1082df372b source=proxy
time="2019-03-06T17:53:53.486837794+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/c7efabd29e74641e6f9d21b027ecc7230018937c7e5b8d5278c3ed36b816502b/proxy.sock: use of closed network connection" name=kata-proxy pid=293287 sandbox=c7efabd29e74641e6f9d21b027ecc7230018937c7e5b8d5278c3ed36b816502b source=proxy
time="2019-03-06T17:53:56.613329395+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/8728e4cc73a89a225bf422e0f690f535fc7bb295f5cc5a5a1bacf5cb85dbdc68/proxy.sock: use of closed network connection" name=kata-proxy pid=293563 sandbox=8728e4cc73a89a225bf422e0f690f535fc7bb295f5cc5a5a1bacf5cb85dbdc68 source=proxy
time="2019-03-06T18:15:05.778432218+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/f3029e3ae9375b6192a03348a19d2c642793aa5b16bd773cb18e07d3519f3e69/kata.sock: use of closed network connection" name=kata-proxy pid=305770 sandbox=f3029e3ae9375b6192a03348a19d2c642793aa5b16bd773cb18e07d3519f3e69 source=proxy
time="2019-03-07T15:09:51.722299892+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/c58fa05d0188a0700bc3f0576282876ae78f9e515809ac2461e53898cb494822/proxy.sock: use of closed network connection" name=kata-proxy pid=125113 sandbox=c58fa05d0188a0700bc3f0576282876ae78f9e515809ac2461e53898cb494822 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:         1.13.1
 API version:     1.26
 Package version: docker-1.13.1-63.mt20190301.gitedd1328.el7.centos.x86_64
 Go version:      go1.7.5
 Git commit:      edd1328/1.13.1
 Built:           Fri Mar  1 06:17:25 2019
 OS/Arch:         linux/amd64

Server:
 Version:         1.13.1
 API version:     1.26 (minimum version 1.12)
 Package version: docker-1.13.1-63.mt20190301.gitedd1328.el7.centos.x86_64
 Go version:      go1.7.5
 Git commit:      edd1328/1.13.1
 Built:           Fri Mar  1 06:17:25 2019
 OS/Arch:         linux/amd64
 Experimental:    false

Output of "docker info":

Containers: 6
 Running: 3
 Paused: 0
 Stopped: 3
Images: 195
Server Version: 1.13.1
Storage Driver: devicemapper
 Pool Name: dockervg-thinpool
 Pool Blocksize: 524.3 kB
 Base Device Size: 10.74 GB
 Backing Filesystem: ext4
 Data file:
 Metadata file:
 Data Space Used: 12.75 GB
 Data Space Total: 973.7 GB
 Data Space Available: 961 GB
 Metadata Space Used: 10.6 MB
 Metadata Space Total: 10.25 GB
 Metadata Space Available: 10.24 GB
 Thin Pool Minimum Free Space: 97.37 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: true
 Deferred Deletion Enabled: true
 Deferred Deleted Device Count: 0
 Library Version: 1.02.140-RHEL7 (2017-05-03)
Logging Driver: json-file
Cgroup Driver: systemd
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: runc kata-runtime
Default Runtime: runc
Init Binary: /usr/libexec/docker/docker-init-current
containerd version: edd132848e706633dfddc104fbd36e9d9df1b9ad (expected: aa8187dbd3b7ad67d8e5e3a15115d3eef43a7ed1)
runc version: e9ab997cfc4151ebcca8e54cf047311121fd4849 (expected: 9df8b306d01f59d3a8029be411de015b7304dd8f)
init version: 5b117de7f824f3d3825737cf09581645abbe35d4 (expected: 949e6facb77383876aeff8a6944dde66b3089574)
Security Options:
 seccomp
  WARNING: You're not using the default seccomp profile
  Profile: /etc/docker/seccomp.json
Kernel Version: 3.10.0-862.mt20181225.115.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
Number of Docker Hooks: 3
CPUs: 40
Total Memory: 377.3 GiB
Name: gh-hulk-k8s-ep14.gh.sankuai.com
ID: 4GNB:L2NJ:RTSE:2HCQ:IHIN:QXND:HANJ:77JA:BS7K:NFHY:OSKA:TRIF
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
 127.0.0.0/8
Registry Mirrors:
 http://127.0.0.1:65001
 registry-hulk.sankuai.com
Live Restore Enabled: true
Registries: docker.io (secure)

Output of "systemctl show docker":

Type=notify
Restart=on-abnormal
NotifyAccess=all
RestartUSec=100ms
TimeoutStartUSec=0
TimeoutStopUSec=1min 30s
WatchdogUSec=0
WatchdogTimestamp=Mon 2019-03-04 16:05:33 CST
WatchdogTimestampMonotonic=364382541172
StartLimitInterval=10000000
StartLimitBurst=5
StartLimitAction=none
FailureAction=none
PermissionsStartOnly=no
RootDirectoryStartOnly=no
RemainAfterExit=no
GuessMainPID=yes
MainPID=212352
ControlPID=0
FileDescriptorStoreMax=0
StatusErrno=0
Result=success
ExecMainStartTimestamp=Mon 2019-03-04 16:05:29 CST
ExecMainStartTimestampMonotonic=364378907326
ExecMainExitTimestampMonotonic=0
ExecMainPID=212352
ExecMainCode=0
ExecMainStatus=0
ExecStart={ path=/usr/bin/dockerd-current ; argv[]=/usr/bin/dockerd-current --exec-opt native.cgroupdriver=systemd --userland-proxy-path=/usr/libexec/docker/docker-proxy-current --init-path=/usr/libexec/docker/docker-init-current --seccomp-profile=/etc/docker/seccomp.json $OPTIONS $DOCKER_STORAGE_OPTIONS $DOCKER_NETWORK_OPTIONS $ADD_REGISTRY $BLOCK_REGISTRY $INSECURE_REGISTRY $REGISTRIES ; 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=519204864
TasksCurrent=205
Delegate=no
CPUAccounting=no
CPUShares=18446744073709551615
StartupCPUShares=18446744073709551615
CPUQuotaPerSecUSec=infinity
BlockIOAccounting=no
BlockIOWeight=18446744073709551615
StartupBlockIOWeight=18446744073709551615
MemoryAccounting=no
MemoryLimit=18446744073709551615
DevicePolicy=auto
TasksAccounting=no
TasksMax=18446744073709551615
Environment=GOTRACEBACK=crash DOCKER_HTTP_HOST_COMPAT=1 PATH=/usr/libexec/docker:/usr/bin:/usr/sbin
EnvironmentFile=/run/containers/registries.conf (ignore_errors=yes)
EnvironmentFile=/etc/sysconfig/docker (ignore_errors=yes)
EnvironmentFile=/etc/sysconfig/docker-storage (ignore_errors=yes)
EnvironmentFile=/etc/sysconfig/docker-network (ignore_errors=yes)
UMask=0022
LimitCPU=18446744073709551615
LimitFSIZE=18446744073709551615
LimitDATA=18446744073709551615
LimitSTACK=18446744073709551615
LimitCORE=18446744073709551615
LimitRSS=18446744073709551615
LimitNOFILE=1048576
LimitAS=18446744073709551615
LimitNPROC=1048576
LimitMEMLOCK=65536
LimitLOCKS=18446744073709551615
LimitSIGPENDING=1545530
LimitMSGQUEUE=819200
LimitNICE=0
LimitRTPRIO=0
LimitRTTIME=18446744073709551615
OOMScoreAdjust=0
Nice=0
IOScheduling=0
CPUSchedulingPolicy=0
CPUSchedulingPriority=0
TimerSlackNSec=50000
CPUSchedulingResetOnFork=no
NonBlocking=no
StandardInput=null
StandardOutput=journal
StandardError=inherit
TTYReset=no
TTYVHangup=no
TTYVTDisallocate=no
SyslogPriority=30
SyslogLevelPrefix=yes
SecureBits=0
CapabilityBoundingSet=18446744073709551615
AmbientCapabilities=0
MountFlags=0
PrivateTmp=no
PrivateNetwork=no
PrivateDevices=no
ProtectHome=no
ProtectSystem=no
SameProcessGroup=no
IgnoreSIGPIPE=yes
NoNewPrivileges=no
SystemCallErrorNumber=0
RuntimeDirectoryMode=0755
KillMode=process
KillSignal=15
SendSIGKILL=yes
SendSIGHUP=no
Id=docker.service
Names=docker.service
Requires=docker-cleanup.timer basic.target
Wants=docker-storage-setup.service system.slice
RequiredBy=docker-cleanup.service docker-novolume-plugin.service
Conflicts=shutdown.target
Before=shutdown.target
After=system.slice network.target registries.service docker-storage-setup.service systemd-journald.socket hulk-host-init.service rhel-push-plugin.socket docker-novolume-plugin.service basic.target
Documentation=http://docs.docker.com
Description=Docker Application Container Engine
LoadState=loaded
ActiveState=active
SubState=running
FragmentPath=/usr/lib/systemd/system/docker.service
UnitFileState=disabled
UnitFilePreset=disabled
InactiveExitTimestamp=Mon 2019-03-04 16:05:29 CST
InactiveExitTimestampMonotonic=364378907406
ActiveEnterTimestamp=Mon 2019-03-04 16:05:33 CST
ActiveEnterTimestampMonotonic=364382541220
ActiveExitTimestamp=Mon 2019-03-04 16:02:22 CST
ActiveExitTimestampMonotonic=364191742436
InactiveEnterTimestamp=Mon 2019-03-04 16:05:23 CST
InactiveEnterTimestampMonotonic=364372582929
CanStart=yes
CanStop=yes
CanReload=yes
CanIsolate=no
StopWhenUnneeded=no
RefuseManualStart=no
RefuseManualStop=no
AllowIsolate=no
DefaultDependencies=yes
OnFailureJobMode=replace
IgnoreOnIsolate=no
IgnoreOnSnapshot=no
NeedDaemonReload=no
JobTimeoutUSec=0
JobTimeoutAction=none
ConditionResult=yes
AssertResult=yes
ConditionTimestamp=Mon 2019-03-04 16:05:29 CST
ConditionTimestampMonotonic=364378906514
AssertTimestamp=Mon 2019-03-04 16:05:29 CST
AssertTimestampMonotonic=364378906515
Transient=no

No kubectl

Packages

kata-ksm-throttler-1.5.0.git+3dd4c9f-18.1.x86_64
kata-linux-container-debug-4.14.67.22-18.1.x86_64
qemu-vanilla-2.11.2+git.0982a56a55-19.1.x86_64
kata-linux-container-4.14.67.22-18.1.x86_64
qemu-lite-bin-2.11.0+git.87517afd72-19.1.x86_64
kata-containers-image-1.5.0-15.1.x86_64
qemu-vanilla-data-2.11.2+git.0982a56a55-19.1.x86_64
qemu-lite-2.11.0+git.87517afd72-19.1.x86_64
kata-proxy-bin-1.5.0+git.9e77a0b-16.1.x86_64
kata-runtime-1.5.0+git.5f7fcd7-24.1.x86_64
qemu-vanilla-bin-2.11.2+git.0982a56a55-19.1.x86_64
kata-proxy-1.5.0+git.9e77a0b-16.1.x86_64
kata-shim-bin-1.5.0+git.efbf3bb-14.1.x86_64
qemu-lite-data-2.11.0+git.87517afd72-19.1.x86_64
kata-shim-1.5.0+git.efbf3bb-14.1.x86_64

kata-containers / runtime

Kata-runtime cannot use the net=container parameter #1335