kata-containers / runtime

Kata Containers version 1.x runtime (for version 2.x see https://github.com/kata-containers/kata-containers).
https://katacontainers.io/
Apache License 2.0
2.1k stars 376 forks source link

podman --pod option does not work as intended #3125

Closed c3d closed 3 years ago

c3d commented 3 years ago

Get your issue reviewed faster

Show kata-collect-data.sh details

# Meta details Running `kata-collect-data.sh` version `1.12.0 (commit )` at `2021-01-22.09:43:30.795857251+0100`. --- Runtime is `/usr/bin/kata-runtime`. # `kata-env` Output of "`/usr/bin/kata-runtime kata-env`": ```toml [Meta] Version = "1.0.24" [Runtime] Debug = false Trace = false DisableGuestSeccomp = true DisableNewNetNs = false SandboxCgroupOnly = true Path = "/usr/bin/kata-runtime" [Runtime.Version] OCI = "1.0.1-dev" [Runtime.Version.Version] Semver = "1.12.0" Major = 1 Minor = 12 Patch = 0 Commit = "" [Runtime.Config] Path = "/usr/share/kata-containers/defaults/configuration.toml" [Hypervisor] MachineType = "q35" Version = "QEMU emulator version 5.2.0 (qemu-5.2.0-4.fc33)\nCopyright (c) 2003-2020 Fabrice Bellard and the QEMU Project developers" Path = "/usr/bin/qemu-kvm" BlockDeviceDriver = "virtio-scsi" EntropySource = "/dev/urandom" SharedFS = "virtio-fs" VirtioFSDaemon = "/usr/libexec/virtiofsd" Msize9p = 8192 MemorySlots = 10 PCIeRootPort = 0 HotplugVFIOOnRootBus = false Debug = false UseVSock = true [Image] Path = "" [Kernel] Path = "/usr/lib/modules/5.9.8-200.fc33.x86_64/vmlinuz" Parameters = "scsi_mod.scan=none systemd.unified_cgroup_hierarchy=0" [Initrd] Path = "/var/cache/kata-containers/osbuilder-images/5.9.8-200.fc33.x86_64/fedora-kata-5.9.8-200.fc33.x86_64.initrd" [Proxy] Type = "noProxy" Path = "" Debug = false [Proxy.Version] Semver = "" Major = 0 Minor = 0 Patch = 0 Commit = "" [Shim] Type = "kataShim" Path = "/usr/libexec/kata-containers/kata-shim" Debug = false [Shim.Version] Semver = "<>" Major = 0 Minor = 0 Patch = 0 Commit = "<>" [Agent] Type = "kata" Debug = false Trace = false TraceMode = "" TraceType = "" [Host] Kernel = "5.9.13-200.fc33.x86_64" Architecture = "amd64" VMContainerCapable = true SupportVSocks = true [Host.Distro] Name = "Fedora" Version = "33" [Host.CPU] Vendor = "GenuineIntel" Model = "Intel(R) Xeon(R) CPU E5-1650 v4 @ 3.60GHz" [Netmon] Path = "/usr/libexec/kata-containers/kata-netmon" Debug = false Enable = false [Netmon.Version] Semver = "1.12.0" Major = 1 Minor = 12 Patch = 0 Commit = "<>" ``` --- # Runtime config files ## Runtime default config files ``` /etc/kata-containers/configuration.toml /usr/share/kata-containers/defaults/configuration.toml ``` ## Runtime config file contents Config file `/etc/kata-containers/configuration.toml` not found Config file `/usr/share/defaults/kata-containers/configuration.toml` not found Output of "`cat "/usr/share/kata-containers/defaults/configuration.toml"`": ```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-kvm" kernel = "/var/cache/kata-containers/vmlinuz.container" initrd = "/var/cache/kata-containers/kata-containers-initrd.img" #image = "/var/cache/kata-containers/kata-containers.img" machine_type = "q35" # 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: ["/usr/bin/qemu-kvm"] valid_hypervisor_paths = ["/usr/bin/qemu-kvm"] # 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 = "systemd.unified_cgroup_hierarchy=0" # 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-fs" # Path to vhost-user-fs daemon. virtio_fs_daemon = "/usr/libexec/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: ["/usr/libexec/virtiofsd"] valid_virtio_fs_daemon_paths = ["/usr/libexec/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" [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] # 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 = "/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: # # - 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=true # 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 ``` --- # KSM throttler ## version Output of "`/usr/lib/systemd/system/kata-ksm-throttler.service --version`": ``` /usr/bin/kata-collect-data.sh: line 178: /usr/lib/systemd/system/kata-ksm-throttler.service: Permission denied ``` ## systemd service # Image details No image --- # Initrd details ```yaml --- osbuilder: url: "https://github.com/kata-containers/osbuilder" version: "fedora-osbuilder-version-unknown" rootfs-creation-time: "2020-11-27T15:00:14.199628121+0000Z" description: "osbuilder rootfs" file-format-version: "0.0.2" architecture: "x86_64" base-distro: name: "" version: "" packages: default: extra: agent: url: "https://github.com/kata-containers/agent" name: "kata-agent" version: "1.12.0-b637f6f8ac590e4b3a5099d29317f61ecbdb3c9b-dirty" agent-is-init-daemon: "no" ``` --- # Logfiles ## Runtime logs Recent runtime problems found in system journal: ``` time="2021-01-20T17:01:59.980196322+01:00" level=error msg="Could not read qemu pid file" arch=amd64 command=delete container=6e2aeb17b36c3b3170b68056cb2b5dc48ea1feb20c9d2bf6c0033fd832d0796b error="open /run/vc/vm/6e2aeb17b36c3b3170b68056cb2b5dc48ea1feb20c9d2bf6c0033fd832d0796b/pid: no such file or directory" name=kata-runtime pid=253388 sandbox=6e2aeb17b36c3b3170b68056cb2b5dc48ea1feb20c9d2bf6c0033fd832d0796b source=virtcontainers subsystem=qemu time="2021-01-20T17:02:00.681781341+01:00" level=warning msg="Failed to get container, force will not fail: Container ID (6e2aeb17b36c3b3170b68056cb2b5dc48ea1feb20c9d2bf6c0033fd832d0796b) does not exist" arch=amd64 command=delete container=6e2aeb17b36c3b3170b68056cb2b5dc48ea1feb20c9d2bf6c0033fd832d0796b name=kata-runtime pid=253404 source=runtime time="2021-01-20T17:05:30.187002149+01:00" level=info msg="sanner return error: read unix @->/run/vc/vm/1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc/qmp.sock: use of closed network connection" arch=amd64 command=create container=1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc name=kata-runtime pid=259464 source=virtcontainers subsystem=qmp time="2021-01-20T17:05:32.013393186+01:00" level=info msg="sanner return error: read unix @->/run/vc/vm/1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc/qmp.sock: use of closed network connection" arch=amd64 command=create container=1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc name=kata-runtime pid=259464 source=virtcontainers subsystem=qmp time="2021-01-20T17:05:32.213559841+01:00" level=error msg="open /run/vc/sbs/distracted_khorana: no such file or directory" arch=amd64 command=create container=1bd874b73a5bc4ec553b5d40f5cc8ed1b82975f9b30a8ccf401236d210e204c0 name=kata-runtime pid=259560 source=runtime time="2021-01-20T17:05:32.24138123+01:00" level=warning msg="Failed to get container, force will not fail: Container ID (1bd874b73a5bc4ec553b5d40f5cc8ed1b82975f9b30a8ccf401236d210e204c0) does not exist" arch=amd64 command=delete container=1bd874b73a5bc4ec553b5d40f5cc8ed1b82975f9b30a8ccf401236d210e204c0 name=kata-runtime pid=259575 source=runtime time="2021-01-20T17:05:33.126196341+01:00" level=warning msg="Failed to get container, force will not fail: Container ID (1bd874b73a5bc4ec553b5d40f5cc8ed1b82975f9b30a8ccf401236d210e204c0) does not exist" arch=amd64 command=delete container=1bd874b73a5bc4ec553b5d40f5cc8ed1b82975f9b30a8ccf401236d210e204c0 name=kata-runtime pid=259634 source=runtime time="2021-01-20T17:08:02.436336728+01:00" level=error msg="open /run/vc/sbs/distracted_khorana: no such file or directory" arch=amd64 command=create container=ffde7dd815cf32458fae24cece94e7ae9dbae949094fc3f5c866de520b731ea5 name=kata-runtime pid=263560 source=runtime time="2021-01-20T17:08:02.468936868+01:00" level=warning msg="Failed to get container, force will not fail: Container ID (ffde7dd815cf32458fae24cece94e7ae9dbae949094fc3f5c866de520b731ea5) does not exist" arch=amd64 command=delete container=ffde7dd815cf32458fae24cece94e7ae9dbae949094fc3f5c866de520b731ea5 name=kata-runtime pid=263575 source=runtime time="2021-01-20T17:08:03.110627778+01:00" level=warning msg="Failed to get container, force will not fail: Container ID (ffde7dd815cf32458fae24cece94e7ae9dbae949094fc3f5c866de520b731ea5) does not exist" arch=amd64 command=delete container=ffde7dd815cf32458fae24cece94e7ae9dbae949094fc3f5c866de520b731ea5 name=kata-runtime pid=263737 source=runtime time="2021-01-20T17:08:55.084788814+01:00" level=error msg="open /run/vc/sbs/distracted_khorana: no such file or directory" arch=amd64 command=create container=771f943325304518e545b48f823557fb779df38d16a42b08996b23e8ce4cb655 name=kata-runtime pid=265110 source=runtime time="2021-01-20T17:08:55.115556848+01:00" level=warning msg="Failed to get container, force will not fail: Container ID (771f943325304518e545b48f823557fb779df38d16a42b08996b23e8ce4cb655) does not exist" arch=amd64 command=delete container=771f943325304518e545b48f823557fb779df38d16a42b08996b23e8ce4cb655 name=kata-runtime pid=265125 source=runtime time="2021-01-20T17:08:55.858922855+01:00" level=warning msg="Failed to get container, force will not fail: Container ID (771f943325304518e545b48f823557fb779df38d16a42b08996b23e8ce4cb655) does not exist" arch=amd64 command=delete container=771f943325304518e545b48f823557fb779df38d16a42b08996b23e8ce4cb655 name=kata-runtime pid=265180 source=runtime time="2021-01-20T17:15:36.530367186+01:00" level=info msg="sanner return error: read unix @->/run/vc/vm/f9b8962610a266fe2fc24364d2ae6476d0c69847576e489c71851c446f06b994/qmp.sock: use of closed network connection" arch=amd64 command=create container=f9b8962610a266fe2fc24364d2ae6476d0c69847576e489c71851c446f06b994 name=kata-runtime pid=273707 source=virtcontainers subsystem=qmp time="2021-01-20T17:15:38.278402691+01:00" level=info msg="sanner return error: read unix @->/run/vc/vm/f9b8962610a266fe2fc24364d2ae6476d0c69847576e489c71851c446f06b994/qmp.sock: use of closed network connection" arch=amd64 command=create container=f9b8962610a266fe2fc24364d2ae6476d0c69847576e489c71851c446f06b994 name=kata-runtime pid=273707 source=virtcontainers subsystem=qmp time="2021-01-20T17:15:38.524138322+01:00" level=error msg="open /run/vc/sbs/fedora-kata: no such file or directory" arch=amd64 command=create container=ed1eb90e51ff9f192db726f29b98d75cb36d4b49c14f1cf09a14142fa444fab9 name=kata-runtime pid=273782 source=runtime time="2021-01-20T17:15:38.554457922+01:00" level=warning msg="Failed to get container, force will not fail: Container ID (ed1eb90e51ff9f192db726f29b98d75cb36d4b49c14f1cf09a14142fa444fab9) does not exist" arch=amd64 command=delete container=ed1eb90e51ff9f192db726f29b98d75cb36d4b49c14f1cf09a14142fa444fab9 name=kata-runtime pid=273798 source=runtime time="2021-01-20T17:26:13.932032119+01:00" level=warning msg="Could not remove container share dir" arch=amd64 command=kill container=f9b8962610a266fe2fc24364d2ae6476d0c69847576e489c71851c446f06b994 error="no such file or directory" name=kata-runtime pid=295560 sandbox=f9b8962610a266fe2fc24364d2ae6476d0c69847576e489c71851c446f06b994 share-dir=/run/kata-containers/shared/sandboxes/f9b8962610a266fe2fc24364d2ae6476d0c69847576e489c71851c446f06b994/f9b8962610a266fe2fc24364d2ae6476d0c69847576e489c71851c446f06b994 source=virtcontainers subsystem=container time="2021-01-20T17:26:13.939932204+01:00" level=error msg="Could not read qemu pid file" arch=amd64 command=kill container=f9b8962610a266fe2fc24364d2ae6476d0c69847576e489c71851c446f06b994 error="open /run/vc/vm/f9b8962610a266fe2fc24364d2ae6476d0c69847576e489c71851c446f06b994/pid: no such file or directory" name=kata-runtime pid=295560 sandbox=f9b8962610a266fe2fc24364d2ae6476d0c69847576e489c71851c446f06b994 source=virtcontainers subsystem=qemu time="2021-01-20T17:26:13.9402128+01:00" level=error msg="Could not read qemu pid file" arch=amd64 command=kill container=f9b8962610a266fe2fc24364d2ae6476d0c69847576e489c71851c446f06b994 error="open /run/vc/vm/f9b8962610a266fe2fc24364d2ae6476d0c69847576e489c71851c446f06b994/pid: no such file or directory" name=kata-runtime pid=295560 sandbox=f9b8962610a266fe2fc24364d2ae6476d0c69847576e489c71851c446f06b994 source=virtcontainers subsystem=qemu time="2021-01-20T17:26:13.940442475+01:00" level=info msg="sanner return error: read unix @->/run/vc/vm/f9b8962610a266fe2fc24364d2ae6476d0c69847576e489c71851c446f06b994/qmp.sock: use of closed network connection" arch=amd64 command=kill container=f9b8962610a266fe2fc24364d2ae6476d0c69847576e489c71851c446f06b994 name=kata-runtime pid=295560 sandbox=f9b8962610a266fe2fc24364d2ae6476d0c69847576e489c71851c446f06b994 source=virtcontainers subsystem=qmp time="2021-01-20T17:26:14.168134811+01:00" level=error msg="Could not read qemu pid file" arch=amd64 command=delete container=f9b8962610a266fe2fc24364d2ae6476d0c69847576e489c71851c446f06b994 error="open /run/vc/vm/f9b8962610a266fe2fc24364d2ae6476d0c69847576e489c71851c446f06b994/pid: no such file or directory" name=kata-runtime pid=295745 sandbox=f9b8962610a266fe2fc24364d2ae6476d0c69847576e489c71851c446f06b994 source=virtcontainers subsystem=qemu time="2021-01-20T17:26:28.498346637+01:00" level=warning msg="Failed to get container, force will not fail: Container ID (ed1eb90e51ff9f192db726f29b98d75cb36d4b49c14f1cf09a14142fa444fab9) does not exist" arch=amd64 command=delete container=ed1eb90e51ff9f192db726f29b98d75cb36d4b49c14f1cf09a14142fa444fab9 name=kata-runtime pid=296214 source=runtime time="2021-01-20T17:26:28.710665694+01:00" level=warning msg="Failed to get container, force will not fail: Container ID (f9b8962610a266fe2fc24364d2ae6476d0c69847576e489c71851c446f06b994) does not exist" arch=amd64 command=delete container=f9b8962610a266fe2fc24364d2ae6476d0c69847576e489c71851c446f06b994 name=kata-runtime pid=296227 source=runtime time="2021-01-20T17:35:52.602877582+01:00" level=warning msg="Could not remove container share dir" arch=amd64 command=delete container=1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc error="no such file or directory" name=kata-runtime pid=307727 sandbox=1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc share-dir=/run/kata-containers/shared/sandboxes/1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc/1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc source=virtcontainers subsystem=container time="2021-01-20T17:35:52.602971327+01:00" level=error msg="Could not read qemu pid file" arch=amd64 command=delete container=1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc error="open /run/vc/vm/1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc/pid: no such file or directory" name=kata-runtime pid=307727 source=virtcontainers subsystem=qemu time="2021-01-20T17:35:52.603309787+01:00" level=error msg="Could not read qemu pid file" arch=amd64 command=delete container=1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc error="open /run/vc/vm/1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc/pid: no such file or directory" name=kata-runtime pid=307727 source=virtcontainers subsystem=qemu time="2021-01-20T17:35:52.608592009+01:00" level=warning msg="Agent did not stop sandbox" arch=amd64 command=delete container=1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc error="Proxy is not running" name=kata-runtime pid=307727 sandbox=1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc sandboxid=1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc source=virtcontainers subsystem=sandbox time="2021-01-20T17:35:52.609175792+01:00" level=warning msg="Unable to connect to unix socket (/run/vc/vm/1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc/qmp.sock): dial unix /run/vc/vm/1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc/qmp.sock: connect: no such file or directory" arch=amd64 command=delete container=1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc name=kata-runtime pid=307727 sandbox=1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc source=virtcontainers subsystem=qmp time="2021-01-20T17:35:52.609227171+01:00" level=error msg="Failed to connect to QEMU instance" arch=amd64 command=delete container=1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc error="dial unix /run/vc/vm/1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc/qmp.sock: connect: no such file or directory" name=kata-runtime pid=307727 sandbox=1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc source=virtcontainers subsystem=qemu time="2021-01-20T17:35:52.609545416+01:00" level=error msg="Could not read qemu pid file" arch=amd64 command=delete container=1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc error="open /run/vc/vm/1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc/pid: no such file or directory" name=kata-runtime pid=307727 sandbox=1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc source=virtcontainers subsystem=qemu time="2021-01-20T17:35:52.609826878+01:00" level=error msg="Could not read qemu pid file" arch=amd64 command=delete container=1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc error="open /run/vc/vm/1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc/pid: no such file or directory" name=kata-runtime pid=307727 sandbox=1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc source=virtcontainers subsystem=qemu time="2021-01-20T17:35:52.612595094+01:00" level=error msg="Could not read qemu pid file" arch=amd64 command=delete container=1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc error="open /run/vc/vm/1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc/pid: no such file or directory" name=kata-runtime pid=307727 sandbox=1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc source=virtcontainers subsystem=qemu time="2021-01-21T11:47:50.482078169+01:00" level=info msg="sanner return error: read unix @->/run/vc/vm/0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9/qmp.sock: use of closed network connection" arch=amd64 command=create container=0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9 name=kata-runtime pid=2620921 source=virtcontainers subsystem=qmp time="2021-01-21T11:47:52.314200645+01:00" level=info msg="sanner return error: read unix @->/run/vc/vm/0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9/qmp.sock: use of closed network connection" arch=amd64 command=create container=0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9 name=kata-runtime pid=2620921 source=virtcontainers subsystem=qmp time="2021-01-21T11:47:52.528178886+01:00" level=error msg="open /run/vc/sbs/fedora: no such file or directory" arch=amd64 command=create container=16f7259dde1fba69ac6769d6a5809011c6d0bd2ca68792158ee8fd1d86e15732 name=kata-runtime pid=2620997 source=runtime time="2021-01-21T11:47:52.555435817+01:00" level=warning msg="Failed to get container, force will not fail: Container ID (16f7259dde1fba69ac6769d6a5809011c6d0bd2ca68792158ee8fd1d86e15732) does not exist" arch=amd64 command=delete container=16f7259dde1fba69ac6769d6a5809011c6d0bd2ca68792158ee8fd1d86e15732 name=kata-runtime pid=2621013 source=runtime time="2021-01-21T11:47:53.695334033+01:00" level=warning msg="Failed to get container, force will not fail: Container ID (16f7259dde1fba69ac6769d6a5809011c6d0bd2ca68792158ee8fd1d86e15732) does not exist" arch=amd64 command=delete container=16f7259dde1fba69ac6769d6a5809011c6d0bd2ca68792158ee8fd1d86e15732 name=kata-runtime pid=2621072 source=runtime time="2021-01-21T18:32:49.622557209+01:00" level=warning msg="Failed to get container, force will not fail: Container ID (1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc) does not exist" arch=amd64 command=delete container=1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc name=kata-runtime pid=3385221 source=runtime time="2021-01-21T18:38:58.429670821+01:00" level=warning msg="Could not umount" arch=amd64 command=delete container=0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9 error="invalid argument" host-path=/run/kata-containers/shared/sandboxes/0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9/mounts/0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9-24578653f1c9c8fb-hostname name=kata-runtime pid=3387121 sandbox=0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9 source=virtcontainers subsystem=container time="2021-01-21T18:38:58.429723809+01:00" level=warning msg="Could not remove container share dir" arch=amd64 command=delete container=0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9 error="no such file or directory" name=kata-runtime pid=3387121 sandbox=0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9 share-dir=/run/kata-containers/shared/sandboxes/0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9/0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9 source=virtcontainers subsystem=container time="2021-01-21T18:38:58.429756998+01:00" level=error msg="Could not read qemu pid file" arch=amd64 command=delete container=0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9 error="open /run/vc/vm/0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9/pid: no such file or directory" name=kata-runtime pid=3387121 source=virtcontainers subsystem=qemu time="2021-01-21T18:38:58.429928421+01:00" level=error msg="Could not read qemu pid file" arch=amd64 command=delete container=0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9 error="open /run/vc/vm/0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9/pid: no such file or directory" name=kata-runtime pid=3387121 source=virtcontainers subsystem=qemu time="2021-01-21T18:38:58.433526087+01:00" level=warning msg="Agent did not stop sandbox" arch=amd64 command=delete container=0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9 error="Proxy is not running" name=kata-runtime pid=3387121 sandbox=0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9 sandboxid=0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9 source=virtcontainers subsystem=sandbox time="2021-01-21T18:38:58.433612521+01:00" level=warning msg="Unable to connect to unix socket (/run/vc/vm/0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9/qmp.sock): dial unix /run/vc/vm/0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9/qmp.sock: connect: no such file or directory" arch=amd64 command=delete container=0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9 name=kata-runtime pid=3387121 sandbox=0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9 source=virtcontainers subsystem=qmp time="2021-01-21T18:38:58.433642875+01:00" level=error msg="Failed to connect to QEMU instance" arch=amd64 command=delete container=0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9 error="dial unix /run/vc/vm/0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9/qmp.sock: connect: no such file or directory" name=kata-runtime pid=3387121 sandbox=0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9 source=virtcontainers subsystem=qemu time="2021-01-21T18:38:58.433794444+01:00" level=error msg="Could not read qemu pid file" arch=amd64 command=delete container=0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9 error="open /run/vc/vm/0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9/pid: no such file or directory" name=kata-runtime pid=3387121 sandbox=0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9 source=virtcontainers subsystem=qemu time="2021-01-21T18:38:58.433997205+01:00" level=error msg="Could not read qemu pid file" arch=amd64 command=delete container=0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9 error="open /run/vc/vm/0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9/pid: no such file or directory" name=kata-runtime pid=3387121 sandbox=0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9 source=virtcontainers subsystem=qemu time="2021-01-21T18:38:58.435426616+01:00" level=error msg="Could not read qemu pid file" arch=amd64 command=delete container=0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9 error="open /run/vc/vm/0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9/pid: no such file or directory" name=kata-runtime pid=3387121 sandbox=0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9 source=virtcontainers subsystem=qemu time="2021-01-21T18:38:58.435736021+01:00" level=error msg="failed to unmount vm share path /run/kata-containers/shared/sandboxes/0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9/shared" arch=amd64 command=delete container=0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9 error="invalid argument" name=kata-runtime pid=3387121 sandbox=0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9 source=virtcontainers subsystem=kata_agent ``` ## Proxy logs Recent proxy problems found in system journal: ``` time="2020-11-04T18:28:04.349224418+01:00" level=info msg=announce agent-logs-socket=/run/vc/vm/ddb39c4b19f7bbc09cde0c5782c12ac5effaac9f7bd14e024920bbfbbdb7843f/console.sock channel-mux-socket=/run/vc/vm/ddb39c4b19f7bbc09cde0c5782c12ac5effaac9f7bd14e024920bbfbbdb7843f/kata.sock debug=true log-level=debug name=kata-proxy pid=4152206 proxy-listen-socket="unix:///run/vc/sbs/ddb39c4b19f7bbc09cde0c5782c12ac5effaac9f7bd14e024920bbfbbdb7843f/proxy.sock" sandbox=ddb39c4b19f7bbc09cde0c5782c12ac5effaac9f7bd14e024920bbfbbdb7843f source=proxy version=unknown time="2020-11-04T18:28:38.674223347+01:00" level=info msg=announce agent-logs-socket=/run/vc/vm/aed95767392adb611b45f67411f64cc6cc1adf40b5b9740890b664749e63401d/console.sock channel-mux-socket=/run/vc/vm/aed95767392adb611b45f67411f64cc6cc1adf40b5b9740890b664749e63401d/kata.sock debug=true log-level=debug name=kata-proxy pid=4152868 proxy-listen-socket="unix:///run/vc/sbs/aed95767392adb611b45f67411f64cc6cc1adf40b5b9740890b664749e63401d/proxy.sock" sandbox=aed95767392adb611b45f67411f64cc6cc1adf40b5b9740890b664749e63401d source=proxy version=unknown time="2020-11-04T18:28:59.090306459+01:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/aed95767392adb611b45f67411f64cc6cc1adf40b5b9740890b664749e63401d/kata.sock: use of closed network connection" name=kata-proxy pid=4152868 sandbox=aed95767392adb611b45f67411f64cc6cc1adf40b5b9740890b664749e63401d source=proxy time="2020-11-04T18:30:23.025322735+01:00" level=info msg=announce agent-logs-socket=/run/vc/vm/0d2109b3ed1b31c3f6b4fdd9d4ea5fa31b697a21d0f59b4181a35391fc0d2055/console.sock channel-mux-socket=/run/vc/vm/0d2109b3ed1b31c3f6b4fdd9d4ea5fa31b697a21d0f59b4181a35391fc0d2055/kata.sock debug=true log-level=debug name=kata-proxy pid=4154802 proxy-listen-socket="unix:///run/vc/sbs/0d2109b3ed1b31c3f6b4fdd9d4ea5fa31b697a21d0f59b4181a35391fc0d2055/proxy.sock" sandbox=0d2109b3ed1b31c3f6b4fdd9d4ea5fa31b697a21d0f59b4181a35391fc0d2055 source=proxy version=unknown time="2020-11-04T18:30:42.954195728+01:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/0d2109b3ed1b31c3f6b4fdd9d4ea5fa31b697a21d0f59b4181a35391fc0d2055/proxy.sock: use of closed network connection" name=kata-proxy pid=4154802 sandbox=0d2109b3ed1b31c3f6b4fdd9d4ea5fa31b697a21d0f59b4181a35391fc0d2055 source=proxy time="2020-11-04T18:44:12.3585432+01:00" level=info msg=announce agent-logs-socket=/run/vc/vm/0531d86ef895eaf7c96059d3e300dcf5bf70390f6c1f407c5917d5dec395a71e/console.sock channel-mux-socket=/run/vc/vm/0531d86ef895eaf7c96059d3e300dcf5bf70390f6c1f407c5917d5dec395a71e/kata.sock debug=true log-level=debug name=kata-proxy pid=4166536 proxy-listen-socket="unix:///run/vc/sbs/0531d86ef895eaf7c96059d3e300dcf5bf70390f6c1f407c5917d5dec395a71e/proxy.sock" sandbox=0531d86ef895eaf7c96059d3e300dcf5bf70390f6c1f407c5917d5dec395a71e source=proxy version=unknown time="2020-11-04T18:44:32.295465765+01:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/0531d86ef895eaf7c96059d3e300dcf5bf70390f6c1f407c5917d5dec395a71e/kata.sock: use of closed network connection" name=kata-proxy pid=4166536 sandbox=0531d86ef895eaf7c96059d3e300dcf5bf70390f6c1f407c5917d5dec395a71e source=proxy time="2020-11-04T18:49:08.685835388+01:00" level=info msg=announce agent-logs-socket=/run/vc/vm/b6817758aa64648da7696d5a93f1c75fa5ce515450dd74198a48d42748faf359/console.sock channel-mux-socket=/run/vc/vm/b6817758aa64648da7696d5a93f1c75fa5ce515450dd74198a48d42748faf359/kata.sock debug=true log-level=debug name=kata-proxy pid=4170396 proxy-listen-socket="unix:///run/vc/sbs/b6817758aa64648da7696d5a93f1c75fa5ce515450dd74198a48d42748faf359/proxy.sock" sandbox=b6817758aa64648da7696d5a93f1c75fa5ce515450dd74198a48d42748faf359 source=proxy version=unknown time="2020-11-04T18:49:28.608929837+01:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/b6817758aa64648da7696d5a93f1c75fa5ce515450dd74198a48d42748faf359/kata.sock: use of closed network connection" name=kata-proxy pid=4170396 sandbox=b6817758aa64648da7696d5a93f1c75fa5ce515450dd74198a48d42748faf359 source=proxy time="2020-11-09T17:59:52.419833239+01:00" level=info msg=announce agent-logs-socket=/run/vc/vm/8a4367233819b36649ae95d9309d07bea3000baeb070f942a037e5f615e2b699/console.sock channel-mux-socket=/run/vc/vm/8a4367233819b36649ae95d9309d07bea3000baeb070f942a037e5f615e2b699/kata.sock debug=true log-level=debug name=kata-proxy pid=47249 proxy-listen-socket="unix:///run/vc/sbs/8a4367233819b36649ae95d9309d07bea3000baeb070f942a037e5f615e2b699/proxy.sock" sandbox=8a4367233819b36649ae95d9309d07bea3000baeb070f942a037e5f615e2b699 source=proxy version=unknown time="2020-11-09T18:00:12.329425358+01:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/8a4367233819b36649ae95d9309d07bea3000baeb070f942a037e5f615e2b699/kata.sock: use of closed network connection" name=kata-proxy pid=47249 sandbox=8a4367233819b36649ae95d9309d07bea3000baeb070f942a037e5f615e2b699 source=proxy time="2020-11-09T18:01:38.903140666+01:00" level=info msg=announce agent-logs-socket=/run/vc/vm/da5df0bf6ed0c75577f2fdf3ca210708fba0e5ff242a4019f641ace09e66a887/console.sock channel-mux-socket=/run/vc/vm/da5df0bf6ed0c75577f2fdf3ca210708fba0e5ff242a4019f641ace09e66a887/kata.sock debug=true log-level=debug name=kata-proxy pid=47653 proxy-listen-socket="unix:///run/vc/sbs/da5df0bf6ed0c75577f2fdf3ca210708fba0e5ff242a4019f641ace09e66a887/proxy.sock" sandbox=da5df0bf6ed0c75577f2fdf3ca210708fba0e5ff242a4019f641ace09e66a887 source=proxy version=unknown time="2020-11-09T18:01:58.901782597+01:00" level=debug msg="Copy stream error" error="session shutdown" name=kata-proxy pid=47653 sandbox=da5df0bf6ed0c75577f2fdf3ca210708fba0e5ff242a4019f641ace09e66a887 source=proxy time="2020-11-09T18:01:58.901782932+01:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/da5df0bf6ed0c75577f2fdf3ca210708fba0e5ff242a4019f641ace09e66a887/kata.sock: use of closed network connection" name=kata-proxy pid=47653 sandbox=da5df0bf6ed0c75577f2fdf3ca210708fba0e5ff242a4019f641ace09e66a887 source=proxy time="2020-11-09T18:01:58.901915095+01:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/da5df0bf6ed0c75577f2fdf3ca210708fba0e5ff242a4019f641ace09e66a887/proxy.sock: use of closed network connection" name=kata-proxy pid=47653 sandbox=da5df0bf6ed0c75577f2fdf3ca210708fba0e5ff242a4019f641ace09e66a887 source=proxy time="2020-11-09T18:05:13.104026967+01:00" level=info msg=announce agent-logs-socket=/run/vc/vm/f3ac9884f530db6a7adda6574c76d72956182b526a81ffe6c78e12e3b0aee408/console.sock channel-mux-socket=/run/vc/vm/f3ac9884f530db6a7adda6574c76d72956182b526a81ffe6c78e12e3b0aee408/kata.sock debug=true log-level=debug name=kata-proxy pid=50397 proxy-listen-socket="unix:///run/vc/sbs/f3ac9884f530db6a7adda6574c76d72956182b526a81ffe6c78e12e3b0aee408/proxy.sock" sandbox=f3ac9884f530db6a7adda6574c76d72956182b526a81ffe6c78e12e3b0aee408 source=proxy version=unknown time="2020-11-09T18:05:33.102750156+01:00" level=debug msg="Copy stream error" error="session shutdown" name=kata-proxy pid=50397 sandbox=f3ac9884f530db6a7adda6574c76d72956182b526a81ffe6c78e12e3b0aee408 source=proxy time="2020-11-09T18:05:33.102854151+01:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/f3ac9884f530db6a7adda6574c76d72956182b526a81ffe6c78e12e3b0aee408/proxy.sock: use of closed network connection" name=kata-proxy pid=50397 sandbox=f3ac9884f530db6a7adda6574c76d72956182b526a81ffe6c78e12e3b0aee408 source=proxy ``` ## Shim logs Recent shim problems found in system journal: ``` time="2020-12-16T12:29:48.529614087+01:00" level=error msg="forward signal failed" container=8f15fd008cb2222eafd295c0ff36ddda0849b20369870926cdb99b65271d3ec4 error="rpc error: code = Unknown desc = container not running" exec-id=8f15fd008cb2222eafd295c0ff36ddda0849b20369870926cdb99b65271d3ec4 name=kata-shim pid=1 signal="urgent I/O condition" source=shim time="2021-01-20T11:46:39.713058849+01:00" level=error msg="forward signal failed" container=d6b698f94536935c5ba6a188b249945c89fa5139d38721b84a2a60a6782419d5 error="rpc error: code = Unavailable desc = transport is closing" exec-id=d6b698f94536935c5ba6a188b249945c89fa5139d38721b84a2a60a6782419d5 name=kata-shim pid=1 signal=terminated source=shim time="2021-01-20T17:29:33.521212956+01:00" level=error msg="forward signal failed" container=1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc error="rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = \"transport: Error while dialing rpc error: code = DeadlineExceeded desc = timed out connecting to vsock 2213151868:1024\"" exec-id=1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc name=kata-shim pid=1 signal="urgent I/O condition" source=shim time="2021-01-20T17:35:52.3191032+01:00" level=error msg="failed waiting for process" container=1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc error="rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = \"transport: Error while dialing rpc error: code = DeadlineExceeded desc = timed out connecting to vsock 2213151868:1024\"" exec-id=1925226ec2b40a2053ebc2fc2a2fdc9248aa600b84cfc35b11c9779fe3750acc name=kata-shim pid=1 source=shim time="2021-01-21T18:37:58.255989963+01:00" level=error msg="forward signal failed" container=0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9 error="rpc error: code = Unavailable desc = transport is closing" exec-id=0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9 name=kata-shim pid=1 signal=terminated source=shim time="2021-01-21T18:38:58.257957617+01:00" level=error msg="failed waiting for process" container=0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9 error="rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = \"transport: Error while dialing rpc error: code = DeadlineExceeded desc = timed out connecting to vsock 3642122429:1024\"" exec-id=0cbdd8b601f7496b1f9b4c9117240923edcf37d43b63d4d80ec105f02ba33ae9 name=kata-shim pid=1 source=shim ``` ## Throttler logs No recent throttler problems found in system journal. --- # Container manager details Have `docker` ## Docker Output of "`docker version`": ``` Client: Version: 19.03.13 API version: 1.40 Go version: go1.15.1 Git commit: 4484c46 Built: Fri Oct 2 19:31:30 2020 OS/Arch: linux/amd64 Experimental: false Server: Engine: Version: 19.03.13 API version: 1.40 (minimum version 1.12) Go version: go1.15.1 Git commit: 4484c46 Built: Fri Oct 2 00:00:00 2020 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.4.3 GitCommit: runc: Version: 1.0.0-rc92+dev GitCommit: c9a9ce0286785bef3f3c3c87cd1232e535a03e15 docker-init: Version: 0.18.0 GitCommit: ``` Output of "`docker info`": ``` Client: Debug Mode: false Server: Containers: 0 Running: 0 Paused: 0 Stopped: 0 Images: 61 Server Version: 19.03.13 Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Native Overlay Diff: true Logging Driver: journald Cgroup Driver: systemd Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog Swarm: inactive Runtimes: runc Default Runtime: runc Init Binary: /usr/libexec/docker/docker-init containerd version: runc version: c9a9ce0286785bef3f3c3c87cd1232e535a03e15 init version: Security Options: seccomp Profile: default selinux Kernel Version: 5.9.13-200.fc33.x86_64 Operating System: Fedora 33 (Thirty Three) OSType: linux Architecture: x86_64 CPUs: 12 Total Memory: 31.22GiB Name: turbo.dinechin.lan ID: WVP5:3KUH:P4O5:P44L:AS7B:O3YL:5RXE:UL7O:536C:YCT4:SV7Z:DJCJ Docker Root Dir: /var/lib/docker Debug Mode: false Registry: https://index.docker.io/v1/ Labels: Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: true WARNING: No swap limit support WARNING: No kernel memory limit support WARNING: No kernel memory TCP limit support WARNING: No oom kill disable support WARNING: No cpu cfs quota support WARNING: No cpu cfs period support WARNING: No cpu shares support ``` Output of "`systemctl show docker`": ``` Type=notify Restart=on-failure NotifyAccess=main RestartUSec=100ms TimeoutStartUSec=infinity TimeoutStopUSec=1min 30s TimeoutAbortUSec=1min 30s TimeoutStartFailureMode=terminate TimeoutStopFailureMode=terminate RuntimeMaxUSec=infinity WatchdogUSec=0 WatchdogTimestampMonotonic=0 RootDirectoryStartOnly=no RemainAfterExit=no GuessMainPID=yes MainPID=1393377 ControlPID=0 FileDescriptorStoreMax=0 NFileDescriptorStore=0 StatusErrno=0 Result=success ReloadResult=success CleanResult=success UID=[not set] GID=[not set] NRestarts=0 OOMPolicy=stop ExecMainStartTimestamp=Fri 2021-01-22 09:44:01 CET ExecMainStartTimestampMonotonic=53235160782 ExecMainExitTimestampMonotonic=0 ExecMainPID=1393377 ExecMainCode=0 ExecMainStatus=0 ExecStart={ path=/usr/bin/dockerd ; argv[]=/usr/bin/dockerd --host=fd:// --exec-opt native.cgroupdriver=systemd $OPTIONS ; ignore_errors=no ; start_time=[Fri 2021-01-22 09:44:01 CET] ; stop_time=[n/a] ; pid=1393377 ; code=(null) ; status=0/0 } ExecStartEx={ path=/usr/bin/dockerd ; argv[]=/usr/bin/dockerd --host=fd:// --exec-opt native.cgroupdriver=systemd $OPTIONS ; flags= ; start_time=[Fri 2021-01-22 09:44:01 CET] ; stop_time=[n/a] ; pid=1393377 ; 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 } ExecReloadEx={ path=/bin/kill ; argv[]=/bin/kill -s HUP $MAINPID ; flags= ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 } Slice=system.slice ControlGroup=/system.slice/docker.service MemoryCurrent=202252288 CPUUsageNSec=902111000 EffectiveCPUs= EffectiveMemoryNodes= TasksCurrent=34 IPIngressBytes=[no data] IPIngressPackets=[no data] IPEgressBytes=[no data] IPEgressPackets=[no data] IOReadBytes=18446744073709551615 IOReadOperations=18446744073709551615 IOWriteBytes=18446744073709551615 IOWriteOperations=18446744073709551615 Delegate=no CPUAccounting=yes CPUWeight=[not set] StartupCPUWeight=[not set] CPUShares=[not set] StartupCPUShares=[not set] CPUQuotaPerSecUSec=infinity CPUQuotaPeriodUSec=infinity AllowedCPUs= AllowedMemoryNodes= IOAccounting=no IOWeight=[not set] StartupIOWeight=[not set] BlockIOAccounting=no BlockIOWeight=[not set] StartupBlockIOWeight=[not set] MemoryAccounting=yes DefaultMemoryLow=0 DefaultMemoryMin=0 MemoryMin=0 MemoryLow=0 MemoryHigh=infinity MemoryMax=infinity MemorySwapMax=infinity MemoryLimit=infinity DevicePolicy=auto TasksAccounting=yes TasksMax=38313 IPAccounting=no EnvironmentFiles=/etc/sysconfig/docker (ignore_errors=yes) UMask=0022 LimitCPU=infinity LimitCPUSoft=infinity LimitFSIZE=infinity LimitFSIZESoft=infinity LimitDATA=infinity LimitDATASoft=infinity LimitSTACK=infinity LimitSTACKSoft=8388608 LimitCORE=infinity LimitCORESoft=infinity LimitRSS=infinity LimitRSSSoft=infinity LimitNOFILE=infinity LimitNOFILESoft=infinity LimitAS=infinity LimitASSoft=infinity LimitNPROC=infinity LimitNPROCSoft=infinity LimitMEMLOCK=65536 LimitMEMLOCKSoft=65536 LimitLOCKS=infinity LimitLOCKSSoft=infinity LimitSIGPENDING=127710 LimitSIGPENDINGSoft=127710 LimitMSGQUEUE=819200 LimitMSGQUEUESoft=819200 LimitNICE=0 LimitNICESoft=0 LimitRTPRIO=0 LimitRTPRIOSoft=0 LimitRTTIME=infinity LimitRTTIMESoft=infinity RootHashSignature= OOMScoreAdjust=0 CoredumpFilter=0x33 Nice=0 IOSchedulingClass=0 IOSchedulingPriority=0 CPUSchedulingPolicy=0 CPUSchedulingPriority=0 CPUAffinity= CPUAffinityFromNUMA=no NUMAPolicy=n/a NUMAMask= TimerSlackNSec=50000 CPUSchedulingResetOnFork=no NonBlocking=no StandardInput=null StandardInputData= StandardOutput=journal StandardError=inherit TTYReset=no TTYVHangup=no TTYVTDisallocate=no SyslogPriority=30 SyslogLevelPrefix=yes SyslogLevel=6 SyslogFacility=3 LogLevelMax=-1 LogRateLimitIntervalUSec=0 LogRateLimitBurst=0 SecureBits=0 CapabilityBoundingSet=cap_chown cap_dac_override cap_dac_read_search cap_fowner cap_fsetid cap_kill cap_setgid cap_setuid cap_setpcap cap_linux_immutable cap_net_bind_service cap_net_broadcast cap_net_admin cap_net_raw cap_ipc_lock cap_ipc_owner cap_sys_module cap_sys_rawio cap_sys_chroot cap_sys_ptrace cap_sys_pacct cap_sys_admin cap_sys_boot cap_sys_nice cap_sys_resource cap_sys_time cap_sys_tty_config cap_mknod cap_lease cap_audit_write cap_audit_control cap_setfcap cap_mac_override cap_mac_admin cap_syslog cap_wake_alarm cap_block_suspend cap_audit_read cap_perfmon cap_bpf cap_checkpoint_restore AmbientCapabilities= DynamicUser=no RemoveIPC=no MountFlags= PrivateTmp=no PrivateDevices=no ProtectClock=no ProtectKernelTunables=no ProtectKernelModules=no ProtectKernelLogs=no ProtectControlGroups=no PrivateNetwork=no PrivateUsers=no PrivateMounts=no ProtectHome=no ProtectSystem=no SameProcessGroup=no UtmpMode=init IgnoreSIGPIPE=yes NoNewPrivileges=no SystemCallErrorNumber=0 LockPersonality=no RuntimeDirectoryPreserve=no RuntimeDirectoryMode=0755 StateDirectoryMode=0755 CacheDirectoryMode=0755 LogsDirectoryMode=0755 ConfigurationDirectoryMode=0755 TimeoutCleanUSec=infinity MemoryDenyWriteExecute=no RestrictRealtime=no RestrictSUIDSGID=no RestrictNamespaces=no MountAPIVFS=no KeyringMode=private ProtectHostname=no KillMode=process KillSignal=15 RestartKillSignal=15 FinalKillSignal=9 SendSIGKILL=yes SendSIGHUP=no WatchdogSignal=6 Id=docker.service Names=docker.service Requires=sysinit.target docker.socket system.slice Wants=network-online.target ConsistsOf=docker.socket Conflicts=shutdown.target Before=shutdown.target After=network-online.target basic.target sysinit.target system.slice firewalld.service docker.socket systemd-journald.socket TriggeredBy=docker.socket Documentation=https://docs.docker.com Description=Docker Application Container Engine LoadState=loaded ActiveState=active FreezerState=running SubState=running FragmentPath=/usr/lib/systemd/system/docker.service UnitFileState=disabled UnitFilePreset=disabled StateChangeTimestamp=Fri 2021-01-22 09:44:08 CET StateChangeTimestampMonotonic=53242317208 InactiveExitTimestamp=Fri 2021-01-22 09:44:01 CET InactiveExitTimestampMonotonic=53235161271 ActiveEnterTimestamp=Fri 2021-01-22 09:44:08 CET ActiveEnterTimestampMonotonic=53242317208 ActiveExitTimestampMonotonic=0 InactiveEnterTimestampMonotonic=0 CanStart=yes CanStop=yes CanReload=yes CanIsolate=no CanFreeze=yes StopWhenUnneeded=no RefuseManualStart=no RefuseManualStop=no AllowIsolate=no DefaultDependencies=yes OnFailureJobMode=replace IgnoreOnIsolate=no NeedDaemonReload=no JobTimeoutUSec=infinity JobRunningTimeoutUSec=infinity JobTimeoutAction=none ConditionResult=yes AssertResult=yes ConditionTimestamp=Fri 2021-01-22 09:44:01 CET ConditionTimestampMonotonic=53235146012 AssertTimestamp=Fri 2021-01-22 09:44:01 CET AssertTimestampMonotonic=53235146017 Transient=no Perpetual=no StartLimitIntervalUSec=1min StartLimitBurst=3 StartLimitAction=none FailureAction=none SuccessAction=none InvocationID=be61e56aa2db442a84a4bd12ba0b1bc3 CollectMode=inactive ``` Have `kubectl` ## Kubernetes Output of "`kubectl version`": ``` error: no configuration has been provided ``` Output of "`kubectl config view`": ``` apiVersion: v1 clusters: [] contexts: [] current-context: "" kind: Config preferences: {} users: [] ``` Output of "`systemctl show kubelet`": ``` Restart=no NotifyAccess=none RestartUSec=100ms TimeoutStartUSec=1min 30s TimeoutStopUSec=1min 30s TimeoutAbortUSec=1min 30s TimeoutStartFailureMode=terminate TimeoutStopFailureMode=terminate RuntimeMaxUSec=infinity WatchdogUSec=infinity WatchdogTimestampMonotonic=0 RootDirectoryStartOnly=no RemainAfterExit=no GuessMainPID=yes MainPID=0 ControlPID=0 FileDescriptorStoreMax=0 NFileDescriptorStore=0 StatusErrno=0 Result=success ReloadResult=success CleanResult=success UID=[not set] GID=[not set] NRestarts=0 ExecMainStartTimestampMonotonic=0 ExecMainExitTimestampMonotonic=0 ExecMainPID=0 ExecMainCode=0 ExecMainStatus=0 MemoryCurrent=[not set] CPUUsageNSec=[not set] EffectiveCPUs= EffectiveMemoryNodes= TasksCurrent=[not set] IPIngressBytes=[no data] IPIngressPackets=[no data] IPEgressBytes=[no data] IPEgressPackets=[no data] IOReadBytes=18446744073709551615 IOReadOperations=18446744073709551615 IOWriteBytes=18446744073709551615 IOWriteOperations=18446744073709551615 Delegate=no CPUAccounting=yes CPUWeight=[not set] StartupCPUWeight=[not set] CPUShares=[not set] StartupCPUShares=[not set] CPUQuotaPerSecUSec=infinity CPUQuotaPeriodUSec=infinity AllowedCPUs= AllowedMemoryNodes= IOAccounting=no IOWeight=[not set] StartupIOWeight=[not set] BlockIOAccounting=no BlockIOWeight=[not set] StartupBlockIOWeight=[not set] MemoryAccounting=yes DefaultMemoryLow=0 DefaultMemoryMin=0 MemoryMin=0 MemoryLow=0 MemoryHigh=infinity MemoryMax=infinity MemorySwapMax=infinity MemoryLimit=infinity DevicePolicy=auto TasksAccounting=yes TasksMax=38313 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=1073741816 LimitNOFILESoft=1073741816 LimitAS=infinity LimitASSoft=infinity LimitNPROC=127710 LimitNPROCSoft=127710 LimitMEMLOCK=4190277632 LimitMEMLOCKSoft=4190277632 LimitLOCKS=infinity LimitLOCKSSoft=infinity LimitSIGPENDING=127710 LimitSIGPENDINGSoft=127710 LimitMSGQUEUE=819200 LimitMSGQUEUESoft=819200 LimitNICE=0 LimitNICESoft=0 LimitRTPRIO=0 LimitRTPRIOSoft=0 LimitRTTIME=infinity LimitRTTIMESoft=infinity RootHashSignature= OOMScoreAdjust=0 CoredumpFilter=0x33 Nice=0 IOSchedulingClass=0 IOSchedulingPriority=0 CPUSchedulingPolicy=0 CPUSchedulingPriority=0 CPUAffinity= CPUAffinityFromNUMA=no NUMAPolicy=n/a NUMAMask= TimerSlackNSec=50000 CPUSchedulingResetOnFork=no NonBlocking=no StandardInput=null StandardInputData= StandardOutput=inherit StandardError=inherit TTYReset=no TTYVHangup=no TTYVTDisallocate=no SyslogPriority=30 SyslogLevelPrefix=yes SyslogLevel=6 SyslogFacility=3 LogLevelMax=-1 LogRateLimitIntervalUSec=0 LogRateLimitBurst=0 SecureBits=0 CapabilityBoundingSet=cap_chown cap_dac_override cap_dac_read_search cap_fowner cap_fsetid cap_kill cap_setgid cap_setuid cap_setpcap cap_linux_immutable cap_net_bind_service cap_net_broadcast cap_net_admin cap_net_raw cap_ipc_lock cap_ipc_owner cap_sys_module cap_sys_rawio cap_sys_chroot cap_sys_ptrace cap_sys_pacct cap_sys_admin cap_sys_boot cap_sys_nice cap_sys_resource cap_sys_time cap_sys_tty_config cap_mknod cap_lease cap_audit_write cap_audit_control cap_setfcap cap_mac_override cap_mac_admin cap_syslog cap_wake_alarm cap_block_suspend cap_audit_read cap_perfmon cap_bpf cap_checkpoint_restore AmbientCapabilities= DynamicUser=no RemoveIPC=no MountFlags= PrivateTmp=no PrivateDevices=no ProtectClock=no ProtectKernelTunables=no ProtectKernelModules=no ProtectKernelLogs=no ProtectControlGroups=no PrivateNetwork=no PrivateUsers=no PrivateMounts=no ProtectHome=no ProtectSystem=no SameProcessGroup=no UtmpMode=init IgnoreSIGPIPE=yes NoNewPrivileges=no SystemCallErrorNumber=0 LockPersonality=no RuntimeDirectoryPreserve=no RuntimeDirectoryMode=0755 StateDirectoryMode=0755 CacheDirectoryMode=0755 LogsDirectoryMode=0755 ConfigurationDirectoryMode=0755 TimeoutCleanUSec=infinity MemoryDenyWriteExecute=no RestrictRealtime=no RestrictSUIDSGID=no RestrictNamespaces=no MountAPIVFS=no KeyringMode=private ProtectHostname=no KillMode=control-group KillSignal=15 RestartKillSignal=15 FinalKillSignal=9 SendSIGKILL=yes SendSIGHUP=no WatchdogSignal=6 Id=kubelet.service Names=kubelet.service Description=kubelet.service LoadState=not-found ActiveState=inactive FreezerState=running SubState=dead StateChangeTimestampMonotonic=0 InactiveExitTimestampMonotonic=0 ActiveEnterTimestampMonotonic=0 ActiveExitTimestampMonotonic=0 InactiveEnterTimestampMonotonic=0 CanStart=no CanStop=yes CanReload=no CanIsolate=no CanFreeze=yes StopWhenUnneeded=no RefuseManualStart=no RefuseManualStop=no AllowIsolate=no DefaultDependencies=yes OnFailureJobMode=replace IgnoreOnIsolate=no NeedDaemonReload=no JobTimeoutUSec=infinity JobRunningTimeoutUSec=infinity JobTimeoutAction=none ConditionResult=no AssertResult=no ConditionTimestampMonotonic=0 AssertTimestampMonotonic=0 LoadError=org.freedesktop.systemd1.NoSuchUnit "Unit kubelet.service not found." Transient=no Perpetual=no StartLimitIntervalUSec=10s StartLimitBurst=5 StartLimitAction=none FailureAction=none SuccessAction=none CollectMode=inactive ``` No `crio` Have `containerd` ## containerd Output of "`containerd --version`": ``` containerd github.com/containerd/containerd 1.4.3 ``` Output of "`systemctl show containerd`": ``` Type=simple Restart=no NotifyAccess=none RestartUSec=100ms TimeoutStartUSec=1min 30s TimeoutStopUSec=1min 30s TimeoutAbortUSec=1min 30s TimeoutStartFailureMode=terminate TimeoutStopFailureMode=terminate RuntimeMaxUSec=infinity WatchdogUSec=infinity WatchdogTimestampMonotonic=0 RootDirectoryStartOnly=no RemainAfterExit=no GuessMainPID=yes MainPID=0 ControlPID=0 FileDescriptorStoreMax=0 NFileDescriptorStore=0 StatusErrno=0 Result=success ReloadResult=success CleanResult=success UID=[not set] GID=[not set] NRestarts=0 OOMPolicy=continue ExecMainStartTimestampMonotonic=0 ExecMainExitTimestampMonotonic=0 ExecMainPID=0 ExecMainCode=0 ExecMainStatus=0 ExecStartPre={ path=/sbin/modprobe ; argv[]=/sbin/modprobe overlay ; ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 } ExecStartPreEx={ path=/sbin/modprobe ; argv[]=/sbin/modprobe overlay ; flags= ; 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 } ExecStartEx={ path=/usr/bin/containerd ; argv[]=/usr/bin/containerd ; flags= ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 } Slice=system.slice MemoryCurrent=[not set] CPUUsageNSec=[not set] EffectiveCPUs= EffectiveMemoryNodes= TasksCurrent=[not set] IPIngressBytes=[no data] IPIngressPackets=[no data] IPEgressBytes=[no data] IPEgressPackets=[no data] IOReadBytes=18446744073709551615 IOReadOperations=18446744073709551615 IOWriteBytes=18446744073709551615 IOWriteOperations=18446744073709551615 Delegate=yes DelegateControllers=cpu cpuacct cpuset io blkio memory devices pids bpf-firewall bpf-devices CPUAccounting=yes CPUWeight=[not set] StartupCPUWeight=[not set] CPUShares=[not set] StartupCPUShares=[not set] CPUQuotaPerSecUSec=infinity CPUQuotaPeriodUSec=infinity AllowedCPUs= AllowedMemoryNodes= IOAccounting=no IOWeight=[not set] StartupIOWeight=[not set] BlockIOAccounting=no BlockIOWeight=[not set] StartupBlockIOWeight=[not set] MemoryAccounting=yes DefaultMemoryLow=0 DefaultMemoryMin=0 MemoryMin=0 MemoryLow=0 MemoryHigh=infinity MemoryMax=infinity MemorySwapMax=infinity MemoryLimit=infinity DevicePolicy=auto TasksAccounting=yes TasksMax=38313 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=524288 LimitNOFILESoft=1024 LimitAS=infinity LimitASSoft=infinity LimitNPROC=127710 LimitNPROCSoft=127710 LimitMEMLOCK=65536 LimitMEMLOCKSoft=65536 LimitLOCKS=infinity LimitLOCKSSoft=infinity LimitSIGPENDING=127710 LimitSIGPENDINGSoft=127710 LimitMSGQUEUE=819200 LimitMSGQUEUESoft=819200 LimitNICE=0 LimitNICESoft=0 LimitRTPRIO=0 LimitRTPRIOSoft=0 LimitRTTIME=infinity LimitRTTIMESoft=infinity RootHashSignature= OOMScoreAdjust=0 CoredumpFilter=0x33 Nice=0 IOSchedulingClass=0 IOSchedulingPriority=0 CPUSchedulingPolicy=0 CPUSchedulingPriority=0 CPUAffinity= CPUAffinityFromNUMA=no NUMAPolicy=n/a NUMAMask= TimerSlackNSec=50000 CPUSchedulingResetOnFork=no NonBlocking=no StandardInput=null StandardInputData= StandardOutput=journal StandardError=inherit TTYReset=no TTYVHangup=no TTYVTDisallocate=no SyslogPriority=30 SyslogLevelPrefix=yes SyslogLevel=6 SyslogFacility=3 LogLevelMax=-1 LogRateLimitIntervalUSec=0 LogRateLimitBurst=0 SecureBits=0 CapabilityBoundingSet=cap_chown cap_dac_override cap_dac_read_search cap_fowner cap_fsetid cap_kill cap_setgid cap_setuid cap_setpcap cap_linux_immutable cap_net_bind_service cap_net_broadcast cap_net_admin cap_net_raw cap_ipc_lock cap_ipc_owner cap_sys_module cap_sys_rawio cap_sys_chroot cap_sys_ptrace cap_sys_pacct cap_sys_admin cap_sys_boot cap_sys_nice cap_sys_resource cap_sys_time cap_sys_tty_config cap_mknod cap_lease cap_audit_write cap_audit_control cap_setfcap cap_mac_override cap_mac_admin cap_syslog cap_wake_alarm cap_block_suspend cap_audit_read cap_perfmon cap_bpf cap_checkpoint_restore AmbientCapabilities= DynamicUser=no RemoveIPC=no MountFlags= PrivateTmp=no PrivateDevices=no ProtectClock=no ProtectKernelTunables=no ProtectKernelModules=no ProtectKernelLogs=no ProtectControlGroups=no PrivateNetwork=no PrivateUsers=no PrivateMounts=no ProtectHome=no ProtectSystem=no SameProcessGroup=no UtmpMode=init IgnoreSIGPIPE=yes NoNewPrivileges=no SystemCallErrorNumber=0 LockPersonality=no RuntimeDirectoryPreserve=no RuntimeDirectoryMode=0755 StateDirectoryMode=0755 CacheDirectoryMode=0755 LogsDirectoryMode=0755 ConfigurationDirectoryMode=0755 TimeoutCleanUSec=infinity MemoryDenyWriteExecute=no RestrictRealtime=no RestrictSUIDSGID=no RestrictNamespaces=no MountAPIVFS=no KeyringMode=private ProtectHostname=no KillMode=process KillSignal=15 RestartKillSignal=15 FinalKillSignal=9 SendSIGKILL=yes SendSIGHUP=no WatchdogSignal=6 Id=containerd.service Names=containerd.service Requires=system.slice sysinit.target Conflicts=shutdown.target Before=shutdown.target After=system.slice sysinit.target basic.target systemd-journald.socket network.target Documentation=https://containerd.io Description=containerd container runtime LoadState=loaded ActiveState=inactive FreezerState=running SubState=dead FragmentPath=/usr/lib/systemd/system/containerd.service UnitFileState=disabled UnitFilePreset=disabled StateChangeTimestampMonotonic=0 InactiveExitTimestampMonotonic=0 ActiveEnterTimestampMonotonic=0 ActiveExitTimestampMonotonic=0 InactiveEnterTimestampMonotonic=0 CanStart=yes CanStop=yes CanReload=no CanIsolate=no CanFreeze=yes StopWhenUnneeded=no RefuseManualStart=no RefuseManualStop=no AllowIsolate=no DefaultDependencies=yes OnFailureJobMode=replace IgnoreOnIsolate=no NeedDaemonReload=no JobTimeoutUSec=infinity JobRunningTimeoutUSec=infinity JobTimeoutAction=none ConditionResult=no AssertResult=no ConditionTimestampMonotonic=0 AssertTimestampMonotonic=0 Transient=no Perpetual=no StartLimitIntervalUSec=10s StartLimitBurst=5 StartLimitAction=none FailureAction=none SuccessAction=none CollectMode=inactive ``` Output of "`cat /etc/containerd/config.toml`": ``` #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 No `dpkg` Have `rpm` Output of "`rpm -qa|egrep "(cc-oci-runtimecc-runtimerunv|kata-proxy|kata-runtime|kata-shim|kata-ksm-throttler|kata-containers-image|linux-container|qemu-)"`": ``` kata-shim-debugsource-1.8.2-1.fc30.x86_64 kata-ksm-throttler-debugsource-1.8.2-1.fc30.x86_64 kata-shim-debuginfo-1.8.2-1.fc30.x86_64 kata-proxy-debuginfo-1.8.2-1.fc30.x86_64 qemu-sanity-check-nodeps-1.1.6-1.fc33.x86_64 kata-runtime-debugsource-1.8.2-1.fc30.x86_64 kata-ksm-throttler-debuginfo-1.8.2-1.fc30.x86_64 ipxe-roms-qemu-20200823-1.git4bd064de.fc33.noarch kata-runtime-debuginfo-1.8.2-1.fc30.x86_64 kata-proxy-debugsource-1.8.2-1.fc30.x86_64 kata-proxy-1.12.0-1.fc33.x86_64 kata-runtime-1.12.0-2.fc33.x86_64 qemu-img-5.2.0-4.fc33.x86_64 qemu-common-5.2.0-4.fc33.x86_64 qemu-ui-opengl-5.2.0-4.fc33.x86_64 qemu-ui-spice-core-5.2.0-4.fc33.x86_64 qemu-char-spice-5.2.0-4.fc33.x86_64 qemu-ui-spice-app-5.2.0-4.fc33.x86_64 qemu-audio-spice-5.2.0-4.fc33.x86_64 qemu-device-display-qxl-5.2.0-4.fc33.x86_64 qemu-ui-egl-headless-5.2.0-4.fc33.x86_64 qemu-ui-sdl-5.2.0-4.fc33.x86_64 qemu-audio-alsa-5.2.0-4.fc33.x86_64 qemu-audio-oss-5.2.0-4.fc33.x86_64 qemu-audio-pa-5.2.0-4.fc33.x86_64 qemu-audio-sdl-5.2.0-4.fc33.x86_64 qemu-block-curl-5.2.0-4.fc33.x86_64 qemu-block-dmg-5.2.0-4.fc33.x86_64 qemu-block-gluster-5.2.0-4.fc33.x86_64 qemu-block-iscsi-5.2.0-4.fc33.x86_64 qemu-block-nfs-5.2.0-4.fc33.x86_64 qemu-block-rbd-5.2.0-4.fc33.x86_64 qemu-block-ssh-5.2.0-4.fc33.x86_64 qemu-char-baum-5.2.0-4.fc33.x86_64 qemu-device-display-virtio-gpu-5.2.0-4.fc33.x86_64 qemu-device-display-virtio-gpu-pci-5.2.0-4.fc33.x86_64 qemu-device-display-virtio-vga-5.2.0-4.fc33.x86_64 qemu-device-usb-redirect-5.2.0-4.fc33.x86_64 qemu-device-usb-smartcard-5.2.0-4.fc33.x86_64 qemu-ui-curses-5.2.0-4.fc33.x86_64 qemu-system-alpha-core-5.2.0-4.fc33.x86_64 qemu-system-arm-core-5.2.0-4.fc33.x86_64 qemu-system-avr-core-5.2.0-4.fc33.x86_64 qemu-system-cris-core-5.2.0-4.fc33.x86_64 qemu-system-hppa-core-5.2.0-4.fc33.x86_64 qemu-system-m68k-core-5.2.0-4.fc33.x86_64 qemu-system-microblaze-core-5.2.0-4.fc33.x86_64 qemu-system-mips-core-5.2.0-4.fc33.x86_64 qemu-system-nios2-core-5.2.0-4.fc33.x86_64 qemu-system-or1k-core-5.2.0-4.fc33.x86_64 qemu-system-ppc-core-5.2.0-4.fc33.x86_64 qemu-system-riscv-core-5.2.0-4.fc33.x86_64 qemu-system-rx-core-5.2.0-4.fc33.x86_64 qemu-system-s390x-core-5.2.0-4.fc33.x86_64 qemu-system-sh4-core-5.2.0-4.fc33.x86_64 qemu-system-sparc-core-5.2.0-4.fc33.x86_64 qemu-system-tricore-core-5.2.0-4.fc33.x86_64 qemu-system-xtensa-core-5.2.0-4.fc33.x86_64 qemu-user-5.2.0-4.fc33.x86_64 qemu-user-static-5.2.0-4.fc33.x86_64 qemu-ui-gtk-5.2.0-4.fc33.x86_64 qemu-system-alpha-5.2.0-4.fc33.x86_64 qemu-system-arm-5.2.0-4.fc33.x86_64 qemu-system-avr-5.2.0-4.fc33.x86_64 qemu-system-cris-5.2.0-4.fc33.x86_64 qemu-system-m68k-5.2.0-4.fc33.x86_64 qemu-system-microblaze-5.2.0-4.fc33.x86_64 qemu-system-mips-5.2.0-4.fc33.x86_64 qemu-system-nios2-5.2.0-4.fc33.x86_64 qemu-system-or1k-5.2.0-4.fc33.x86_64 qemu-system-ppc-5.2.0-4.fc33.x86_64 qemu-system-riscv-5.2.0-4.fc33.x86_64 qemu-system-rx-5.2.0-4.fc33.x86_64 qemu-system-s390x-5.2.0-4.fc33.x86_64 qemu-system-sh4-5.2.0-4.fc33.x86_64 qemu-system-sparc-5.2.0-4.fc33.x86_64 qemu-system-tricore-5.2.0-4.fc33.x86_64 qemu-system-xtensa-5.2.0-4.fc33.x86_64 qemu-system-x86-core-5.2.0-4.fc33.x86_64 qemu-system-x86-5.2.0-4.fc33.x86_64 qemu-kvm-5.2.0-4.fc33.x86_64 qemu-system-aarch64-core-5.2.0-4.fc33.x86_64 qemu-system-aarch64-5.2.0-4.fc33.x86_64 qemu-5.2.0-4.fc33.x86_64 qemu-kvm-core-5.2.0-4.fc33.x86_64 qemu-system-hppa-5.2.0-4.fc33.x86_64 qemu-guest-agent-5.2.0-4.fc33.x86_64 kata-shim-1.12.0-1.fc33.x86_64 kata-ksm-throttler-1.12.0-1.fc33.x86_64 libvirt-daemon-driver-qemu-7.0.0-1.fc33.x86_64 ``` ---

Description of problem

The --pod option of podman does not work as intended:

Expected result

Actual result

Creating a pod with --pod new:name creates only the infra pause container, but not the actual workload:

# podman run -it --rm --runtime kata --pod new:fedora fedora bash
Error: open /run/vc/sbs/fedora: no such file or directory: OCI not found
#  podman ps --pod
CONTAINER ID  IMAGE                 COMMAND  CREATED             STATUS                 PORTS   NAMES               POD ID        PODNAME
b2f156e50030  k8s.gcr.io/pause:3.2           About a minute ago  Up About a minute ago          9e978e508813-infra  9e978e508813  fedora

The same problem occurs with configurations given as an example online:

# podman run -dt --pod new:nginx --runtime kata -p 32597:80 quay.io/libpod/alpine_nginx:latest                                    9:55:04turbo.dinechin.lan↵130
Trying to pull quay.io/libpod/alpine_nginx:latest...
Getting image source signatures
Copying blob a3ed95caeb02 done  
Copying blob a3ed95caeb02 done  
Copying blob a3ed95caeb02 skipped: already exists  
Copying blob a3ed95caeb02 done  
Copying blob ee08fa06e364 done  
Copying blob 7ecd51378d2e done  
Copying blob 4fe2ade4980c done  
Writing manifest to image destination
Storing signatures
Error: open /run/vc/sbs/nginx: no such file or directory: OCI not found

Adding a container manually does not work either:

# podman run -it --rm --runtime kata --pod kata-pod fedora bash
Error: open /run/vc/sbs/kata-pod: no such file or directory: OCI not found

On the other hand, adding a pod without specifying the kata runtime falsely appears to work, but runs it outside of the kata VM:

# podman run -it --rm  --pod kata-pod fedora bash
[root@turbo /]# 
# podman ps --pod
CONTAINER ID  IMAGE                                     COMMAND  CREATED         STATUS            PORTS   NAMES               POD ID        PODNAME
bd047e51e1a7  registry.fedoraproject.org/fedora:latest  bash     3 minutes ago   Up 3 minutes ago          wonderful_hodgkin   c49bb14f8de1  kata-pod
f1f2d7171e59  k8s.gcr.io/pause:3.2                               10 minutes ago  Up 5 minutes ago          c49bb14f8de1-infra  c49bb14f8de1  kata-pod

In that case, the output of top shows that the wonderful_hodgkin container is running outside of the Kata pod:

1414867 root      20   0   79.5m   2.0m   1.7m S   0.0   0.0   0:00.00  `- conmon                                                                             
1414887 root      20   0   77.9m   1.5m   1.3m S   0.0   0.0   0:00.00      `- virtiofsd                                                                      
1414902 root      20   0 2413.9m   3.2m   2.9m S   0.0   0.0   0:00.00          `- virtiofsd                                                                  
1414897 root      20   0 2365.6m 298.2m 272.0m S   0.0   0.9   0:01.90      `- qemu-system-x86                                                                
1414940 root      20   0 1350.7m  14.3m   8.6m S   0.0   0.0   0:00.00      `- kata-shim                                                                      
1417141 root      20   0   79.5m   2.1m   1.8m S   0.0   0.0   0:00.00  `- conmon                                                                             
1417149 root      20   0   11.2m   3.9m   3.4m S   0.0   0.0   0:00.01      `- bash                 

Further information

I vaguely remember having tried that a long time ago, and thought it worked. It may be because I was confused by the fact that you can add containers to the pod, and it seems to work, except they are not running in the VM.

fidencio commented 3 years ago

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:

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.