9 Commits

Author SHA1 Message Date
liuzekun
294a810705 docker: sync patches from internal
Signed-off-by: liuzekun <liuzekun@huawei.com>
2020-11-28 09:37:25 +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
xiadanni1
07877c6fda docker: use git-commit to store commit ID
Change-Id: Id13ecdba61708f62595d6db593c670c304abf0bb
Signed-off-by: xiadanni1 <xiadanni1@huawei.com>
2020-06-16 02:07:26 +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
Grooooot
e7de2c79b3 docker: add patches
Signed-off-by: Grooooot <isula@huawei.com>
2020-03-05 15:13:09 +08:00
dogsheng
be56a4fe89 Package init 2019-12-25 19:10:46 +08:00
overweight
6138d366d1 Package init 2019-09-30 10:37:25 -04:00