search

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 374 forks source link

Container fails to start after reboot #1711

Closed pceiley closed 3 years ago

pceiley commented 5 years ago

Description of problem

  1. Create a container called plex using docker run
  2. Stop and start container (works as expected)
  3. Reboot system
  4. Attempt to start container (error)

Expected result

Container will start without error

Actual result

$ sudo docker start plex
Error response from daemon: OCI runtime create failed: rpc error: code = Internal desc = Could not run process: container_linux.go:348: starting container process caused "exec: \"/init\": stat /init: no such file or directory": unknown
Error: failed to start containers: plex
kata-collect-data.sh ``` $ sudo kata-collect-data.sh # Meta details Running `kata-collect-data.sh` version `1.6.2 (commit )` at `2019-05-19.10:08:41.483362831+1000`. --- Runtime is `/usr/bin/kata-runtime`. # `kata-env` Output of "`/usr/bin/kata-runtime kata-env`": ```toml [Meta] Version = "1.0.20" [Runtime] Debug = false Trace = false DisableGuestSeccomp = true DisableNewNetNs = false Path = "/usr/bin/kata-runtime" [Runtime.Version] Semver = "1.6.2" Commit = "" OCI = "1.0.1-dev" [Runtime.Config] Path = "/usr/share/defaults/kata-containers/configuration-qemu.toml" [Hypervisor] MachineType = "pc" Version = "QEMU emulator version 2.11.0\nCopyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers" Path = "/usr/bin/kata-qemu-lite-system-x86_64" BlockDeviceDriver = "virtio-scsi" EntropySource = "/dev/urandom" Msize9p = 8192 MemorySlots = 10 Debug = false UseVSock = false [Image] Path = "/usr/share/kata-containers/kata-containers-image_clearlinux_1.6.2_agent_4a3627d0c16.img" [Kernel] Path = "/usr/share/kata-containers/vmlinuz-4.19.44-38.container" Parameters = "init=/usr/lib/systemd/systemd systemd.unit=kata-containers.target systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket systemd.mask=systemd-journald.service systemd.mask=systemd-journald.socket systemd.mask=systemd-journal-flush.service systemd.mask=systemd-udevd.service systemd.mask=systemd-udevd.socket systemd.mask=systemd-udev-trigger.service systemd.mask=systemd-timesyncd.service systemd.mask=systemd-update-utmp.service systemd.mask=systemd-tmpfiles-setup.service systemd.mask=systemd-tmpfiles-cleanup.service systemd.mask=systemd-tmpfiles-cleanup.timer systemd.mask=tmp.mount" [Initrd] Path = "" [Proxy] Type = "kataProxy" Version = "kata-proxy version 1.6.2" Path = "/usr/libexec/kata-containers/kata-proxy" Debug = false [Shim] Type = "kataShim" Version = "kata-shim version 1.6.2" Path = "/usr/libexec/kata-containers/kata-shim" Debug = false [Agent] Type = "kata" [Host] Kernel = "4.19.44-36.lts2018" Architecture = "amd64" VMContainerCapable = true SupportVSocks = false [Host.Distro] Name = "Clear Linux OS" Version = "29480" [Host.CPU] Vendor = "GenuineIntel" Model = "Intel(R) Core(TM) i3-8109U CPU @ 3.00GHz" [Netmon] Version = "kata-netmon version 1.6.2" Path = "/usr/libexec/kata-containers/kata-netmon" Debug = false Enable = false ``` --- # Runtime config files ## Runtime default config files ``` /etc/kata-containers/configuration.toml /usr/share/defaults/kata-containers/configuration.toml ``` ## Runtime config file contents Config file `/etc/kata-containers/configuration.toml` not found Output of "`cat "/usr/share/defaults/kata-containers/configuration.toml"`": ```toml # Copyright (c) 2017-2019 Intel Corporation # # SPDX-License-Identifier: Apache-2.0 # # XXX: WARNING: this file is auto-generated. # XXX: # XXX: Source file: "cli/config/configuration-qemu.toml.in" # XXX: Project: # XXX: Name: Kata Containers # XXX: Type: kata [hypervisor.qemu] path = "/usr/bin/kata-qemu-lite-system-x86_64" kernel = "/usr/share/kata-containers/vmlinuz.container" image = "/usr/share/kata-containers/kata-containers.img" machine_type = "pc" # Optional space-separated list of options to pass to the guest kernel. # For example, use `kernel_params = "vsyscall=emulate"` if you are having # trouble running pre-2.15 glibc. # # WARNING: - any parameter specified here will take priority over the default # parameter value of the same name used to start the virtual machine. # Do not set values here unless you understand the impact of doing so as you # may stop the virtual machine from booting. # To see the list of default parameters, enable hypervisor debug, create a # container and look for 'default-kernel-parameters' log entries. kernel_params = "" # 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 # 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] # 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="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=bridged` and `internetworking_model=macvtap`. It works only # with `internetworking_model=none`. The tap device will be in the host network namespace and can connect to a bridge # (like OVS) directly. # If you are using docker, `disable_new_netns` only works with `docker run --net=none` # (default: false) #disable_new_netns = true ``` --- # KSM throttler ## version Output of "` --version`": ``` /usr/bin/kata-collect-data.sh: line 175: --version: command not found ``` ## systemd service # Image details ```yaml --- osbuilder: url: "https://github.com/kata-containers/osbuilder" version: "unknown" rootfs-creation-time: "2019-04-18T20:15:35.480962665+0000Z" description: "osbuilder rootfs" file-format-version: "0.0.2" architecture: "x86_64" base-distro: name: "Clear" version: "28920" packages: default: - "chrony" - "iptables-bin" - "libudev0-shim" - "systemd" extra: agent: url: "https://github.com/kata-containers/agent" name: "kata-agent" version: "1.6.2-4a3627d0c169f8277ce95a11ca6bb89aee90e05d" agent-is-init-daemon: "no" ``` --- # Initrd details No initrd --- # Logfiles ## Runtime logs Recent runtime problems found in system journal: ``` time="2019-05-19T09:12:36.716338164+10:00" level=warning msg="Could not umount" arch=amd64 command=kill container=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 error="invalid argument" host-path=/run/kata-containers/shared/sandboxes/35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213/35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213-b7c6b97dcf25ab9a-data name=kata-runtime pid=22245 sandbox=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 source=virtcontainers subsystem=container time="2019-05-19T09:12:36.71650639+10:00" level=error msg="invalid argument" arch=amd64 command=kill container=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 name=kata-runtime pid=22245 sandbox=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 source=runtime time="2019-05-19T09:12:37.128293657+10:00" level=error msg="failed to cleanup vm share path /run/kata-containers/shared/sandboxes/35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213" arch=amd64 command=delete container=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 error="unlinkat /run/kata-containers/shared/sandboxes/35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213/35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213/rootfs: device or resource busy" name=kata-runtime pid=22304 sandbox=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 source=virtcontainers subsystem=kata_agent time="2019-05-19T09:24:27.903228349+10:00" level=warning msg="load sandbox devices failed" arch=amd64 command=create container=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 error="open /run/vc/sbs/35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213/devices.json: no such file or directory" name=kata-runtime pid=856 sandbox=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 sandboxid=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 source=virtcontainers subsystem=sandbox time="2019-05-19T09:24:28.839691694+10:00" level=error msg="rpc error: code = Internal desc = Could not run process: container_linux.go:348: starting container process caused \"exec: \\\"/init\\\": stat /init: no such file or directory\"" arch=amd64 command=create container=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 name=kata-runtime pid=856 source=runtime time="2019-05-19T09:25:05.928227184+10:00" level=warning msg="load sandbox devices failed" arch=amd64 command=create container=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 error="open /run/vc/sbs/35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213/devices.json: no such file or directory" name=kata-runtime pid=1124 sandbox=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 sandboxid=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 source=virtcontainers subsystem=sandbox time="2019-05-19T09:25:06.575049846+10:00" level=error msg="rpc error: code = Internal desc = Could not run process: container_linux.go:348: starting container process caused \"exec: \\\"/init\\\": stat /init: no such file or directory\"" arch=amd64 command=create container=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 name=kata-runtime pid=1124 source=runtime time="2019-05-19T09:25:39.037244473+10:00" level=warning msg="load sandbox devices failed" arch=amd64 command=create container=516f62c4ea254cba7b8e1998a0aa2ade316f3a5aa637ce7e947a926cae51d201 error="open /run/vc/sbs/516f62c4ea254cba7b8e1998a0aa2ade316f3a5aa637ce7e947a926cae51d201/devices.json: no such file or directory" name=kata-runtime pid=1262 sandbox=516f62c4ea254cba7b8e1998a0aa2ade316f3a5aa637ce7e947a926cae51d201 sandboxid=516f62c4ea254cba7b8e1998a0aa2ade316f3a5aa637ce7e947a926cae51d201 source=virtcontainers subsystem=sandbox time="2019-05-19T09:25:57.648265637+10:00" level=warning msg="load sandbox devices failed" arch=amd64 command=create container=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 error="open /run/vc/sbs/35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213/devices.json: no such file or directory" name=kata-runtime pid=1531 sandbox=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 sandboxid=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 source=virtcontainers subsystem=sandbox time="2019-05-19T09:25:58.29649887+10:00" level=error msg="rpc error: code = Internal desc = Could not run process: container_linux.go:348: starting container process caused \"exec: \\\"/init\\\": stat /init: no such file or directory\"" arch=amd64 command=create container=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 name=kata-runtime pid=1531 source=runtime time="2019-05-19T09:27:21.134281189+10:00" level=warning msg="load sandbox devices failed" arch=amd64 command=create container=8d4512b5a9865f4815d47b49481519215d0122374b21aa0274f7a39faed91354 error="open /run/vc/sbs/8d4512b5a9865f4815d47b49481519215d0122374b21aa0274f7a39faed91354/devices.json: no such file or directory" name=kata-runtime pid=1694 sandbox=8d4512b5a9865f4815d47b49481519215d0122374b21aa0274f7a39faed91354 sandboxid=8d4512b5a9865f4815d47b49481519215d0122374b21aa0274f7a39faed91354 source=virtcontainers subsystem=sandbox time="2019-05-19T09:27:33.021224597+10:00" level=warning msg="load sandbox devices failed" arch=amd64 command=create container=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 error="open /run/vc/sbs/35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213/devices.json: no such file or directory" name=kata-runtime pid=1924 sandbox=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 sandboxid=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 source=virtcontainers subsystem=sandbox time="2019-05-19T09:27:33.676671519+10:00" level=error msg="rpc error: code = Internal desc = Could not run process: container_linux.go:348: starting container process caused \"exec: \\\"/init\\\": stat /init: no such file or directory\"" arch=amd64 command=create container=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 name=kata-runtime pid=1924 source=runtime time="2019-05-19T09:29:50.01730045+10:00" level=warning msg="load sandbox devices failed" arch=amd64 command=create container=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 error="open /run/vc/sbs/35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213/devices.json: no such file or directory" name=kata-runtime pid=2261 sandbox=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 sandboxid=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 source=virtcontainers subsystem=sandbox time="2019-05-19T09:29:50.662978175+10:00" level=error msg="rpc error: code = Internal desc = Could not run process: container_linux.go:348: starting container process caused \"exec: \\\"/init\\\": stat /init: no such file or directory\"" arch=amd64 command=create container=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 name=kata-runtime pid=2261 source=runtime time="2019-05-19T09:30:31.660265234+10:00" level=warning msg="load sandbox devices failed" arch=amd64 command=create container=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 error="open /run/vc/sbs/35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213/devices.json: no such file or directory" name=kata-runtime pid=2519 sandbox=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 sandboxid=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 source=virtcontainers subsystem=sandbox time="2019-05-19T09:30:32.307653359+10:00" level=error msg="rpc error: code = Internal desc = Could not run process: container_linux.go:348: starting container process caused \"exec: \\\"/init\\\": stat /init: no such file or directory\"" arch=amd64 command=create container=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 name=kata-runtime pid=2519 source=runtime time="2019-05-19T09:30:40.266226882+10:00" level=warning msg="load sandbox devices failed" arch=amd64 command=create container=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 error="open /run/vc/sbs/35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213/devices.json: no such file or directory" name=kata-runtime pid=2900 sandbox=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 sandboxid=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 source=virtcontainers subsystem=sandbox time="2019-05-19T09:30:40.91165799+10:00" level=error msg="rpc error: code = Internal desc = Could not run process: container_linux.go:348: starting container process caused \"exec: \\\"/init\\\": stat /init: no such file or directory\"" arch=amd64 command=create container=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 name=kata-runtime pid=2900 source=runtime time="2019-05-19T09:30:43.395293665+10:00" level=warning msg="load sandbox devices failed" arch=amd64 command=create container=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 error="open /run/vc/sbs/35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213/devices.json: no such file or directory" name=kata-runtime pid=3150 sandbox=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 sandboxid=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 source=virtcontainers subsystem=sandbox time="2019-05-19T09:30:44.017709475+10:00" level=error msg="rpc error: code = Internal desc = Could not run process: container_linux.go:348: starting container process caused \"exec: \\\"/init\\\": stat /init: no such file or directory\"" arch=amd64 command=create container=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 name=kata-runtime pid=3150 source=runtime time="2019-05-19T09:33:29.02322164+10:00" level=warning msg="load sandbox devices failed" arch=amd64 command=create container=b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad error="open /run/vc/sbs/b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad/devices.json: no such file or directory" name=kata-runtime pid=3434 sandbox=b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad sandboxid=b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad source=virtcontainers subsystem=sandbox time="2019-05-19T09:34:17.572255814+10:00" level=warning msg="load sandbox devices failed" arch=amd64 command=create container=b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad error="open /run/vc/sbs/b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad/devices.json: no such file or directory" name=kata-runtime pid=4268 sandbox=b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad sandboxid=b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad source=virtcontainers subsystem=sandbox time="2019-05-19T09:34:25.496232096+10:00" level=warning msg="Could not umount" arch=amd64 command=kill container=b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad error="invalid argument" host-path=/run/kata-containers/shared/sandboxes/b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad/b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad-e8b757f0477540ee-data name=kata-runtime pid=4413 sandbox=b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad source=virtcontainers subsystem=container time="2019-05-19T09:34:25.496401708+10:00" level=error msg="invalid argument" arch=amd64 command=kill container=b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad name=kata-runtime pid=4413 sandbox=b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad source=runtime time="2019-05-19T09:34:26.134012239+10:00" level=error msg="failed to cleanup vm share path /run/kata-containers/shared/sandboxes/b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad" arch=amd64 command=delete container=b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad error="unlinkat /run/kata-containers/shared/sandboxes/b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad/b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad/rootfs: device or resource busy" name=kata-runtime pid=4466 sandbox=b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad source=virtcontainers subsystem=kata_agent time="2019-05-19T09:34:43.568298292+10:00" level=warning msg="load sandbox devices failed" arch=amd64 command=create container=b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad error="open /run/vc/sbs/b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad/devices.json: no such file or directory" name=kata-runtime pid=601 sandbox=b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad sandboxid=b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad source=virtcontainers subsystem=sandbox time="2019-05-19T09:34:46.44524099+10:00" level=error msg="rpc error: code = Internal desc = Could not run process: container_linux.go:348: starting container process caused \"exec: \\\"/init\\\": stat /init: no such file or directory\"" arch=amd64 command=create container=b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad name=kata-runtime pid=601 source=runtime time="2019-05-19T09:35:18.323966826+10:00" level=warning msg="load sandbox devices failed" arch=amd64 command=create container=b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad error="open /run/vc/sbs/b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad/devices.json: no such file or directory" name=kata-runtime pid=943 sandbox=b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad sandboxid=b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad source=virtcontainers subsystem=sandbox time="2019-05-19T09:35:18.94462155+10:00" level=error msg="rpc error: code = Internal desc = Could not run process: container_linux.go:348: starting container process caused \"exec: \\\"/init\\\": stat /init: no such file or directory\"" arch=amd64 command=create container=b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad name=kata-runtime pid=943 source=runtime time="2019-05-19T09:37:58.960832444+10:00" level=error msg="open /var/lib/vc/sbs: permission denied" arch=amd64 command=list name=kata-runtime pid=1083 source=runtime time="2019-05-19T09:38:40.331955739+10:00" level=warning msg="load sandbox devices failed" arch=amd64 command=create container=b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad error="open /run/vc/sbs/b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad/devices.json: no such file or directory" name=kata-runtime pid=1242 sandbox=b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad sandboxid=b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad source=virtcontainers subsystem=sandbox time="2019-05-19T09:38:40.973575113+10:00" level=error msg="rpc error: code = Internal desc = Could not run process: container_linux.go:348: starting container process caused \"exec: \\\"/init\\\": stat /init: no such file or directory\"" arch=amd64 command=create container=b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad name=kata-runtime pid=1242 source=runtime time="2019-05-19T10:02:53.207154422+10:00" level=warning msg="load sandbox devices failed" arch=amd64 command=create container=a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd error="open /run/vc/sbs/a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd/devices.json: no such file or directory" name=kata-runtime pid=2793 sandbox=a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd sandboxid=a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd source=virtcontainers subsystem=sandbox time="2019-05-19T10:03:22.896063881+10:00" level=warning msg="load sandbox devices failed" arch=amd64 command=create container=a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd error="open /run/vc/sbs/a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd/devices.json: no such file or directory" name=kata-runtime pid=3397 sandbox=a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd sandboxid=a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd source=virtcontainers subsystem=sandbox time="2019-05-19T10:03:32.271814275+10:00" level=warning msg="Could not umount" arch=amd64 command=kill container=a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd error="invalid argument" host-path=/run/kata-containers/shared/sandboxes/a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd/a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd-b090348f07323604-data name=kata-runtime pid=3556 sandbox=a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd source=virtcontainers subsystem=container time="2019-05-19T10:03:32.271947503+10:00" level=error msg="invalid argument" arch=amd64 command=kill container=a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd name=kata-runtime pid=3556 sandbox=a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd source=runtime time="2019-05-19T10:03:33.509258124+10:00" level=error msg="failed to cleanup vm share path /run/kata-containers/shared/sandboxes/a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd" arch=amd64 command=delete container=a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd error="unlinkat /run/kata-containers/shared/sandboxes/a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd/a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd/rootfs: device or resource busy" name=kata-runtime pid=3606 sandbox=a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd source=virtcontainers subsystem=kata_agent time="2019-05-19T10:03:51.705219478+10:00" level=warning msg="load sandbox devices failed" arch=amd64 command=create container=a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd error="open /run/vc/sbs/a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd/devices.json: no such file or directory" name=kata-runtime pid=599 sandbox=a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd sandboxid=a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd source=virtcontainers subsystem=sandbox time="2019-05-19T10:03:54.574345221+10:00" level=error msg="rpc error: code = Internal desc = Could not run process: container_linux.go:348: starting container process caused \"exec: \\\"/init\\\": stat /init: no such file or directory\"" arch=amd64 command=create container=a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd name=kata-runtime pid=599 source=runtime time="2019-05-19T10:04:13.877245594+10:00" level=warning msg="load sandbox devices failed" arch=amd64 command=create container=a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd error="open /run/vc/sbs/a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd/devices.json: no such file or directory" name=kata-runtime pid=905 sandbox=a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd sandboxid=a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd source=virtcontainers subsystem=sandbox time="2019-05-19T10:04:14.517866572+10:00" level=error msg="rpc error: code = Internal desc = Could not run process: container_linux.go:348: starting container process caused \"exec: \\\"/init\\\": stat /init: no such file or directory\"" arch=amd64 command=create container=a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd name=kata-runtime pid=905 source=runtime time="2019-05-19T10:04:58.78065418+10:00" level=warning msg="load sandbox devices failed" arch=amd64 command=create container=a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd error="open /run/vc/sbs/a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd/devices.json: no such file or directory" name=kata-runtime pid=1200 sandbox=a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd sandboxid=a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd source=virtcontainers subsystem=sandbox time="2019-05-19T10:04:59.412195903+10:00" level=error msg="rpc error: code = Internal desc = Could not run process: container_linux.go:348: starting container process caused \"exec: \\\"/init\\\": stat /init: no such file or directory\"" arch=amd64 command=create container=a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd name=kata-runtime pid=1200 source=runtime ``` ## Proxy logs Recent proxy problems found in system journal: ``` time="2019-05-19T09:12:36.785996796+10:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213/proxy.sock: use of closed network connection" name=kata-proxy pid=8635 sandbox=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 source=proxy time="2019-05-19T09:24:28.819463023+10:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213/proxy.sock: use of closed network connection" name=kata-proxy pid=892 sandbox=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 source=proxy time="2019-05-19T09:25:06.543479871+10:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213/kata.sock: use of closed network connection" name=kata-proxy pid=1159 sandbox=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 source=proxy time="2019-05-19T09:25:45.986638902+10:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/516f62c4ea254cba7b8e1998a0aa2ade316f3a5aa637ce7e947a926cae51d201/kata.sock: use of closed network connection" name=kata-proxy pid=1296 sandbox=516f62c4ea254cba7b8e1998a0aa2ade316f3a5aa637ce7e947a926cae51d201 source=proxy time="2019-05-19T09:25:58.263418947+10:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213/proxy.sock: use of closed network connection" name=kata-proxy pid=1565 sandbox=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 source=proxy time="2019-05-19T09:27:33.645707098+10:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213/kata.sock: use of closed network connection" name=kata-proxy pid=1958 sandbox=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 source=proxy time="2019-05-19T09:29:45.649212534+10:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/8d4512b5a9865f4815d47b49481519215d0122374b21aa0274f7a39faed91354/kata.sock: use of closed network connection" name=kata-proxy pid=1727 sandbox=8d4512b5a9865f4815d47b49481519215d0122374b21aa0274f7a39faed91354 source=proxy time="2019-05-19T09:29:50.629925309+10:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213/kata.sock: use of closed network connection" name=kata-proxy pid=2295 sandbox=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 source=proxy time="2019-05-19T09:29:50.629998184+10:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213/proxy.sock: use of closed network connection" name=kata-proxy pid=2295 sandbox=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 source=proxy time="2019-05-19T09:30:32.278256208+10:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213/proxy.sock: use of closed network connection" name=kata-proxy pid=2554 sandbox=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 source=proxy time="2019-05-19T09:30:40.878742402+10:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213/kata.sock: use of closed network connection" name=kata-proxy pid=2933 sandbox=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 source=proxy time="2019-05-19T09:30:43.990821979+10:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213/proxy.sock: use of closed network connection" name=kata-proxy pid=3184 sandbox=35d8e4923e87e8e74d3ddf46de16cf05f8b984ec738e95f7e1f6ab010210f213 source=proxy time="2019-05-19T09:34:13.53290156+10:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad/proxy.sock: use of closed network connection" name=kata-proxy pid=3468 sandbox=b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad source=proxy time="2019-05-19T09:34:25.565407803+10:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad/kata.sock: use of closed network connection" name=kata-proxy pid=4301 sandbox=b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad source=proxy time="2019-05-19T09:34:46.428799143+10:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad/proxy.sock: use of closed network connection" name=kata-proxy pid=640 sandbox=b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad source=proxy time="2019-05-19T09:35:18.912390107+10:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad/proxy.sock: use of closed network connection" name=kata-proxy pid=978 sandbox=b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad source=proxy time="2019-05-19T09:38:40.939357722+10:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad/kata.sock: use of closed network connection" name=kata-proxy pid=1277 sandbox=b77d590d155e45f8c4b12c1824a94e6887f8c34beb0ae7f0fb0273330b519aad source=proxy time="2019-05-19T10:03:15.931921375+10:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd/proxy.sock: use of closed network connection" name=kata-proxy pid=2830 sandbox=a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd source=proxy time="2019-05-19T10:03:32.341215664+10:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd/proxy.sock: use of closed network connection" name=kata-proxy pid=3431 sandbox=a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd source=proxy time="2019-05-19T10:03:54.55624961+10:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd/kata.sock: use of closed network connection" name=kata-proxy pid=637 sandbox=a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd source=proxy time="2019-05-19T10:04:14.487549913+10:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd/proxy.sock: use of closed network connection" name=kata-proxy pid=940 sandbox=a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd source=proxy time="2019-05-19T10:04:59.381613435+10:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd/proxy.sock: use of closed network connection" name=kata-proxy pid=1234 sandbox=a2258222f44a5ddb9c81c089202b448fa78dc7b89742d535cc2a1fc767b5e7fd source=proxy ``` ## Shim logs No recent shim problems found in system journal. ## Throttler logs No recent throttler problems found in system journal. --- # Container manager details Have `docker` ## Docker Output of "`docker version`": ``` Client: Version: 18.06.3 API version: 1.38 Go version: go1.12.5 Git commit: d7080c17a580919f5340a15a8e5e013133089680 Built: Fri May 10 17:02:29 2019 OS/Arch: linux/amd64 Experimental: false Server: Engine: Version: 18.06.3 API version: 1.38 (minimum version 1.12) Go version: go1.12.5 Git commit: d7080c17a580919f5340a15a8e5e013133089680 Built: Fri May 10 17:02:40 2019 OS/Arch: linux/amd64 Experimental: false ``` Output of "`docker info`": ``` Containers: 1 Running: 0 Paused: 0 Stopped: 1 Images: 2 Server Version: 18.06.3 Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Native Overlay Diff: false Logging Driver: json-file Cgroup Driver: cgroupfs Plugins: Volume: local Network: bridge host macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog Swarm: inactive Runtimes: kata-runtime runc Default Runtime: kata-runtime Init Binary: docker-init containerd version: 1.2.6 (expected: 468a545b9edcd5932818eb9de8e72413e616e86e) runc version: <> (expected: a592beb5bc4c4092b1b1bac971afed27687340c5) init version: N/A (expected: ) Security Options: seccomp Profile: default Kernel Version: 4.19.44-36.lts2018 Operating System: Clear Linux OS OSType: linux Architecture: x86_64 CPUs: 4 Total Memory: 7.724GiB Name: block ID: QOLD:G35K:U4HU:A45J:FBDX:S25D:TASW:QKGF:TMZA:LPLP:WE2R:3DWQ Docker Root Dir: /var/lib/docker Debug Mode (client): false Debug Mode (server): false Registry: https://index.docker.io/v1/ Labels: Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false ``` Output of "`systemctl show docker`": ``` Type=notify Restart=on-failure NotifyAccess=main RestartUSec=100ms TimeoutStartUSec=infinity TimeoutStopUSec=1min 30s RuntimeMaxUSec=infinity WatchdogUSec=0 WatchdogTimestampMonotonic=0 RootDirectoryStartOnly=no RemainAfterExit=no GuessMainPID=yes MainPID=325 ControlPID=0 FileDescriptorStoreMax=0 NFileDescriptorStore=0 StatusErrno=0 Result=success UID=[not set] GID=[not set] NRestarts=0 ExecMainStartTimestamp=Sun 2019-05-19 10:03:50 AEST ExecMainStartTimestampMonotonic=6005655 ExecMainExitTimestampMonotonic=0 ExecMainPID=325 ExecMainCode=0 ExecMainStatus=0 ExecStart={ path=/usr/bin/dockerd ; argv[]=/usr/bin/dockerd $DOCKER_EXTRA_RUNTIMES $DOCKER_DEFAULT_RUNTIME $DOCKER_EXTRA_OPTS --storage-driver=overlay2 ; ignore_errors=no ; start_time=[Sun 2019-05-19 10:03:50 AEST] ; stop_time=[n/a] ; pid=325 ; 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=294395904 CPUUsageNSec=[not set] TasksCurrent=30 IPIngressBytes=18446744073709551615 IPIngressPackets=18446744073709551615 IPEgressBytes=18446744073709551615 IPEgressPackets=18446744073709551615 Delegate=yes DelegateControllers=cpu cpuacct io blkio memory devices pids bpf-firewall bpf-devices CPUAccounting=no CPUWeight=[not set] StartupCPUWeight=[not set] CPUShares=[not set] StartupCPUShares=[not set] CPUQuotaPerSecUSec=infinity IOAccounting=no IOWeight=[not set] StartupIOWeight=[not set] BlockIOAccounting=no BlockIOWeight=[not set] StartupBlockIOWeight=[not set] MemoryAccounting=yes MemoryMin=0 MemoryLow=0 MemoryHigh=infinity MemoryMax=infinity MemorySwapMax=infinity MemoryLimit=infinity DevicePolicy=auto TasksAccounting=yes TasksMax=4915 IPAccounting=no Environment=[unprintable] [unprintable] UMask=0022 LimitCPU=infinity LimitCPUSoft=infinity LimitFSIZE=infinity LimitFSIZESoft=infinity LimitDATA=infinity LimitDATASoft=infinity LimitSTACK=infinity LimitSTACKSoft=8388608 LimitCORE=infinity LimitCORESoft=infinity LimitRSS=infinity LimitRSSSoft=infinity LimitNOFILE=infinity LimitNOFILESoft=infinity LimitAS=infinity LimitASSoft=infinity LimitNPROC=infinity LimitNPROCSoft=infinity LimitMEMLOCK=65536 LimitMEMLOCKSoft=65536 LimitLOCKS=infinity LimitLOCKSSoft=infinity LimitSIGPENDING=31147 LimitSIGPENDINGSoft=31147 LimitMSGQUEUE=819200 LimitMSGQUEUESoft=819200 LimitNICE=0 LimitNICESoft=0 LimitRTPRIO=0 LimitRTPRIOSoft=0 LimitRTTIME=infinity LimitRTTIMESoft=infinity OOMScoreAdjust=0 Nice=0 IOSchedulingClass=0 IOSchedulingPriority=0 CPUSchedulingPolicy=0 CPUSchedulingPriority=0 TimerSlackNSec=50000 CPUSchedulingResetOnFork=no NonBlocking=no StandardInput=null StandardInputData= StandardOutput=journal StandardError=inherit TTYReset=no TTYVHangup=no TTYVTDisallocate=no SyslogPriority=30 SyslogLevelPrefix=yes SyslogLevel=6 SyslogFacility=3 LogLevelMax=-1 LogRateLimitIntervalUSec=0 LogRateLimitBurst=0 SecureBits=0 CapabilityBoundingSet=cap_chown cap_dac_override cap_dac_read_search cap_fowner cap_fsetid cap_kill cap_setgid cap_setuid cap_setpcap cap_linux_immutable cap_net_bind_service cap_net_broadcast cap_net_admin cap_net_raw cap_ipc_lock cap_ipc_owner cap_sys_module cap_sys_rawio cap_sys_chroot cap_sys_ptrace cap_sys_pacct cap_sys_admin cap_sys_boot cap_sys_nice cap_sys_resource cap_sys_time cap_sys_tty_config cap_mknod cap_lease cap_audit_write cap_audit_control cap_setfcap cap_mac_override cap_mac_admin cap_syslog cap_wake_alarm cap_block_suspend AmbientCapabilities= DynamicUser=no RemoveIPC=no MountFlags= PrivateTmp=no PrivateDevices=no ProtectKernelTunables=no ProtectKernelModules=no ProtectControlGroups=no PrivateNetwork=no PrivateUsers=no PrivateMounts=no ProtectHome=no ProtectSystem=no SameProcessGroup=no UtmpMode=init IgnoreSIGPIPE=yes NoNewPrivileges=no SystemCallErrorNumber=0 LockPersonality=no RuntimeDirectoryPreserve=no RuntimeDirectoryMode=0755 StateDirectoryMode=0755 CacheDirectoryMode=0755 LogsDirectoryMode=0755 ConfigurationDirectoryMode=0755 MemoryDenyWriteExecute=no RestrictRealtime=no RestrictSUIDSGID=no RestrictNamespaces=no MountAPIVFS=no KeyringMode=private KillMode=process KillSignal=15 FinalKillSignal=9 SendSIGKILL=yes SendSIGHUP=no WatchdogSignal=6 Id=docker.service Names=docker.service Requires=system.slice sysinit.target Wants=docker-set-runtime.service network-online.target WantedBy=multi-user.target Conflicts=shutdown.target Before=multi-user.target shutdown.target After=network-online.target sysinit.target basic.target firewalld.service systemd-journald.socket docker-set-runtime.service system.slice Documentation=https://docs.docker.com Description=Docker Application Container Engine LoadState=loaded ActiveState=active SubState=running FragmentPath=/usr/lib/systemd/system/docker.service DropInPaths=/etc/systemd/system/docker.service.d/50-runtime.conf /usr/lib/systemd/system/docker.service.d/clearlinux.conf UnitFileState=enabled UnitFilePreset=disabled StateChangeTimestamp=Sun 2019-05-19 10:03:54 AEST StateChangeTimestampMonotonic=9815464 InactiveExitTimestamp=Sun 2019-05-19 10:03:50 AEST InactiveExitTimestampMonotonic=6005795 ActiveEnterTimestamp=Sun 2019-05-19 10:03:54 AEST ActiveEnterTimestampMonotonic=9815464 ActiveExitTimestampMonotonic=0 InactiveEnterTimestampMonotonic=0 CanStart=yes CanStop=yes CanReload=yes CanIsolate=no StopWhenUnneeded=no RefuseManualStart=no RefuseManualStop=no AllowIsolate=no DefaultDependencies=yes OnFailureJobMode=replace IgnoreOnIsolate=no NeedDaemonReload=no JobTimeoutUSec=infinity JobRunningTimeoutUSec=infinity JobTimeoutAction=none ConditionResult=yes AssertResult=yes ConditionTimestamp=Sun 2019-05-19 10:03:50 AEST ConditionTimestampMonotonic=6005161 AssertTimestamp=Sun 2019-05-19 10:03:50 AEST AssertTimestampMonotonic=6005161 Transient=no Perpetual=no StartLimitIntervalUSec=1min StartLimitBurst=3 StartLimitAction=none FailureAction=none FailureActionExitStatus=-1 SuccessAction=none SuccessActionExitStatus=-1 InvocationID=c08f93eeee39487197ddeca2e9f5a4b3 CollectMode=inactive ``` No `kubectl` Have `crio` ## crio Output of "`crio --version`": ``` crio version 1.13.6 commit: "" ``` Output of "`systemctl show crio`": ``` Type=notify Restart=on-failure NotifyAccess=main RestartUSec=10s TimeoutStartUSec=infinity TimeoutStopUSec=1min 30s RuntimeMaxUSec=infinity WatchdogUSec=0 WatchdogTimestampMonotonic=0 RootDirectoryStartOnly=no RemainAfterExit=no GuessMainPID=yes MainPID=0 ControlPID=0 FileDescriptorStoreMax=0 NFileDescriptorStore=0 StatusErrno=0 Result=success UID=[not set] GID=[not set] NRestarts=0 ExecMainStartTimestampMonotonic=0 ExecMainExitTimestampMonotonic=0 ExecMainPID=0 ExecMainCode=0 ExecMainStatus=0 ExecStart={ path=/usr/bin/crio ; argv[]=/usr/bin/crio $CRIO_STORAGE_OPTIONS $CRIO_NETWORK_OPTIONS $CRIO_METRICS_OPTIONS ; 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 MemoryCurrent=[not set] CPUUsageNSec=[not set] TasksCurrent=[not set] IPIngressBytes=18446744073709551615 IPIngressPackets=18446744073709551615 IPEgressBytes=18446744073709551615 IPEgressPackets=18446744073709551615 Delegate=no CPUAccounting=no CPUWeight=[not set] StartupCPUWeight=[not set] CPUShares=[not set] StartupCPUShares=[not set] CPUQuotaPerSecUSec=infinity IOAccounting=no IOWeight=[not set] StartupIOWeight=[not set] BlockIOAccounting=no BlockIOWeight=[not set] StartupBlockIOWeight=[not set] MemoryAccounting=yes MemoryMin=0 MemoryLow=0 MemoryHigh=infinity MemoryMax=infinity MemorySwapMax=infinity MemoryLimit=infinity DevicePolicy=auto TasksAccounting=yes TasksMax=infinity IPAccounting=no Environment=GOTRACEBACK=crash EnvironmentFiles=/etc/sysconfig/crio (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=1048576 LimitNOFILESoft=1048576 LimitAS=infinity LimitASSoft=infinity LimitNPROC=1048576 LimitNPROCSoft=1048576 LimitMEMLOCK=65536 LimitMEMLOCKSoft=65536 LimitLOCKS=infinity LimitLOCKSSoft=infinity LimitSIGPENDING=31147 LimitSIGPENDINGSoft=31147 LimitMSGQUEUE=819200 LimitMSGQUEUESoft=819200 LimitNICE=0 LimitNICESoft=0 LimitRTPRIO=0 LimitRTPRIOSoft=0 LimitRTTIME=infinity LimitRTTIMESoft=infinity OOMScoreAdjust=-999 Nice=0 IOSchedulingClass=0 IOSchedulingPriority=0 CPUSchedulingPolicy=0 CPUSchedulingPriority=0 TimerSlackNSec=50000 CPUSchedulingResetOnFork=no NonBlocking=no StandardInput=null StandardInputData= StandardOutput=journal StandardError=inherit TTYReset=no TTYVHangup=no TTYVTDisallocate=no SyslogPriority=30 SyslogLevelPrefix=yes SyslogLevel=6 SyslogFacility=3 LogLevelMax=-1 LogRateLimitIntervalUSec=0 LogRateLimitBurst=0 SecureBits=0 CapabilityBoundingSet=cap_chown cap_dac_override cap_dac_read_search cap_fowner cap_fsetid cap_kill cap_setgid cap_setuid cap_setpcap cap_linux_immutable cap_net_bind_service cap_net_broadcast cap_net_admin cap_net_raw cap_ipc_lock cap_ipc_owner cap_sys_module cap_sys_rawio cap_sys_chroot cap_sys_ptrace cap_sys_pacct cap_sys_admin cap_sys_boot cap_sys_nice cap_sys_resource cap_sys_time cap_sys_tty_config cap_mknod cap_lease cap_audit_write cap_audit_control cap_setfcap cap_mac_override cap_mac_admin cap_syslog cap_wake_alarm cap_block_suspend AmbientCapabilities= DynamicUser=no RemoveIPC=no MountFlags= PrivateTmp=no PrivateDevices=no ProtectKernelTunables=no ProtectKernelModules=no ProtectControlGroups=no PrivateNetwork=no PrivateUsers=no PrivateMounts=no ProtectHome=no ProtectSystem=no SameProcessGroup=no UtmpMode=init IgnoreSIGPIPE=yes NoNewPrivileges=no SystemCallErrorNumber=0 LockPersonality=no RuntimeDirectoryPreserve=no RuntimeDirectoryMode=0755 StateDirectoryMode=0755 CacheDirectoryMode=0755 LogsDirectoryMode=0755 ConfigurationDirectoryMode=0755 MemoryDenyWriteExecute=no RestrictRealtime=no RestrictSUIDSGID=no RestrictNamespaces=no MountAPIVFS=no KeyringMode=private KillMode=control-group KillSignal=15 FinalKillSignal=9 SendSIGKILL=yes SendSIGHUP=no WatchdogSignal=6 Id=crio.service Names=crio.service Requires=system.slice sysinit.target Wants=crio-set-runtime.service Conflicts=shutdown.target Before=shutdown.target After=crio-set-runtime.service basic.target systemd-journald.socket system.slice sysinit.target network-online.target Documentation=https://github.com/cri-o/cri-o Description=Open Container Initiative Daemon LoadState=loaded ActiveState=inactive SubState=dead FragmentPath=/usr/lib/systemd/system/crio.service DropInPaths=/usr/lib/systemd/system/crio.service.d/crio-clearlinux.conf UnitFileState=disabled UnitFilePreset=disabled StateChangeTimestampMonotonic=0 InactiveExitTimestampMonotonic=0 ActiveEnterTimestampMonotonic=0 ActiveExitTimestampMonotonic=0 InactiveEnterTimestampMonotonic=0 CanStart=yes CanStop=yes CanReload=yes CanIsolate=no StopWhenUnneeded=no RefuseManualStart=no RefuseManualStop=no AllowIsolate=no DefaultDependencies=yes OnFailureJobMode=replace IgnoreOnIsolate=no NeedDaemonReload=no JobTimeoutUSec=infinity JobRunningTimeoutUSec=infinity JobTimeoutAction=none ConditionResult=no AssertResult=no ConditionTimestampMonotonic=0 AssertTimestampMonotonic=0 Transient=no Perpetual=no StartLimitIntervalUSec=2min StartLimitBurst=6 StartLimitAction=none FailureAction=none FailureActionExitStatus=-1 SuccessAction=none SuccessActionExitStatus=-1 CollectMode=inactive ``` Output of "`cat /etc/crio/crio.conf`": ``` cat: /etc/crio/crio.conf: No such file or directory ``` Have `containerd` ## containerd Output of "`containerd --version`": ``` containerd github.com/containerd/containerd 1.2.6 1.2.6 ``` Output of "`systemctl show containerd`": ``` Type=simple Restart=always NotifyAccess=none RestartUSec=5s TimeoutStartUSec=1min 30s TimeoutStopUSec=1min 30s RuntimeMaxUSec=infinity WatchdogUSec=0 WatchdogTimestampMonotonic=0 RootDirectoryStartOnly=no RemainAfterExit=no GuessMainPID=yes MainPID=0 ControlPID=0 FileDescriptorStoreMax=0 NFileDescriptorStore=0 StatusErrno=0 Result=success UID=[not set] GID=[not set] NRestarts=0 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 } ExecStart={ path=/usr/bin/containerd ; argv[]=/usr/bin/containerd ; ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 } Slice=system.slice MemoryCurrent=[not set] CPUUsageNSec=[not set] TasksCurrent=[not set] IPIngressBytes=18446744073709551615 IPIngressPackets=18446744073709551615 IPEgressBytes=18446744073709551615 IPEgressPackets=18446744073709551615 Delegate=yes DelegateControllers=cpu cpuacct io blkio memory devices pids bpf-firewall bpf-devices CPUAccounting=no CPUWeight=[not set] StartupCPUWeight=[not set] CPUShares=[not set] StartupCPUShares=[not set] CPUQuotaPerSecUSec=infinity IOAccounting=no IOWeight=[not set] StartupIOWeight=[not set] BlockIOAccounting=no BlockIOWeight=[not set] StartupBlockIOWeight=[not set] MemoryAccounting=yes MemoryMin=0 MemoryLow=0 MemoryHigh=infinity MemoryMax=infinity MemorySwapMax=infinity MemoryLimit=infinity DevicePolicy=auto TasksAccounting=yes TasksMax=4915 IPAccounting=no UMask=0022 LimitCPU=infinity LimitCPUSoft=infinity LimitFSIZE=infinity LimitFSIZESoft=infinity LimitDATA=infinity LimitDATASoft=infinity LimitSTACK=infinity LimitSTACKSoft=8388608 LimitCORE=infinity LimitCORESoft=infinity LimitRSS=infinity LimitRSSSoft=infinity LimitNOFILE=1048576 LimitNOFILESoft=1048576 LimitAS=infinity LimitASSoft=infinity LimitNPROC=infinity LimitNPROCSoft=infinity LimitMEMLOCK=65536 LimitMEMLOCKSoft=65536 LimitLOCKS=infinity LimitLOCKSSoft=infinity LimitSIGPENDING=31147 LimitSIGPENDINGSoft=31147 LimitMSGQUEUE=819200 LimitMSGQUEUESoft=819200 LimitNICE=0 LimitNICESoft=0 LimitRTPRIO=0 LimitRTPRIOSoft=0 LimitRTTIME=infinity LimitRTTIMESoft=infinity OOMScoreAdjust=-999 Nice=0 IOSchedulingClass=0 IOSchedulingPriority=0 CPUSchedulingPolicy=0 CPUSchedulingPriority=0 TimerSlackNSec=50000 CPUSchedulingResetOnFork=no NonBlocking=no StandardInput=null StandardInputData= StandardOutput=journal StandardError=inherit TTYReset=no TTYVHangup=no TTYVTDisallocate=no SyslogPriority=30 SyslogLevelPrefix=yes SyslogLevel=6 SyslogFacility=3 LogLevelMax=-1 LogRateLimitIntervalUSec=0 LogRateLimitBurst=0 SecureBits=0 CapabilityBoundingSet=cap_chown cap_dac_override cap_dac_read_search cap_fowner cap_fsetid cap_kill cap_setgid cap_setuid cap_setpcap cap_linux_immutable cap_net_bind_service cap_net_broadcast cap_net_admin cap_net_raw cap_ipc_lock cap_ipc_owner cap_sys_module cap_sys_rawio cap_sys_chroot cap_sys_ptrace cap_sys_pacct cap_sys_admin cap_sys_boot cap_sys_nice cap_sys_resource cap_sys_time cap_sys_tty_config cap_mknod cap_lease cap_audit_write cap_audit_control cap_setfcap cap_mac_override cap_mac_admin cap_syslog cap_wake_alarm cap_block_suspend AmbientCapabilities= DynamicUser=no RemoveIPC=no MountFlags= PrivateTmp=no PrivateDevices=no ProtectKernelTunables=no ProtectKernelModules=no ProtectControlGroups=no PrivateNetwork=no PrivateUsers=no PrivateMounts=no ProtectHome=no ProtectSystem=no SameProcessGroup=no UtmpMode=init IgnoreSIGPIPE=yes NoNewPrivileges=no SystemCallErrorNumber=0 LockPersonality=no RuntimeDirectoryPreserve=no RuntimeDirectoryMode=0755 StateDirectoryMode=0755 CacheDirectoryMode=0755 LogsDirectoryMode=0755 ConfigurationDirectoryMode=0755 MemoryDenyWriteExecute=no RestrictRealtime=no RestrictSUIDSGID=no RestrictNamespaces=no MountAPIVFS=no KeyringMode=private KillMode=process KillSignal=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=basic.target sysinit.target system.slice systemd-journald.socket network.target Documentation=https://containerd.io Description=containerd container runtime LoadState=loaded ActiveState=inactive 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 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 FailureActionExitStatus=-1 SuccessAction=none SuccessActionExitStatus=-1 CollectMode=inactive ``` Output of "`cat /etc/containerd/config.toml`": ``` cat: /etc/containerd/config.toml: No such file or directory ``` --- # Packages No `dpkg` No `rpm` --- ```
devimc commented 5 years ago

@pceiley thanks for raising this, are you running this test in a virtual machine? Can you reproduce it in other distro (no clearlinux)?

I can't reproduce this issue in a virtual machine with Ubuntu 18.04

jodh-intel commented 5 years ago

Hi @pceiley. Looking at the information provided, there are a few worrying errors:

level=warning msg="Could not umount"
level=error msg="invalid argument"

But the main one which I think would explain the behaviour you are seeing is:

level=error msg="open /var/lib/vc/sbs: permission denied"

Could you check to see what permissions that directory has? Have you changed users or reset permissions below /var maybe?

pceiley commented 5 years ago

Hi @devimc & @jodh-intel: thanks very much for the replies!

Could you check to see what permissions that directory has?

$ sudo ls -la /var/lib/vc/sbs
total 8
drwxr-x--- 2 root root 4096 May 19 12:24 .
drwxr-x--- 3 root root 4096 May 18 18:02 ..

Does this look correct?

Have you changed users or reset permissions below /var maybe?

Certainly not intentionally!

are you running this test in a virtual machine?

No - bare metal.

Can you reproduce it in other distro (no clearlinux)?

I haven't tried. It's a server and it does some pretty critical things so can't really afford to mess around with it.