Linux

48389 readers

2272 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

I often read that (docker) containers are not good for security. What are secure methods of creating secure isolated environments to run questionable programs in? (lemmy.ml)

submitted 1 year ago by cyclohexane@lemmy.ml to c/linux@lemmy.ml

35 comments fedilink hide all child comments

I've read that standard containers are optimized for developer productivity and not security, which makes sense.

But then what would be ideal to use for security? Suppose I want to isolate environments from each other for security purposes, to run questionable programs or reduce attack surface. What are some secure solutions?

Something without the performance hit of VMs

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

[–] dragnucs@lemmy.ml 3 points 1 year ago (1 children)

This is a problem of the containerized program and the image itself. This problem affect, containers, VM, and baremetal aswel.

[–] boo@beehaw.org 2 points 1 year ago (1 children)

I agree. But imo these usecases are more known and mature in traditional setups, we could apt update and restart a systemd service and its done.

Its not so obvious and there are no mechanisms for containers/images.

(I am not into devops/sysadmin, so this might also be my lack of exposure)

[–] dragnucs@lemmy.ml 2 points 1 year ago (1 children)

Most often, images are updated automatically and are managed by the developers themselves so images are usually up to date. If you don't know how to build images, it may be difficult for you to update the containerized software before the vendor does. But this situation is infrequent.

[–] agressivelyPassive@feddit.de 1 points 1 year ago

Many projects just pull in a bunch of images from wherever and never update them. Especially if it's that one obscure image that happens to package this over obscure app you absolutely need.