[BUG] No data shown in UI after docker pull new images about docker-grocy HOT 6 CLOSED

I get that. If you had come to us when it first broke during an upgrade, we could have helped. But after changing mounts, too much is changed and we can't possibly reproduce your setup to properly troubleshoot.

If it breaks again, feel free to drop by our Discord, which is great for quick chats and troubleshooting.

Good luck!

from docker-grocy.

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

from docker-grocy.

You're mounting an incorrect folder. Please follow the readme

from docker-grocy.

I started with:

  grocy:
    image: lscr.io/linuxserver/grocy:latest
    container_name: grocy
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/Copenhagen
    volumes:
      - /mnt/data/docker/grocy:/config
    ports:
      - "10.0.30.21:9283:80"
    restart: unless-stopped

I had it working a loooong time ago, but hadn't used it for many months (years?) until I tried again recently, and it no longer worked; I just got a page showing:

Unable to run Grocy: config.php in data directory (/app/www/public/../data) not found. Have you copied config-dist.php to the data directory and renamed it to config.php?

Searching for a fix, I found someone saying that swapping :/config to :/var/www/data worked for them. Different docker image, I think, but I tried, and it worked where nothing else did.

EDIT: Also found suggestion of :/var/www/data` here

Since then, it has worked until today when I updated the container. Changing back to /mnt/data/docker/grocy:/config gives the same result that made me change to /mnt/data/docker/grocy:/var/www/data in the first place, the web UI doesn't load (The page isn’t redirecting properly) despite no errors in docker logs if keeping the persistent data (initially created with /mnt/data/docker/grocy:/config).

  grocy:
    image: lscr.io/linuxserver/grocy:latest
    container_name: grocy
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/Copenhagen
    volumes:
      - /mnt/data/docker/grocy:/config
    ports:
      - "10.0.30.21:9283:80"
    restart: unless-stopped

docker kill grocy
sudo rm -rf /mnt/data/docker/grocy
docker-compose up -d

The page isn’t redirecting properly`) despite no errors in docker logs if keeping the persistent data (initially created with `/mnt/data/docker/grocy:/config

So it seems like I should worry about why a new instance with docker-compose as in this post doesn't get me to the login page instead?

Any idea why that is?

from docker-grocy.

You can't just switch mount points like that and expect it not to break. That suggestion you linked is not even for this image. Your persistent folder on host is likely broken beyond repair.

You need to either start with a fresh config folder and start over, or restore from a working backup (likely from before you switched the mount point in the first place.

from docker-grocy.

It's not so much that I didn't expect anything to break when changing mount points, it's more that it already was broken using /config (after not accessing it for a while), before making changes to the documented setup, so I got a bit... desperate? Adventurous? Somewhere in between.

But sure, I'll restart (I have scripts to re-add all products). And avoid leaving it running for months/years between using it going forward.

from docker-grocy.