3 ms·
Nearly all points (daemon-less runtimes, daemon-less builds) the author has mentioned has been addressed by open source ecosystem in smaller standalone projects
by alpb 7y ago
Nearly all points (daemon-less runtimes, daemon-less builds) the author has mentioned has been addressed by open source ecosystem in smaller standalone projects that are available.
Docker provides a nice high-level layer for the end user on the developer machine. Its CLI is efficient, so are the builds when they're local, with a cache. I still use it on my dev machine despite being aware of the alternatives.
Anyone security-aware company using containers in production most likely go with non-Docker approaches. Some notable examples include runc, Podman, Buildah, img, ko, Bazel/distroless.
- solipsism 7y agoDistroless is not non-Docker, it's very much Docker.
- alpb 7y agoPlease explain. You can build images using Bazel with distroless as the base image. Similarly I think Jib/ko use distroless images without needing a docker engine.
- solipsism 7y agoThe thing you build is a Docker image.
- alpb 7y agoTechnically an OCI image, and there’s nothing relevant that is mentioned in the original article in your argument, and you can run the resulting image without docker so I think at this point your argument sounds like random blabber, sorry.
- pavon 7y agoIt is an OCI image[1], which is supported by multiple runtimes, including docker. [1]https://www.opencontainers.org/ https://www.opencontainers.org/