Simon Richter <s...@debian.org> writes: > I have several containers that are allowed to address the docker > instance they are running on to start additional containers, without > ever having a need to run the docker daemon themselves. > > Since Docker has quite an extensive list of dependencies, it would be > nice if the client could be installed separately.
Let me read this back to see if that would address your concern: - Currently, the docker.io binary package ships: -rwxr-xr-x root/root 28651408 ./usr/bin/docker -rwxr-xr-x root/root 2141168 ./usr/sbin/docker-proxy -rwxr-xr-x root/root 91274536 ./usr/sbin/dockerd - The binary package docker.io currently declares: Depends: libc6 (>= 2.34), libsystemd0, adduser, containerd (>= 1.4~), iptables, sysvinit-utils (>= 3.05-4~), runc (>= 1.0.0~rc8~), tini The suggestion at hand is to introduce a new binary package (let's call it "docker-client") that ships: -rwxr-xr-x root/root 28651408 ./usr/bin/docker And doesn't declare depends on adduser, containerd, iptables, sysvinit-utils, runc or tini. That means you would not need the docker-proxy or the dockerd inside the container because you are providing a Docker-in-Docker setup where the container gets the control socker of the dockerd from the host available as a bind-mount. Did I get that right? Mind sending a patch? best, -rt
