Does docker support hot upgrade from 18.6 to 19.3 ?

Description

Does docker support hot upgrade from 18.6 to 19.3?

Steps to reproduce the issue:

1. In 18.6, I see docker working with docker-containerd, which is a subprocess of docker. It doesn't seem to be able to run independently with docker.
2. and In 19.3 docker working with containerd, containerd is a component that runs independently, regardless of whether docker is running.
3. I wonder if it is possible to upgrade docker from 18.6 to 19.3 and keep the node pods uninterrupted.

Describe the results you received:

Describe the results you expected:

Additional information you deem important (e.g. issue happens only occasionally):

Output of docker version:

Client:
 Version:           18.06.3-ce
 API version:       1.38
 Go version:        go1.10.4
 Git commit:        d7080c1
 Built:             Wed Feb 20 02:24:22 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          18.6.3-ce
  API version:      1.38 (minimum version 1.12)
  Go version:       go1.10.3
  Git commit:       7f659f6724
  Built:            Thu Aug 20 07:10:40 2020
  OS/Arch:          linux/amd64
  Experimental:     false

Output of docker info:

Containers: 49
 Running: 36
 Paused: 0
 Stopped: 13
Images: 82
Server Version: 18.6.3-ce-tke.1
Storage Driver: overlay2
 Backing Filesystem: xfs
 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: runc runc-wrapper
Default Runtime: runc
Init Binary: docker-init
containerd version: e6b3f5632f50dbc4e9cb6288d911bf4f5e95b18e (expected: 468a545b9edcd5932818eb9de8e72413e616e86e)
runc version: dc9208a3303feef5b3839f4323d9beb36df0a9dd (expected: a592beb5bc4c4092b1b1bac971afed27687340c5)
init version: fec3683
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.14.105-1-tlinux3-0019
Operating System: Tencent tlinux 2.2 (Final)
OSType: linux
Architecture: x86_64
CPUs: 90
Total Memory: 187.9GiB
Name: VM-200-122-centos
ID: ZYZ5:FR3Q:UKKH:2I7P:YNS4:Q37D:UWSI:TSSY:FOKI:4PGP:KNXT:B4QL
Docker Root Dir: /data_online/1/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
Registry Mirrors:
 https://mirror.ccs.tencentyun.com/
Live Restore Enabled: true

Additional environment details (AWS, VirtualBox, physical, etc.):

The issue names Docker 18.06, Docker 19.3, docker-containerd, and containerd, but no source file, test, or entry point. Start by checking the project's documented upgrade guidance and runtime-transition behavior; done would require a maintainer-confirmed answer about whether running node pods can remain uninterrupted.