Mainly here to keep up with the news on Linux.

  • 1 Post
  • 10 Comments
Joined 1 year ago
cake
Cake day: July 15th, 2023

help-circle
  • Kekin@lemy.loltoSelfhosted@lemmy.worldCaddy and forgejo
    link
    fedilink
    English
    arrow-up
    4
    ·
    2 months ago

    Not really through Caddy but for my setup I have it so the ssh port for Forgejo is only accessible through tailscale. So for push/pulling updated my ssh config file to something like

    Host git.mysite.com HostName tailscaleMachineName User git Port 1234

    Then doing git pull git@git.mysite.com:user/project.git works just fine as long as I am connected to tailscale

    Otherwise you could open the port for Forgejo’s ssh so that you can access it without any vpn




  • I can speak at least for rootless podman, I spent some hours on it and different ways I tried all ended in permission issues.

    I gave up on trying to do it properly and just set the permissions of the /dev/dri device to 666, so that my podman container can use the gpu for transcoding.

    Part of the issue with the container images that I tried is that they create a new user with whatever uid:gid I pass to the container, and so even if my nonroot user is part of the render group, the new user inside the container is not and so it can’t write to the /dev/dri/renderD128 (gpu), and so transcode wouldn’t work.

    That’s where I left the troubleshooting at cause it was being a headache



  • Yeah I’m fairly certain it’s a permission issue. Having the gpu with permissions 666 makes it work inside the containers.

    The thing is also that these container images (plex and jellyfin) create a separate user inside, instead of using the root user, and this new user (“abc” for lsio images) doesn’t get added to the same groups as the root user.

    Also the render group that gets passed to the container appears as “nogroup”, so I thought of adding user abc to “nogroup” but still didn’t seem to work.