17 Commits

Author SHA1 Message Date
chenjiankun
542207bf0a docker: fix terminal abnormal after docker run
fix #I5OBZ9
fix #I5LDB4
fix #I5FTB4
2022-09-13 19:58:50 +08:00
zhongjiawei
777a2b05b8 fix CVE-2021-41092
fix #I5D1C0
fix CVE-2021-41092
2022-06-29 14:52:33 +08:00
zjw
69f6dc243f fix CVE-2021-41091
fix #I5CA8V
fix CVE-2021-41091
2022-06-29 09:57:50 +08:00
zjw
9d4f69f055 fix CVE-2021-41089
fix #I5CA8X
2022-06-29 09:54:58 +08:00
zjw
2b2be77fce close channel in write side to avoid panic in docker stats
fix #I5ATMV
2022-06-29 09:50:20 +08:00
zjw
6b4b0f7702 fix status inconsistent after restart container
fix #I5AIPF
fix #I5AD5N
2022-06-29 09:45:41 +08:00
chenjiankun
e676158bba sync from openEuler-22.03-LTS 2022-06-28 16:29:12 +08:00
duyiwei
632b430ea3 fix CVE-2022-24769 2022-06-10 15:13:38 +08:00
xiadanni
447f294a20 docker:update seccomp whitelist to Linux 5.10 syscall list
Signed-off-by: xiadanni <xiadanni1@huawei.com>
2021-09-26 23:57:52 +08:00
WangFengTu
c7f907b1e3 fix rpmbuild failed
Signed-off-by: WangFengTu <wangfengtu@huawei.com>
2021-08-31 14:22:57 +08:00
DCCooper
0f204a4fd6 docker:remove go-md2man build require
Signed-off-by: DCCooper <1866858@gmail.com>
2021-02-09 18:51:03 +08:00
jingrui
af6293703d docker: sync bugfix
Change-Id: I4dc92059d90415199fcd143d75cc68cfdb67c430
Signed-off-by: jingrui <jingrui@huawei.com>
2021-01-19 14:03:29 +08:00
jingrui
a7fbe55e45 docker: sync daemon pkg to cli vendor
Change-Id: I3f272af66670959fc7d42d5be2526ebf7f9eecfb
Signed-off-by: jingrui <jingrui@huawei.com>
2020-07-06 18:56:50 +08:00
liuzekun
c0d5f8afd5 docker: check whether exit file is exist before kill process directly
kill process directly should check whether exit file is exist already,
for avoid kill the new process which reused this pid

Signed-off-by: liuzekun <liuzekun@huawei.com>
2020-04-10 17:13:31 +08:00
liuzekun
9f71f40e9f docker: 'delete event' is not need to process in daemon processEvent
Signed-off-by: liuzekun <liuzekun@huawei.com>
2020-04-10 11:01:16 +08:00
Grooooot
76b6c4c1b3 docker: Delete stale containerd object on start failure
containerd has two objects with regard to containers.
This is a "container" object which is metadata and a "task" which is
manging the actual runtime state.

When docker starts a container, it creates both the container metadata
and the task at the same time. So when a container exists, docker deletes
both of these objects as well.

This ensures that if, on start, when we go to create the container metadata object
in containerd, if there is an error due to a name conflict taht we go
ahead and clean that up and try again.

backport from upstream: https://github.com/moby/moby/pull/38364

Signed-off-by: Grooooot <isula@huawei.com>
2020-03-17 10:49:57 +08:00
overweight
6138d366d1 Package init 2019-09-30 10:37:25 -04:00