Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] feed-icons mount point changed upstream without being reflected in docker-compose.yml #517

Open
winneratwin opened this issue Jun 2, 2024 · 0 comments
Labels

Comments

@winneratwin
Copy link

Describe the bug
The feed-icons folder has changed from location in the docker-compose example.

https://gitlab.tt-rss.org/tt-rss/tt-rss/-/commit/a30b9bb649#4debf48ffbb605888365af7cf016170407384eca_1675_1691

Have you googled?
Yes

Deployment method

  • Docker Compose
services:
 ttrss:
   image: wangqiru/ttrss
   restart: unless-stopped
   environment:
     - SELF_URL_PATH=https://rss.redacted.com/
     - DB_HOST=10.69.0.8
     - DB_PORT=5432
     - DB_NAME=tinytinyrss
     - DB_USER=redacted
     - DB_PASS=redacted
   volumes:
     - ./plugins:/var/www/plugins.local
     - ./cache:/var/www/cache/
     #- ./app:/var/www/
   networks:
     traefik:
       ipv4_address: 10.69.0.40



networks:
 traefik:
   external: true

Deployment environment

  • OS: raspberry pi os Linux raspberrypi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
  • Browser: firefox

To Reproduce
Steps to reproduce the behavior:

  1. launch image without changing icons:/var/www/feed-icons/ to icons:/var/www/cache/feed-icons/
  2. add a feed with a icon
  3. wait for it to fetch the icon
  4. restart the container
  5. see no icons

Expected behavior
The icons should be persistent

Screenshots
Screenshot of ttrss instance after restarting container having changed mount point to the correct point.
image

Error logs
Would look like normal logs due to it being a persistence problem.

Additional context
Seems like you bumped the postgres version in docker-compose without realizing that the configuration was broken.

@winneratwin winneratwin added the bug label Jun 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant