Linux

1259 readers

102 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

36 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

[–] boo 1 points 1 year ago (3 children)

It can pull and build containers fine but last time I tried there were some differences. Mounts were not usable because user uid/gid behave quite differently. Tools like portainer dont work on podman containers. I havent tried out any networking or advanced stuff yet.

But i found that the considerations to write docker files are quite different for podman.

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

Differences you find could be related to containers being run rootless, or the host system having SELinux enforcesd. Both problems could be intended behavior and can be soled simply by using by adding correct labels to mount points like :z or :Z. This SELinux feature also affects Docker when setup.

Portaiers tries to connect to a docker sock path that is not the same with Podman. While podman is rootless and does not need a daemon, socks and stuff, it has support for them nevertheless. So you can simply adjust Portainer config to work with podman. I havnt tried it yet but I managed to do similar things for other software.

[–] boo 1 points 1 year ago

I dont have much idea about SELinux, apart from the name. But I think the problem I was having was specifically wrt uid, with docker I used to add user with the same uid/gid as the host user, as a developer this would help me with debugging. But this differs with the non root setup.

[–] mosthated@lemmy.ml 1 points 1 year ago

Gotcha. I use docker containers on computing clusters at the University, but because of security, I have to convert them to singularity containers. That is okay, but I was hoping that by running podman I could prevent this extra step.

[–] cyclohexane@lemmy.ml 0 points 1 year ago (1 children)

Podman supports dockerfile, right?

[–] Tiuku@sopuli.xyz 1 points 1 year ago

Unlike docker, podman doesn't try to do everything on it's own. There's a separate tool known as buildah which builds containers from dockerfiles just fine.

Ps. More generally, they're called containerfiles.