weixin_39693971
2020-12-08 19:41 阅读 2

Exec a process and exit will hang there waiting for terminal close

Description of problem

When exec a shell process and then run a background process in it, and then exit this shell, it will hang there waiting the terminal close.

How to reproduce: 1: id=sudo docker run -d busybox top 2: sudo docker exec -ti $id sh 3: run "sleep 10000 &" in the container 4: run "exit"

The "exit" will not exit successfully and it will wait there.

The root cause is that, kata assumes once a process exits, its io/terminal will also be closed, once the kata client received the io closed, it will then wait on the process to clean it up. But the problem is that if a child process is run as background and it will also inherit its parent's terminal, thus even the parent process exits, it's terminal will not closed, thus the kata client will wait on the terminal for ever.

Expected result

(replace this text with an explanation of what you thought would happen)

Actual result

(replace this text with details of what actually happened)

$ sudo kata-collect-data.sh

Meta details

Running kata-collect-data.sh version 1.2.0 (commit a39a3f15a3c996648248de28be8719f17604fded) at 2018-09-14.15:38:58.657470931+0800.

Runtime is /usr/local/bin/kata-runtime.

kata-env

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


[Meta]
  Version = "1.0.15"

[Runtime]
  Debug = false
  Path = "/usr/local/bin/kata-runtime"
  [Runtime.Version]
    Semver = "1.2.0"
    Commit = "26e3443d7a6f698ee8557bfb66c454eb7c855d11-dirty"
    OCI = "1.0.1"
  [Runtime.Config]
    Path = "/usr/share/defaults/kata-containers/configuration.toml"

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

[Image]
  Path = ""

[Kernel]
  Path = "/usr/share/kata-containers/kata-vmlinuz-4.14.49.container"
  Parameters = "agent.log=debug"

[Initrd]
  Path = "/usr/share/kata-containers/kata-containers-initrd-2018-09-14-15:11:46.341680236+0800-a126188"

[Proxy]
  Type = "kataProxy"
  Version = "kata-proxy version 1.2.0-5377b5db51fe59b52b07ee442d3598802b23d7f7"
  Path = "/usr/libexec/kata-containers/kata-proxy"
  Debug = false

[Shim]
  Type = "kataShim"
  Version = "kata-shim version 1.2.0-35c7dbabc677b0d67b4b5b21fc87c90090bc5a82"
  Path = "/usr/libexec/kata-containers/kata-shim"
  Debug = false

[Agent]
  Type = "kata"

[Host]
  Kernel = "4.15.0-34-generic"
  Architecture = "amd64"
  VMContainerCapable = true
  SupportVSocks = true
  [Host.Distro]
    Name = "Ubuntu"
    Version = "16.04"
  [Host.CPU]
    Vendor = "GenuineIntel"
    Model = "Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz"

Runtime config files

Runtime default config files


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

Runtime config file contents

Config file /etc/kata-containers/configuration.toml not found Output of "cat "/usr/share/defaults/kata-containers/configuration.toml"":


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

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

[hypervisor.qemu]
path = "/usr/bin/qemu-lite-system-x86_64"
kernel = "/usr/share/kata-containers/vmlinuz.container"
initrd = "/usr/share/kata-containers/kata-containers-initrd.img"
#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 = "agent.log=debug"

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[runtime]
# If enabled, the runtime will log additional debug messages to the
# system log
# (default: disabled)
enable_debug = true
#
# Internetworking model
# Determines how the VM should be connected to the
# the container network interface
# Options:
#
#   - bridged
#     Uses a linux bridge to interconnect the container interface to
#     the VM. Works for most cases except macvlan and ipvlan.
#
#   - macvtap
#     Used when the Container network interface can be bridged using
#     macvtap.
internetworking_model="bridged"

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

Image details

No image

Initrd details


---
osbuilder:
  url: "https://github.com/kata-containers/osbuilder"
  version: "unknown"
rootfs-creation-time: "2018-09-14T07:00:27."
description: "osbuilder rootfs"
file-format-version: "0.0.2"
architecture: "x86_64"
base-distro:
  name: "Alpine"
  version: "v3.7"
  packages:
    default:
      - "iptables"
    extra:

agent:
  url: "https://github.com/kata-containers/agent"
  name: "kata-agent"
  version: "1.3.0-rc0-d32aa7caf3470166e504b5460ff3ffb869506fea"
  agent-is-init-daemon: "yes"

Logfiles

Runtime logs

Recent runtime problems found in system journal:


time="2018-09-14T15:15:59.829856821+08:00" level=debug msg="Could not retrieve anything from storage" arch=amd64 command=create container=1916f63d1f1ba1b2e58df7c0dbded67e1bb9bf22373ae03dfde33b119b076166 name=kata-runtime pid=2261 source=virtcontainers subsystem=kata_agent
time="2018-09-14T15:15:59.829965895+08:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=1916f63d1f1ba1b2e58df7c0dbded67e1bb9bf22373ae03dfde33b119b076166 error="open /run/vc/sbs/1916f63d1f1ba1b2e58df7c0dbded67e1bb9bf22373ae03dfde33b119b076166/devices.json: no such file or directory" name=kata-runtime pid=2261 sandbox=1916f63d1f1ba1b2e58df7c0dbded67e1bb9bf22373ae03dfde33b119b076166 sandboxid=1916f63d1f1ba1b2e58df7c0dbded67e1bb9bf22373ae03dfde33b119b076166 source=virtcontainers subsystem=sandbox
time="2018-09-14T15:16:29.865492866+08:00" level=error msg="Container 1916f63d1f1ba1b2e58df7c0dbded67e1bb9bf22373ae03dfde33b119b076166 not ready, running or paused, cannot send a signal" arch=amd64 command=kill container=1916f63d1f1ba1b2e58df7c0dbded67e1bb9bf22373ae03dfde33b119b076166 name=kata-runtime pid=2424 sandbox=1916f63d1f1ba1b2e58df7c0dbded67e1bb9bf22373ae03dfde33b119b076166 source=runtime
time="2018-09-14T15:16:29.926072067+08:00" level=error msg="Container 1916f63d1f1ba1b2e58df7c0dbded67e1bb9bf22373ae03dfde33b119b076166 not ready, running or paused, cannot send a signal" arch=amd64 command=kill container=1916f63d1f1ba1b2e58df7c0dbded67e1bb9bf22373ae03dfde33b119b076166 name=kata-runtime pid=2453 sandbox=1916f63d1f1ba1b2e58df7c0dbded67e1bb9bf22373ae03dfde33b119b076166 source=runtime
time="2018-09-14T15:17:11.014753531+08:00" level=debug msg="Could not retrieve anything from storage" arch=amd64 command=create container=8f449c43f3cb5e6730b023bb13d8489e28e3f55770620417b58e95b7963519d3 name=kata-runtime pid=2574 source=virtcontainers subsystem=kata_agent
time="2018-09-14T15:17:11.015021083+08:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=8f449c43f3cb5e6730b023bb13d8489e28e3f55770620417b58e95b7963519d3 error="open /run/vc/sbs/8f449c43f3cb5e6730b023bb13d8489e28e3f55770620417b58e95b7963519d3/devices.json: no such file or directory" name=kata-runtime pid=2574 sandbox=8f449c43f3cb5e6730b023bb13d8489e28e3f55770620417b58e95b7963519d3 sandboxid=8f449c43f3cb5e6730b023bb13d8489e28e3f55770620417b58e95b7963519d3 source=virtcontainers subsystem=sandbox
time="2018-09-14T15:19:24.48870142+08:00" level=error msg="remove /run/kata-containers/shared/sandboxes/8f449c43f3cb5e6730b023bb13d8489e28e3f55770620417b58e95b7963519d3/8f449c43f3cb5e6730b023bb13d8489e28e3f55770620417b58e95b7963519d3/rootfs: device or resource busy" arch=amd64 command=kill container=8f449c43f3cb5e6730b023bb13d8489e28e3f55770620417b58e95b7963519d3 name=kata-runtime pid=2898 sandbox=8f449c43f3cb5e6730b023bb13d8489e28e3f55770620417b58e95b7963519d3 source=runtime
time="2018-09-14T15:19:24.511569079+08:00" level=error msg="rpc error: code = FailedPrecondition desc = Could not signal process : rpc error: code = NotFound desc = Container 8f449c43f3cb5e6730b023bb13d8489e28e3f55770620417b58e95b7963519d3 not found" arch=amd64 command=kill container=8f449c43f3cb5e6730b023bb13d8489e28e3f55770620417b58e95b7963519d3 name=kata-runtime pid=2912 sandbox=8f449c43f3cb5e6730b023bb13d8489e28e3f55770620417b58e95b7963519d3 source=runtime
time="2018-09-14T15:24:48.813622818+08:00" level=debug msg="Could not retrieve anything from storage" arch=amd64 command=create container=234fc081208b5fdc4c640dbc8a1ddd436e4decbd99df99d578f0dcadc6323bf6 name=kata-runtime pid=3420 source=virtcontainers subsystem=kata_agent
time="2018-09-14T15:24:48.8137411+08:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=234fc081208b5fdc4c640dbc8a1ddd436e4decbd99df99d578f0dcadc6323bf6 error="open /run/vc/sbs/234fc081208b5fdc4c640dbc8a1ddd436e4decbd99df99d578f0dcadc6323bf6/devices.json: no such file or directory" name=kata-runtime pid=3420 sandbox=234fc081208b5fdc4c640dbc8a1ddd436e4decbd99df99d578f0dcadc6323bf6 sandboxid=234fc081208b5fdc4c640dbc8a1ddd436e4decbd99df99d578f0dcadc6323bf6 source=virtcontainers subsystem=sandbox
time="2018-09-14T15:25:23.36674057+08:00" level=error msg="remove /run/kata-containers/shared/sandboxes/234fc081208b5fdc4c640dbc8a1ddd436e4decbd99df99d578f0dcadc6323bf6/234fc081208b5fdc4c640dbc8a1ddd436e4decbd99df99d578f0dcadc6323bf6/rootfs: device or resource busy" arch=amd64 command=kill container=234fc081208b5fdc4c640dbc8a1ddd436e4decbd99df99d578f0dcadc6323bf6 name=kata-runtime pid=3645 sandbox=234fc081208b5fdc4c640dbc8a1ddd436e4decbd99df99d578f0dcadc6323bf6 source=runtime
time="2018-09-14T15:25:23.402428947+08:00" level=error msg="rpc error: code = FailedPrecondition desc = Could not signal process : rpc error: code = NotFound desc = Container 234fc081208b5fdc4c640dbc8a1ddd436e4decbd99df99d578f0dcadc6323bf6 not found" arch=amd64 command=kill container=234fc081208b5fdc4c640dbc8a1ddd436e4decbd99df99d578f0dcadc6323bf6 name=kata-runtime pid=3658 sandbox=234fc081208b5fdc4c640dbc8a1ddd436e4decbd99df99d578f0dcadc6323bf6 source=runtime

Proxy logs

Recent proxy problems found in system journal:


time="2018-09-14T15:16:29.720065674+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/1916f63d1f1ba1b2e58df7c0dbded67e1bb9bf22373ae03dfde33b119b076166/kata.sock: use of closed network connection" name=kata-proxy pid=2316 sandbox=1916f63d1f1ba1b2e58df7c0dbded67e1bb9bf22373ae03dfde33b119b076166 source=proxy

Shim logs

No recent shim problems found in system journal.

Container manager details

Have docker

Docker

Output of "docker version":


Client:
 Version:           18.06.1-ce
 API version:       1.38
 Go version:        go1.10.3
 Git commit:        e68fc7a
 Built:             Tue Aug 21 17:24:56 2018
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          18.06.1-ce
  API version:      1.38 (minimum version 1.12)
  Go version:       go1.10.3
  Git commit:       e68fc7a
  Built:            Tue Aug 21 17:23:21 2018
  OS/Arch:          linux/amd64
  Experimental:     false

Output of "docker info":


Containers: 31
 Running: 0
 Paused: 0
 Stopped: 31
Images: 9
Server Version: 18.06.1-ce
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: kata-runtime runc
Default Runtime: kata-runtime
Init Binary: docker-init
containerd version: 468a545b9edcd5932818eb9de8e72413e616e86e
runc version: 26e3443d7a6f698ee8557bfb66c454eb7c855d11-dirty (expected: 69663f0bd4b60df09991c08812a60108003fa340)
init version: fec3683
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.15.0-34-generic
Operating System: Ubuntu 16.04.3 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 5.744GiB
Name: ubuntu
ID: 4VUG:CIGQ:DGZT:XCSV:SNTZ:ZRUF:ZSTB:AABR:4OJI:R2V4:GRJY:5UFE
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 26
 Goroutines: 52
 System Time: 2018-09-14T15:38:59.28537204+08:00
 EventsListeners: 0
Username: fupanli
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

WARNING: No swap limit support

Output of "systemctl show docker":


Type=notify
Restart=on-failure
NotifyAccess=main
RestartUSec=100ms
TimeoutStartUSec=infinity
TimeoutStopUSec=1min 30s
RuntimeMaxUSec=infinity
WatchdogUSec=0
WatchdogTimestamp=Fri 2018-09-14 15:24:34 CST
WatchdogTimestampMonotonic=588679858
FailureAction=none
PermissionsStartOnly=no
RootDirectoryStartOnly=no
RemainAfterExit=no
GuessMainPID=yes
MainPID=3138
ControlPID=0
FileDescriptorStoreMax=0
NFileDescriptorStore=0
StatusErrno=0
Result=success
ExecMainStartTimestamp=Fri 2018-09-14 15:24:32 CST
ExecMainStartTimestampMonotonic=587256924
ExecMainExitTimestampMonotonic=0
ExecMainPID=3138
ExecMainCode=0
ExecMainStatus=0
ExecStart={ path=/usr/bin/dockerd ; argv[]=/usr/bin/dockerd -D --add-runtime kata-runtime=/usr/local/bin/kata-runtime --default-runtime=runc --storage-driver=overlay2 ; ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
ExecReload={ path=/bin/kill ; argv[]=/bin/kill -s HUP $MAINPID ; ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
Slice=system.slice
ControlGroup=/system.slice/docker.service
MemoryCurrent=517636096
CPUUsageNSec=9643256371
TasksCurrent=129
Delegate=yes
CPUAccounting=no
CPUShares=18446744073709551615
StartupCPUShares=18446744073709551615
CPUQuotaPerSecUSec=infinity
BlockIOAccounting=no
BlockIOWeight=18446744073709551615
StartupBlockIOWeight=18446744073709551615
MemoryAccounting=no
MemoryLimit=18446744073709551615
DevicePolicy=auto
TasksAccounting=no
TasksMax=18446744073709551615
UMask=0022
LimitCPU=18446744073709551615
LimitCPUSoft=18446744073709551615
LimitFSIZE=18446744073709551615
LimitFSIZESoft=18446744073709551615
LimitDATA=18446744073709551615
LimitDATASoft=18446744073709551615
LimitSTACK=18446744073709551615
LimitSTACKSoft=8388608
LimitCORE=18446744073709551615
LimitCORESoft=18446744073709551615
LimitRSS=18446744073709551615
LimitRSSSoft=18446744073709551615
LimitNOFILE=1048576
LimitNOFILESoft=1048576
LimitAS=18446744073709551615
LimitASSoft=18446744073709551615
LimitNPROC=18446744073709551615
LimitNPROCSoft=18446744073709551615
LimitMEMLOCK=65536
LimitMEMLOCKSoft=65536
LimitLOCKS=18446744073709551615
LimitLOCKSSoft=18446744073709551615
LimitSIGPENDING=23292
LimitSIGPENDINGSoft=23292
LimitMSGQUEUE=819200
LimitMSGQUEUESoft=819200
LimitNICE=0
LimitNICESoft=0
LimitRTPRIO=0
LimitRTPRIOSoft=0
LimitRTTIME=18446744073709551615
LimitRTTIMESoft=18446744073709551615
OOMScoreAdjust=0
Nice=0
IOScheduling=0
CPUSchedulingPolicy=0
CPUSchedulingPriority=0
TimerSlackNSec=50000
CPUSchedulingResetOnFork=no
NonBlocking=no
StandardInput=null
StandardOutput=journal
StandardError=inherit
TTYReset=no
TTYVHangup=no
TTYVTDisallocate=no
SyslogPriority=30
SyslogLevelPrefix=yes
SyslogLevel=6
SyslogFacility=3
SecureBits=0
CapabilityBoundingSet=18446744073709551615
AmbientCapabilities=0
MountFlags=0
PrivateTmp=no
PrivateNetwork=no
PrivateDevices=no
ProtectHome=no
ProtectSystem=no
SameProcessGroup=no
UtmpMode=init
IgnoreSIGPIPE=yes
NoNewPrivileges=no
SystemCallErrorNumber=0
RuntimeDirectoryMode=0755
KillMode=process
KillSignal=15
SendSIGKILL=yes
SendSIGHUP=no
Id=docker.service
Names=docker.service
Requires=docker.socket sysinit.target system.slice
Wants=network-online.target
ConsistsOf=docker.socket
Conflicts=shutdown.target
Before=shutdown.target
After=docker.socket firewalld.service basic.target systemd-journald.socket sysinit.target system.slice network-online.target
TriggeredBy=docker.socket
Documentation=https://docs.docker.com
Description=Docker Application Container Engine
LoadState=loaded
ActiveState=active
SubState=running
FragmentPath=/lib/systemd/system/docker.service
DropInPaths=/etc/systemd/system/docker.service.d/kata-containers.conf
UnitFileState=disabled
UnitFilePreset=enabled
StateChangeTimestamp=Fri 2018-09-14 15:24:34 CST
StateChangeTimestampMonotonic=588679859
InactiveExitTimestamp=Fri 2018-09-14 15:24:32 CST
InactiveExitTimestampMonotonic=587256957
ActiveEnterTimestamp=Fri 2018-09-14 15:24:34 CST
ActiveEnterTimestampMonotonic=588679859
ActiveExitTimestamp=Fri 2018-09-14 15:23:51 CST
ActiveExitTimestampMonotonic=545686104
InactiveEnterTimestamp=Fri 2018-09-14 15:23:52 CST
InactiveEnterTimestampMonotonic=546702097
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
JobTimeoutAction=none
ConditionResult=yes
AssertResult=yes
ConditionTimestamp=Fri 2018-09-14 15:24:32 CST
ConditionTimestampMonotonic=587256358
AssertTimestamp=Fri 2018-09-14 15:24:32 CST
AssertTimestampMonotonic=587256358
Transient=no
StartLimitInterval=60000000
StartLimitBurst=3
StartLimitAction=none

No kubectl

Packages

Have dpkg Output of "dpkg -l|egrep "(cc-oci-runtimecc-runtimerunv|kata-proxy|kata-runtime|kata-shim|kata-containers-image|linux-container|qemu-)"":


ii  kata-containers-image                      1.1.0-30                                     amd64        Kata containers image
ii  kata-linux-container                       4.14.51.1-131                                amd64        linux kernel optimised for container-like workloads.
ii  qemu-hyper                                 2.9.1-1                                      amd64        qemu upstream v2.9.1
ii  qemu-lite                                  2.11.0+git.6ba2bfbee9-44                     amd64        linux kernel optimised for container-like workloads.

Have rpm Output of "rpm -qa|egrep "(cc-oci-runtimecc-runtimerunv|kata-proxy|kata-runtime|kata-shim|kata-containers-image|linux-container|qemu-)"":



该提问来源于开源项目:kata-containers/agent

  • 点赞
  • 写回答
  • 关注问题
  • 收藏
  • 复制链接分享

4条回答 默认 最新

  • weixin_39725154 weixin_39725154 2020-12-08 19:41

    IMO runc is same. The best way to run a process background in a container is docker exec -tid sleep 10000.

    点赞 评论 复制链接分享
  • weixin_39693971 weixin_39693971 2020-12-08 19:41

    Hi
    No, I cannot reproduce this issue on runc using docker. Actually runc/runc-shim can close the terminal successfully even there is background child process running.

    点赞 评论 复制链接分享
  • weixin_39779975 weixin_39779975 2020-12-08 19:41

    Hi - as the template requested, please can you paste the output of sudo kata-collect-data.sh as a comment here so we can understand your environment?

    点赞 评论 复制链接分享
  • weixin_39725154 weixin_39725154 2020-12-08 19:41

    Sorry, you're right. I test with an old version of docker.

    点赞 评论 复制链接分享

相关推荐