Quote:
Originally Posted by mralk3
Slackware Aarch64 comes with containerization out of the box. It is called "lxc". The man pages are excellent resources and there is also a guide on docs.slackware.com, here:
https://docs.slackware.com/howtos:misc:lxc
Docker is quite popular, but if you are looking for packages that are maintained by the Slackware distribution, this is also an option. It supports a minimal installation of Slackware within each container. |
LXC and Docker can be used for the same purposes but are very different in the way they work and their functionality. There are benefits and drawbacks depending on what the user intends to do with them.
LXC is a great OS virtualization method for working in a real Linux environment. However, it's nowhere near as portable as Docker. LXC images are nowhere near as lightweight as Docker images, but LXC images are more lightweight than the overheads of a physical or virtual machine.
Docker is great for running applications with all the configurations required to run them included within any images. Which means when images are distributed the settings and versions of the services used don’t change. So, with Docker the whole application can be shared without breaking the code when it's run under different OS environments. When a Docker container works on my Linux system you can take that container and run it on your Windows, macOS, FreeBSD system, or whichever OS you have Docker installed. LXC does not afford this scalability or portability. On top of all that, users don't have to set up VMs to deploy Docker images and/or run containers.
Docker initialy used LXC (2013?) but has since revised its code to run a completely new container architecture.
There's nothing wrong with using unofficial packages for getting things done, or broadening the scope of Slackware users, especially when official packages aren't available. Slackbuilds.org offers all the Docker (and its dependencies) build scrtipts. So, why not make good use of them? Why not, indeed.
