68
LXD: Containers for Human Beings
(secluded.site)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 20 Sep 2023
68 points (97.2% liked)
Linux
48375 readers
1355 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
Good summary.. had a quick read and I use containers the same way (mostly proxmox these days because it makes them so easy, but it's just lxc under the hood).
I share your dislike of docker-only apps. Lemmy is a good example.. the 'from scratch' install didn't work at all for me and the ansible script just creates docker images..
I work around it by nesting docker in an lxc container for such apps. Keeps them contained in one place.. easier to manage. I have a proxmox template with docker installed (& my base network setup) so it only takes a couple of minutes to spin up.
I'm new to the container world, but everything I've seen and read about so far makes me dislike Docker. I really don't get why it's so popular - except for the cross-platform compatibility I guess?
In a word: convenience.
It was in the right place at the right time with easy UX. A big audience were developers not so familiar with sysadmin in the commercial software world. It provided an easy way to get a kind of executable package. Devs could throw in all their Python/Ruby/JS dependencies and not worry about it. "works on my machine" was basically good enough because you just ship the whole damn thing over.
Docker then supervised the process for you, too. The whole Docker package took care of a lot of things
PS: for those really interested in containers, I always recommend looking into Plan 9: the OS from the original UNIX team intended as a successor to UNIX. Every process has its own namespace and the whole OS is built around that concept (plus a few other core things.. too much to go into here). see also https://pdos.csail.mit.edu/~rsc/plan9.html
Don't forget configuration. A properly built Docker image can be configured purely via environment variables, which are all in one place. That's much more transparent than having 20 locations with tiny changes to the defaults.
There are obviously edge cases where this doesn't work, but even then you still have a just a bundle of config files in one place.