3 ms·

Is it accurate to say LXC is to Docker as git is to GitHub, or vim/emacs vs. Visual Studio Code? I haven't seen many examples demonstrating the tooling used to

• haolez 5y ago
  In the first months of Docker, yes. Nowadays, they are different beasts.
• throwawayboise 5y ago
  lxc launch, lxc list, lxc start, lxc stop, etc.... That's all I've ever needed. Docker is overkill if you just need to run a few containers. There is a point where it makes sense but running a few containers for a small/personal project is not it.
  • mrweasel 5y ago
    Funnily enough I view it the other way around. LXC is a bit overkill, I just wanted to run a container, not an entire VM. In my mind you need to treat LXC containers as VMs, in terms of managements. They need to be patched, monitored and maintained the same ways as a VM. Docker containers still need to patched of cause, many seems to forget that bit, but generally they seem easier to deal with. Of cause that depends on what has been stuffed into the container image. LXC is underrated though, for small projects and business it can be a great alternative to VM platforms.
• sarusso 5y ago
  I recently wrote something to clarify my mind around all this [1]. If we assume that by Docker we mean the Docker engine, then I think you might compare it as you said (maybe more in terms as vim/emacs vs. Visual Studio Code as Git is a technology while GitHub is a platform). But Docker is many things: a company, a command line tool, a container runtime, a container engine, an image format, a registry... [1] https://sarusso.github.io/blog_container_engines_runtimes_orchestrators.html https://sarusso.github.io/blog_container_engines_runtimes_or...