3 ms·
If you are only building a container then you can use BuildKit. But there are plenty of instances where having the socket is extremely useful. For example I've
by windexh8er 7y ago
If you are only building a container then you can use BuildKit. But there are plenty of instances where having the socket is extremely useful. For example I've seen plenty of test suites run in a container on a unique host that uses Docker socket to build containers on many other hosts.
The Docker daemon used to be required. It has always done a lot of things. I don't understand your comment given the fact minimizing Docker today is easy because functions of container operations have been broken out into unique tools over time. Part of Dockers success, I believe, is that you could do everything in a single install.
- zaro 7y ago> But there are plenty of instances where having the socket is extremely useful. Of course there are plenty of cases where the socket is useful, but you can have the daemon on top of non daemon requiring tools. Which BTW is the direction docker is going in now, when it is an industry standard. >The Docker daemon used to be required. It has always done a lot of things. But initially docker was doing two things only, build a container and run a container. And for both daemon is not required. > Part of Dockers success, I believe, is that you could do everything in a single install. Single install has to do only with packaging, not the architecture or docker.