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

  • piezoelectron@sopuli.xyz
    4·
    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@lemmy.ml
      7·
      1 year ago

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

      • piezoelectron@sopuli.xyz
        3·
        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@feddit.uk
          2·
          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

    • mosthated@lemmy.ml
      1·
      1 year ago

      Related to this: can podman completely replace Docker? I.e., can it pull containers and build containers in addition to running them?

      • boo@beehaw.org
        2·
        1 year ago

        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·
          1 year ago

          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.