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

Docker container directly copy file migration, causing subsequent submissions to be invisible but can be pulled #7753

Open
1 task done
cl-Rainful opened this issue May 29, 2024 · 0 comments
Labels
💊 bug Something isn't working

Comments

@cl-Rainful
Copy link

Gogs version

0.13

Git version

  • Server: 0.13(gogs version)
  • Client: 2.37.2.windows.2

Operating system

Windows 10

Database

mysql:8.0.29

Describe the bug

I used to use it normally (Docker-compose deployment), but two months ago, my server expired, so I used to directly compress the copy file by directly copying the file and then decompressed it on the new machine and directly deployed. Recently I discovered that I all found me all my Submitting information is not visible on GOGS, but you can still fetch it

here is my docker-compose.yml
version: "3"
services:

gogs:
image: gogs/gogs:0.13
container_name: gogs
restart: unless-stopped
volumes:
- ./data:/data
networks:
- service

networks:
service:
external: true

docker network service is normal bridge

To reproduce

use gogs normally, and then stop docker, compress the all file into tar, scp to new machine and decompress it, then docker start

Expected behavior

i only wants to report it

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@cl-Rainful cl-Rainful added the 💊 bug Something isn't working label May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💊 bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant