• InverseParallax@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        14 days ago

        Nah, there’s something broken, I think it’s because group render under the container has a different GID than the container so the acl fails and you either sudo or chmod.

        Lxc is still a little wobbly in places.

        • Possibly linux@lemmy.zip
          link
          fedilink
          English
          arrow-up
          3
          ·
          edit-2
          14 days ago

          I use podman and since it runs as my user it has exactly same same permissions as me. I just add my user to the proper group and it works.

          Anyway for LXC you could just passthough a folder and then create a file. From there you can look at the file on the host to see who owns it. That will give you the needed information to set permissions correctly

          • InverseParallax@lemmy.world
            link
            fedilink
            English
            arrow-up
            3
            ·
            14 days ago

            Ahh, I’m running priveleged containers, I wrote my own scripted framework for containers around lxc in mostly python.

            Basically I fell head over heels in love with freebsd jails and wanted them on Linux, then started running x11 apps in them, it’s my heroin.

            Haven’t used podman outside proper k8s for work, did proxmox for a bit, but it was just a webgui for the same thing.

            There were a bunch of online bug reports about the /dev/dri issue, maybe there’s a better solution now, but since this is my workstation I wasn’t as worried about security.