Your message dated Mon, 06 Jan 2020 20:16:05 +1100
with message-id <2322258.ngoZA6K3Ya@deblab>
and subject line Re: Bug#948211: Decouple containerd from docker.io again?
has caused the Debian Bug report #948211,
regarding Decouple containerd from docker.io again?
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
948211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948211
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: docker.io
Severity: wishlist
Hi Dmitry Smirnov and Arnaud Rebillout,
I would like to have a standalone containerd package. Containerd has
CRI(Kubernetes Container Runtime Interface) support[1].
This makes it possible to run containerd alone without docker, eg on a
Kubernetes node[2]. And I don't need features like `docker build` in
this scenario.
Would you like to:
a. build a separate containerd package from src:containerd
b. build a separate containerd package from src:docker.io
I think nowadays the docker upstream has much improvement on the
dependencies versions. So a separate src:containerd makes sense. I
checked the docker-ce repo, it has pull containerd 1.3 to its master.
So if you like the option a, I could help move the current
src:containerd from experimental to unstable, when the next docker
major release happens. (of course, the version of containerd should
sync with the docker release.)
[1] https://github.com/containerd/cri/
[2]
https://kubernetes.io/blog/2018/05/24/kubernetes-containerd-integration-goes-ga/
--
Shengjing Zhu
--- End Message ---
--- Begin Message ---
On Sunday, 5 January 2020 11:28:51 PM AEDT Shengjing Zhu wrote:
> I would like to have a standalone containerd package.
We already have standalone "containerd" package in Debian:
https://tracker.debian.org/pkg/containerd
But it is in the bad shape and could benefit from maintainers attention.
Maintaining standalone "containerd" requires skilled capable contributor(s)
with a lot of time to spare or adequate funding.
> Would you like to:
> a. build a separate containerd package from src:containerd
It is already done bot someone should maintain it. Could you?
> b. build a separate containerd package from src:docker.io
Absolutely not. Docker (upstream) is incapable of providing standalone
reusable containerd (or any other components). They had abused all good
software management practices with incorporating (vendoring) private patched
forks of various libraries, depending on a very particular commit of
containerd, etc. We have tried to maintain standalone "containerd" for Docker
consumption in the past and it lead to disaster. Docker is fragile enough
anyway and it should continue to use its own private "containerd" binary
(which is not a problem for those who want to maintain a standalone
"containerd").
> I think nowadays the docker upstream has much improvement on the
> dependencies versions.
I'm skeptical about it. But IMHO it does not matter much anyway because
Docker rapidly becomes a new MySQL. If you remember situation with MySQL, the
world deprecated it in favour of MariaDB due to bad governance of the former.
Docker is not just poorly governed but it is also an inferior technology,
poorly architected. It is rapidly drifting to obsolescence and the successor
(Podman) is just around the corner waiting for acceptance in NEW.
> So a separate src:containerd makes sense. I
> checked the docker-ce repo, it has pull containerd 1.3 to its master.
> So if you like the option a, I could help move the current
> src:containerd from experimental to unstable, when the next docker
> major release happens.
I suggest to take over the standalone containerd package to maintain it as
standalone package without coordination with Docker.
In any case, even if Docker can switch from private to standalone
"containerd", the latter should be brought to shape first.
We, Docker maintainers, have no capacity to spare as maintaining Docker is a
pretty much full time job to take care of 100+ dependency packages.
--
All the best,
Dmitry Smirnov.
---
It is impossible to imagine Goethe or Beethoven being good at billiards
or golf.
-- H. L. Mencken
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
