• 18 Posts
  • 300 Comments
Joined 3 years ago
Cake day: June 10th, 2023
  • frozen@lemmy.frozeninferno.xyztoAnnouncements@lemmy.ml•Lemmy Release v0.19.12English
    1·
    7 months ago

    Below is my current dockerfile, which is using 0.19.11 right now to fix the issue. The issue happens when I switch to 0.19.12.

    networks:
  # communication to web and clients
  lemmyexternalproxy:
  lemmybridge:
  # communication between lemmy services
  lemmyinternal:
    driver: bridge
    internal: true

services:
  photon:
    image: ghcr.io/xyphyn/photon:latest
    networks:
      - lemmyexternalproxy
      - lemmyinternal
    ports:
      - 8080:3000
    environment:
      - PUBLIC_INSTANCE_URL=lemmy.frozeninferno.xyz
      - PUBLIC_LOCK_TO_INSTANCE=true
      - PUBLIC_DEFAULT_COMMENT_SORT=Top
      - PUBLIC_FULL_WIDTH_LAYOUT=true
      - PUBLIC_DEFAULT_FEED=Subscribed
    restart: unless-stopped
    depends_on:
      - lemmy
      - lemmy-ui

  proxy:
    image: nginx:1-alpine
    networks:
      - lemmyinternal
      - lemmyexternalproxy
    ports:
      # only ports facing any connection from outside
      - 8880:80
      - 8843:443
    volumes:
      - ./nginx.conf:/etc/nginx/nginx.conf:ro
      # setup your certbot and letsencrypt config
      - ./certbot:/var/www/certbot
      - ./letsencrypt:/etc/letsencrypt/live
    restart: unless-stopped
    depends_on:
      - pictrs
      - lemmy-ui

  lemmy:
    image: dessalines/lemmy:0.19.11
    hostname: lemmy
    networks:
      - lemmyinternal``
      - lemmybridge
    ports:
      - 8536:8536
    restart: unless-stopped
    environment:
      - RUST_LOG="warn,lemmy_server=info,lemmy_api=info,lemmy_api_common=info,lemmy_api_crud=info,lemmy_apub=info,lemmy_db_schema=info,lemmy_db_views=info,lemmy_db_views_actor=info,lemmy_db_views_moderator=info,lemmy_routes=info,lemmy_utils=info,lemmy_websocket=info"
    volumes:
      - ./lemmy.hjson:/config/config.hjson
    depends_on:
      - postgres
      - pictrs

  lemmy-ui:
    image: dessalines/lemmy-ui:0.19.11
    networks:
      - lemmyinternal
      - lemmybridge
    ports:
      - 1234:1234
    environment:
      # this needs to match the hostname defined in the lemmy service
      - LEMMY_UI_LEMMY_INTERNAL_HOST=lemmy:8536
      # set the outside hostname here
      - LEMMY_UI_LEMMY_EXTERNAL_HOST=192.168.0.10:1236
      - LEMMY_UI_HOST=lemmy-ui:1234
      - LEMMY_HTTPS=true
    depends_on:
      - lemmy
    restart: unless-stopped

  pictrs:
    image: asonix/pictrs:0.5
    # this needs to match the pictrs url in lemmy.hjson
    hostname: pictrs
    # we can set options to pictrs like this, here we set max. image size and forced format for conversion
    # entrypoint: /sbin/tini -- /usr/local/bin/pict-rs -p /mnt -m 4 --image-format webp
    networks:
      - lemmyinternal
      - lemmybridge
    environment:
      - PICTRS__API_KEY=API_KEY
      - RUST_BACKTRACE=full
      - PICTRS__UPGRADE__CONCURRENCY=256
      - PICTRS__OLD_REPO__PATH=/mnt/sled-repo
      - PICTRS__REPO__TYPE=postgres
      - PICTRS__REPO__URL=postgres://lemmy:<censored>@postgres:5432/pictrs
    user: 991:991
    volumes:
      - ./pictrs:/mnt
    restart: unless-stopped

  postgres:
    image: postgres:16-alpine
    # this needs to match the database host in lemmy.hson
    hostname: postgres
    networks:
      - lemmyinternal
    environment:
      - POSTGRES_USER=lemmy
      - POSTGRES_PASSWORD=<censored>
      - POSTGRES_DB=lemmy
    volumes:
      - ./postgres:/var/lib/postgresql/data
    restart: unless-stopped
    shm_size: 12gb

  adminer:
    image: adminer
    restart: always
    networks:
      - lemmyinternal
      - lemmyexternalproxy
    ports:
      - 10000:8080
  • frozen@lemmy.frozeninferno.xyztoAnnouncements@lemmy.ml•Lemmy Release v0.19.12English
    1·
    7 months ago

    I’m using the regular Docker file, and I’m getting the same thing.

    Lots of the following in the UI logs.

    { name: 'couldnt_find_person', message: '' }
{ name: 'couldnt_find_post', message: '' }
{
  name: 'unknown',
  message: 'Query deserialize error: invalid digit found in string'
}
{
  name: 'unknown',
  message: 'Query deserialize error: invalid digit found in string'
}
{ name: 'couldnt_find_post', message: '' }
{ name: 'couldnt_find_post', message: '' }

    However, Photon’s alternative UI works fine.