20
submitted 9 months ago* (last edited 9 months ago) by GustavoM@lemmy.world to c/linux@lemmy.ml

Title. Mostly because of two flags: --read-only and --log-driver.

you are viewing a single comment's thread
view the rest of the comments
[-] agressivelyPassive@feddit.de -2 points 9 months ago

I think you still don't get the idea of read-only containers.

They're set up in a way that prohibits any writes except some very well defined locations. That could mean piping logs directly to stdout and don't write them to disk, or not caching on disk, etc.

That is standard practice in professional setup (though for security reasons).

No, it's not magic, but software can get configured, you know? And if you do that properly, you might see a change in behavior.

[-] aksdb@feddit.de 4 points 9 months ago

If the application in question doesn't need to write anything, it also doesn't write outside of docker, so it also won't wear down the SD card.

If the app has to write something, a fully read-only container will simply not work (the app will crash or fail otherwise).

this post was submitted on 03 Dec 2023
20 points (81.2% liked)

Linux

47343 readers
1367 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

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS