---
version: "3.4"
services:
  postgresql:
    image: docker.io/library/postgres:12-alpine
    restart: unless-stopped
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -d $${POSTGRES_DB} -U $${POSTGRES_USER}"]
      start_period: 20s
      interval: 30s
      retries: 5
      timeout: 5s
    volumes:
      - database:/var/lib/postgresql/data
    environment:
      POSTGRES_PASSWORD: ${PG_PASS:?database password required}
      POSTGRES_USER: ${PG_USER:-authentik}
      POSTGRES_DB: ${PG_DB:-authentik}
    env_file:
      - .env
  redis:
    image: docker.io/library/redis:alpine
    command: --save 60 1 --loglevel warning
    restart: unless-stopped
    healthcheck:
      test: ["CMD-SHELL", "redis-cli ping | grep PONG"]
      start_period: 20s
      interval: 30s
      retries: 5
      timeout: 3s
    volumes:
      - redis:/data
  server:
    image: ${AUTHENTIK_IMAGE:-ghcr.io/goauthentik/server}:${AUTHENTIK_TAG:-2023.10.4}
    restart: unless-stopped
    command: server
    environment:
      AUTHENTIK_REDIS__HOST: redis
      AUTHENTIK_POSTGRESQL__HOST: postgresql
      AUTHENTIK_POSTGRESQL__USER: ${PG_USER:-authentik}
      AUTHENTIK_POSTGRESQL__NAME: ${PG_DB:-authentik}
      AUTHENTIK_POSTGRESQL__PASSWORD: ${PG_PASS}
    volumes:
      - ./media:/media
      - ./custom-templates:/templates
    env_file:
      - .env
    ports:
      - "${COMPOSE_PORT_HTTP:-9000}:9000"
      - "${COMPOSE_PORT_HTTPS:-9443}:9443"
    depends_on:
      - postgresql
      - redis
  worker:
    image: ${AUTHENTIK_IMAGE:-ghcr.io/goauthentik/server}:${AUTHENTIK_TAG:-2023.10.4}
    restart: unless-stopped
    command: worker
    environment:
      AUTHENTIK_REDIS__HOST: redis
      AUTHENTIK_POSTGRESQL__HOST: postgresql
      AUTHENTIK_POSTGRESQL__USER: ${PG_USER:-authentik}
      AUTHENTIK_POSTGRESQL__NAME: ${PG_DB:-authentik}
      AUTHENTIK_POSTGRESQL__PASSWORD: ${PG_PASS}
    # `user: root` and the docker socket volume are optional.
    # See more for the docker socket integration here:
    # https://goauthentik.io/docs/outposts/integrations/docker
    # Removing `user: root` also prevents the worker from fixing the permissions
    # on the mounted folders, so when removing this make sure the folders have the correct UID/GID
    # (1000:1000 by default)
    user: root
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - ./media:/media
      - ./certs:/certs
      - ./custom-templates:/templates
    env_file:
      - .env
    depends_on:
      - postgresql
      - redis
volumes:
  database:
    driver: local
  redis:
    driver: local

It’s the default compose file.

Did you install via docker? Did you perform any modifications to the compose file aside from the steps listed in the directions?

You can, or you can simply declare the network share as the library directory and it’ll treat it like a regular directory.

I’ve worked at an ISP NOC for several years where part of my job was supporting various wired and wireless environments that have Internet access delivered in a variety of mediums.

Long story short, if your Verizon service is a cellular home plan (since it’s 300mbps and Verizon offers these plans it sounds like it could be) then you’re gonna feel it over gaming, especially especially with wireless. Your best experience will be wired, assuming the wires aren’t damaged or misterminated or CCA.

With wired, your LAN experience will be ideal from your computer until the router. The router, however, deals with two sides of the equation. Your local network and then the internet. It has to communicate outside of your home. If that’s happening over a cellular connection then you’re just going to see latency and packet loss and there’s nothing to do about it unless you can change physics.

Assuming you’re cellular, the fix is to move to a wired medium (even fixed wireless would be a step up though). Wired internet such as fiber or coaxial cable is far less susceptible to interference and is capable of moving data quicker and in a more stable method. But it tends to be more expensive and requires more “visible” maintenance on the ISP’s end which can be frustrating for the customer.

I do a lot of my docker on Debian, some on Ubuntu. Debian is perfect for it. Something like Fedora (or a relative of it) will be awesome too since Podman will be great with it.