3rd party gitea - data volumes lost after updating the cow?

adriano

Hi, after updating my cow with update.sh and followed by a reboot, I “lost” data in my gitea installation. The installation was done, following: https://mailcow.github.io/mailcow-dockerized-docs/third_party-gitea/

It looks like the repositry storage is gone and the the avatar images also…

docker-compose logs --tail=200 gitea-mailcow shows:

...ules/context/repo.go:527:RepoAssignment() [E] RepoAssignment Invalid repo /app/gitea/data/gitea-repositories/gitea-admin/my1strepo.git: no such file or directory ...uters/routes/base.go:116:2() [W] Unable to find avatars d7e6c85658ccd4c67bd3a10b3d7e27c7 gitea-mailcow_1 | 2021/07/09 10:16:58 Completed GET /avatars/d7e6c85658ccd4c67bd3a10b3d7e27c7?size=48 404 Not Found in 657.519µs

Thanks for any help/ideas!

diekuh

Hi, if you created it as described in the docs, it would use ./data/gitea, there is no way we would delete or purge a directory on your fs.

adriano

Hi, and thanks for your quick reply! Sorry, I am getting to old ;-) docker still confuses me and I am lacking a lot of understanding…

Having followed the documentation and having:

gitea-mailcow: image: gitea/gitea:1 volumes: - ./data/gitea:/data networks: mailcow-network: aliases: - gitea ports: - "${GITEA_SSH_PORT:-127.0.0.1:4000}:22"

in docker-compose.override.yml and running docker-compose up -d gives me a directory structure of:

/opt/mailcow-dockerized/data/gitea# ls git gitea ssh

on my mailcow host. Maybe this does not match giteas own configuration (any more)?

Repository-Wurzelpfad /app/gitea/data/gitea-repositories Verzeichnis für statische Dateien /app/gitea Benutzerdefinierter Root Pfad /data/gitea Logdateipfad /app/gitea/log

Should the repository directory structure be visible from the mailcow-host under ./data?
How would I safely remove the gitea container and its data to start the gitea install from scratch but keep my mailcow install intact?

Thanks a ton!

adriano

Well, to make a long story short. For sure this is rooted in me not understanding Docker. To better understand this and to improve my understanding of Docker, how would I safely remove the gitea container and its data to start the gitea install from scratch but keep my mailcow install intact?

adriano

I’ll start over with gitea . Its all in the documentation ;-) Thanks a lot: https://mailcow.github.io/mailcow-dockerized-docs/debug-rm_volumes/

adriano

Help please….
Sorry, I wanted to start from scratch with the gitea docs. But following https://mailcow.github.io/mailcow-dockerized-docs/debug-rm_volumes/ to delete the persistant storage of the gitea container leads me to the question if there is a persistant storage for the container??????

docker-compose.override.yml

`
version: ‘2.1’
services:

    gitea-mailcow:
        image: gitea/gitea:1
        volumes:
            - ./data/gitea:/data
        networks:
            mailcow-network:
                aliases:
                    - gitea
        ports:
            - "${GITEA_SSH_PORT:-127.0.0.1:4000}:22"

and:

docker volume ls DRIVER VOLUME NAME local 1d2a3e66bc7099e35e06b1d282c0c02620f251220a446d3fb9c5d45b38bc79ff local 01f81e1c7a4dd97f09ff3597ed35fe7771b69bd320da68c9e81b7e5466283dbf local 2cdb025c06588e77811f6dad2d93bf8eb075a140b85c5057ade4e24cec7b287b local 3b88c58e0824dc8fc08dd72959a83cd2967d70850a8b501d70ea7d0dd27bcefe local 3e485c7361f977f5272b8bb05a916b9dc27087736efbc1a82485ef8f7f7d0a5c local 3f92ab5c89b91c393e12bc99cebc6fa29a60a6a5538391e930a0092d03d68c57 local 4b1e573aec78fba7aba81402d0dc03b8e7d4582c91056de08c928338101e5276 local 04b15414916df3262a84d74c61dd42bb70c5ec64a711a4888571eff1eec374b3 local 06b49be632a848b9e5de506e5ec3511da7d0484a6d67c09529dfc35f6ff47bf1 local 7d7a98f1ff776c4afff993e599219dbda10074e231dca0e89fd3e7ca2ead938b local 7e8733470174a8aae90c969dc3759c100ad9443730d3c2d2146e00fcccf087ee local 8f0c1fd0e366ab17ec07bfcd4cf982b726875745cfa0556cfca51995dff86e7e local 08cf5b122c4cf4764deb15b08ccd55b7cc6c31bc7e63bbe7307e01437422fbb0 local 9d5fddbc61118aa8b3d8128c344c55a83969be25f095173ce68e54a375d8fd23 local 95d055439190bc0ef4a08e202c2ae40663255705ed5619a84b871274fd608a4e local 99f695d4afa0dd2a466254e332bb0e1a591c3eec9108aca8e3ecd8557af6de1a local 143deebc3f09e737f08a41381cdd87506dc9d82b19081b299af0a9480877ce4e local 195a3938f0f73141c9c139c229f968d6d969b384ca7bdb2fade52650e3d7764d local 608f6524e6ccfb317d0f00be99516ff4f833b5b810ee9fc9ea683f2af97fd810 local 726b28cd8b72955b4757c8b308a5f9c66f8f66baf9c156dbbd01a3d957c27b77 local b2b9f32b88c07231c6dcee4d44f7916e1fc5325323100fd836af44dd41f2e132 local b68ad83817ae36c19469f205e4b4566a527136febb67485a2a8c5432199bb2d7 local bcda5a1272beedd654abc11dd9339967511a794c4b85f16ef2198c4fb64d4336 local d83ad0c62660930d65d428bd488436ec3f2954c20437127631a7809b491daaa4 local d27486158603c28b26281b4f80901b226806fb9a034eb110b0cada59fd367098 local e7aad389356e0d1522df74fbeab0c63fd95800175a6c247ef482b2c167913e0e local f10e16183f1d7d52e8671e75e04e9f43248b3e09cc81f116dc3e7feae49c3b5b local mailcowdockerized_crypt-vol-1 local mailcowdockerized_mysql-socket-vol-1 local mailcowdockerized_mysql-vol-1 local mailcowdockerized_postfix-vol-1 local mailcowdockerized_redis-vol-1 local mailcowdockerized_rspamd-vol-1 local mailcowdockerized_sogo-userdata-backup-vol-1 local mailcowdockerized_sogo-web-vol-1 local mailcowdockerized_solr-vol-1 local mailcowdockerized_vmail-attachments-vol-1 local mailcowdockerized_vmail-index-vol-1 local mailcowdockerized_vmail-vol-1 local mailcowdockerized_xmpp-upload-vol-1 local mailcowdockerized_xmpp-vol-1

there is no volume for gitea??? Is this correct? So how to restart with gitea from scratch?

There is /opt/mailcow-dockerized/data/gitea/gitea/conf/app.ini on my mailcow hosts file system which I can alter and which settings change giteas behavior… Do I have to adapt settings in app.ini like

[repository] ROOT = /app/gitea/data/gitea-repositories
to another path??

Thanks for any help - I am lost