Linux

47375 readers

1405 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

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Bulk Updating Alpine Linux (monero.house)

submitted 1 year ago by NonDollarCurrency@monero.house to c/linux@lemmy.ml

5 comments fedilink hide all child comments

Hey all, this might be a simple one but I have around 8 LXC Alpine Linux containers running various services. I like to keep my servers up to date but as you can imagine, sshing into 8 servers and running the update and upgrade commands can be cumbersome as well as each machine has to redownload the same packages again and again over and over.

So I guess my questions are:

What is the best way to update and upgrade all 8 servers at the same time?
Is there any way I can run a package cache server so I can point all 8 servers to a single server so I only need to download the packages once?

you are viewing a single comment's thread
view the rest of the comments

[–] lemmyng@beehaw.org 1 points 1 year ago

If you are set on continuing to use LXC, then ansible, puppet, salt, or chef would be the first step. That at least gets you to dip your toes into configuration management, and if you're familiar with that the later parts will become more familiar.

Longer term you should consider moving to OCI containers and runtimes (eg docker or podman). It will feel like a big leap and you'll question certain ways things are done (I should know, I did it myself years ago) but if you approach it with an open mind and give it a chance you'll find that it lets your shift left on the maintenance issues you'll be dealing with. For example with your second question, you update your base image, then build your service containers on top of that. Update once, use everywhere.