I was using docker container atlassian/bitbucket-server:6.9.0 connected to external DB running postgres:12.12
Container volume was mapped as /localhost_directory:/var/atlassian/application-data/bitbucket
After re-installing host OS I have decided to use podman instead docker however I cannot start container anymore.
I was able to run clean bitbucket server that is connected to new DB ton the same postgresql and this works fine.
When I change configuration in the bitbucket.properties and point to OLD DB I'm able to start and login to bitbucket. I also can see all my repositories however when I access them they are empty. This is because the /var/atlassian/application-data/bitbucket/shared/data/repositories is empty.
Now the problem is where I copy data from old /var/atlassian/application-data/bitbucket/shared/data/repositories to currently running server than I'm still not able to see any data in the repository.
I did make sure owner of all files in the /var/atlassian/application-data/bitbucket is set to bitbucket:bitbucket. however I'm not able to change permissions even as a root because following errors:
chown: changing ownership of './shared/data/repositories/372/objects/17/75531206d46b83a0b3acc2d1a9b43ae03bef77': Permission denied
chown: changing ownership of './shared/data/repositories/372/objects/8f/cfd5cb58efa641c050d717a72860e40bfd57fe': Permission denied
chown: changing ownership of './shared/data/repositories/372/objects/10/7f48be69ed24162de635eff8fb0874c39db51c': Permission denied
When I access repository from the browser I see following error
'/usr/bin/git cat-file -t refs/heads/master:' exited with code 128 saying: fatal: failed to read object 38e55dfaab92c8e11dd8452550a2451b25644f7a: Permission denied
Please see your system administrator.
and from logs:
Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...