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?

dragnucs, 1 year ago

It is the application Docker that is not secure. Containers are. In fact Docker runs a daemon as root to wich you communicate from a client. This is what makes it less secure; running under root power. It also has a few shortcomings of privileged containers. This can be easily solved by using podman and SELinux. If you can manage to run Docker rootless, then you are magnitudes higher in security.

piezoelectron, 1 year ago

Do you think Podman is ready to take over Docker? My understanding is that Podman is Docker without the root requirement.

dragnucs, 1 year ago

Yes it is. I’ve been using it for more than a year now. Works reliably. Has pod support aswel.

piezoelectron, 1 year ago

Great. I don’t know enough to use either but I think I’m going to try lean on podman from the get go. In any case, I know that all podman commands are exactly identical to Docker, such that you can replace, say, docker compose with podman compose and move on with ease.

Guilvareux, 1 year ago

With the specific exception of podman compose I completely agree. I haven’t tested it for a while but podman compose has had issues with compose file syntax in my experience. Especially with network configs.

However, I have been using “docker-compose” with podman’s docker compatible socket implementation when necessary, with great success