u/1185dfrRvaxAJXPxs9

I've just ordered a Lenovo M720q ThinkCentre i5-9400T 1.8 GHz 256GB 16GB.

I'm setting up a server at home to run:

Docker Compose

Dockhand

Jellyfin & Arr stack

Frigate

Immich

Misc utilities such as Adguard home, Chrony, Samba share

Backup undecided but at this stage thinking Backrest (with Restic)

Remote access via Tailscale

I'm currently running the Jellyfin stack on my gaming PC which is working perfectly but uses too much power.

I'm currently running Frigate, Immich, Adguard, Chrony, Mosquitto as Home Assistant add ons on a Lenovo 6700T with Home Assistant OS, but will move that HA off of the Lenovo (minus the addons) and onto an RPi4b.

So, Debian or Ubuntu for the new server?

I'm really not that interested in Proxmox or such like, it seems simple is better, but that is quite probably just ignorance on my part.

I have Frigate running reliably on my Home Assistant server as a HAOS add on. I'm now trying to install Frigate as a docker container on my Linux Mint PC.

Hardware: Ryzen 7 7800X3D, Radeon RX9060XT-16Gb, 32Gb RAM

Media folder is on a mounted usb hdd /media/user/usb5tb1/frigate

Frigate container is in /home/user/docker/frigate/

Frigate.yml config.yml is in /home/user/docker/frigate/config - I copied this from my working HAOS frigate install, just changed the detector section to:

detectors:
  onnx_0:
    type: onnx

docker-compose.yml:

services:
  frigate:
    image: ghcr.io/blakeblackshear/frigate:stable-rocm
    container_name: frigate
    restart: unless-stopped
    stop_grace_period: 30s
    privileged: true
    shm_size: 512mb
    devices:
      - /dev/dri:/dev/dri # For VAAPI hardware video decoding
      - /dev/kfd:/dev/kfd # For ROCm-based object detection
    volumes:
      - ./config:/config
      - /media/user/usb5tb1/frigate:/media/frigate  
      - type: tmpfs
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    ports:
      - "5000:5000"   # Web UI
      - "8554:8554"   # RTSP feeds
      - "8555:8555/tcp"  # WebRTC over TCP
      - "8555:8555/udp"  # WebRTC over UDP

    environment:
      - LIBVA_DRIVER_NAME=radeonsi 

I'm installing it as a stack using Dockhand - it starts but almost immediately restarts, repeatedly.

I can post the log but it's large, thought I'd ask if anyone cans see an obvious error in the above first.

EDIT: Ok, looks like I'm making life hard installing on my AMD machine. Ultimately Frigate will be running on the Home Assistant hardware that it's running on now (intel i7 6700T with intel GPU) but in a container on Debian server, and HA will be running on a RPi4b. Might just give up on this AMD install and concentrate on the intel box.

Posted this in the Tailscale sub but looks like it's more appropriate to post here...

I'm in the process of de- Google/Microsoft -ing my life. I've been using Proton Mail for a few years now.

I'll be self hosting a lot of things, and Tailscale is just so elegant for remote access I plan to keep using it.

But the Tailscale SSO requires a google (or MS/apple) account for SSO.

Are there any plans to support Proton as an identity provider for services such as Tailscale? Seems there might be a Proton api access issue?

I'm trusting Proton with my email, VPN, password manager, and 2FA - would be great if I could use Proton for Tailscale and other SSO as well.

I'm in the process of de- Google/Microsoft -ing my life. I'll be self hosting a lot of things, but Tailscale is just so elegant for remote access I plan to keep using it.

But this means I need a google (or MS/apple) account for SSO - Github is owned by MS, Okta/Onelogin are paid services. Self-hosting OIDC looks beyond me.

Are there any plans to include Proton as a natively supported identity provider? I'm trusting them with my email , password manager, and 2FA - would be great if I could use them for Tailscale as well.

Very new to this, learning by doing (and breaking).

I understand I just need to copy my docker-compose.yml and .env files somewhere and I can quickly and easily redeploy the stack.

But what about the config files for the containers? What is best practice for this?

eg volumes: - ./config:/config - /media/frigate:/media/frigate

should ./config for each container in the stack instead all point to a common config folder? Then I can just back that up?

I'm assuming there is a simple way to do this but my searches are coming up either empty or so complicated that I think I'm missing something.

I'm currently on my first trip away with Mint on my laptop. So first time I've had to run it on the battery, it's usually plugged in overnight.

Going to bed with power about 75%, in the morning it's dead flat. Never had this issue with Windows.

It's set to suspend when lid is closed in the power management app. Any idea how to troubleshoot this?