Thanks for that info. I did combine an upgrade (1.20 to 1.21) with the migrations, but I guess I lucked into it working. My problem was that the container's path to the migrated gitea volume was incorrect.
- Posts
- 25
- Comments
- 103
- Joined
- 2 yr. ago
- Posts
- 25
- Comments
- 103
- Joined
- 2 yr. ago
homeassistant @lemmy.world Dreametech L10s Ultra won't clean - it demands to be returned to base
homeassistant @lemmy.world Looking for help integrating Dreametech L10s Ultra with Home Assistant
homeassistant @lemmy.world IR and RF blaster recommendations
homeassistant @lemmy.world DreameBot L10s Ultra questions
Linux @lemmy.ml Java app dropping connection to keyboard?

I don't know if your problem is the same as mine was, but the symptom sounds the same.
The docker-compose.yaml file shown in the Forgejo documentation for docker installation shows this mount:
volumes: - ./forgejo:/dataFor me, Forgejo installed and created new resource files in
/dataand ignored the resource files gitea alread made.I changed the volume to:
volumes: - data:/var/lib/giteaForgejo then recognized the gitea resources.