Deploying Gitea with Docker causes server disk write exceptions. #13470

New Issue

GiteaMirror · 2025-11-02T10:43:21-06:00

GiteaMirror commented

2025-11-02 10:43:21 -06:00

Originally created by @devaige on GitHub (Sep 7, 2024).

Description

After Gitea is deployed in Docker mode and a demo project is pushed, it is observed for a week and a large number of BLOCK Input operations are seen through docker stats:

CONTAINER ID   NAME      CPU %     MEM USAGE / LIMIT     MEM %     NET I/O          BLOCK I/O         PIDS
d7165c75a99b   gitea     0.13%     116.3MiB / 7.634GiB   1.52%     19.2kB / 456kB   34.8GB / 24.6kB   20
c6881353dff8   nexus     0.43%     2.732GiB / 7.634GiB   35.78%    2.78kB / 0B      182MB / 15.2MB    95

For comparison, here is a Nexus service that has been running for half a month. This causes the server to have a large number of disk write operations and a surge in CPU usage during a fixed period of time. Gitea is not currently open to others and is still in the personal testing phase, so it is unlikely to be caused by the number of users.

Gitea Version

1.22.2

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

https://docs.gitea.com/zh-cn/installation/install-with-docker

Database

SQLite

Originally created by @devaige on GitHub (Sep 7, 2024). ### Description After Gitea is deployed in Docker mode and a demo project is pushed, it is observed for a week and a large number of BLOCK Input operations are seen through `docker stats`: ```shell CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS d7165c75a99b gitea 0.13% 116.3MiB / 7.634GiB 1.52% 19.2kB / 456kB 34.8GB / 24.6kB 20 c6881353dff8 nexus 0.43% 2.732GiB / 7.634GiB 35.78% 2.78kB / 0B 182MB / 15.2MB 95 ``` For comparison, here is a Nexus service that has been running for half a month. This causes the server to have a large number of disk write operations and a surge in CPU usage during a fixed period of time. Gitea is not currently open to others and is still in the personal testing phase, so it is unlikely to be caused by the number of users. ### Gitea Version 1.22.2 ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? https://docs.gitea.com/zh-cn/installation/install-with-docker ### Database SQLite

GiteaMirror added the issue/needs-feedback label 2025-11-02 10:43:21 -06:00

GiteaMirror closed this issue

2025-11-02 10:43:21 -06:00

GiteaMirror commented

2025-11-02 10:43:22 -06:00

@lunny commented on GitHub (Sep 10, 2024):

Do you have any other operations rather than packages push? i.e. git push/pull?

@lunny commented on GitHub (Sep 10, 2024): Do you have any other operations rather than packages push? i.e. git push/pull?

GiteaMirror commented

2025-11-02 10:43:22 -06:00

@Aathoss commented on GitHub (Sep 22, 2024):

I have the same problem: high disk usage, especially in writing, due to API calls.

The two services run on different machines:

I use the Docker image gitea/gitea:latest with an SQLite database.
For the job, I use Docker image gitea/act_runner:latest.

As soon as I launch act_runner, the machine hosting Gitea experiences a constant disk usage of 1.5MB/s.

@Aathoss commented on GitHub (Sep 22, 2024): I have the same problem: high disk usage, especially in writing, due to API calls. The two services run on different machines: - I use the Docker image gitea/gitea:latest with an SQLite database. - For the job, I use Docker image gitea/act_runner:latest. As soon as I launch act_runner, the machine hosting Gitea experiences a constant disk usage of 1.5MB/s.

GiteaMirror commented

2025-11-02 10:43:23 -06:00

@lunny commented on GitHub (Sep 22, 2024):

I think the most possible I/O is the repository indexer of Gitea. act_runner will generate logs if there are tasks. The logs will be written to database first and then disk after finished.

@lunny commented on GitHub (Sep 22, 2024): I think the most possible I/O is the repository indexer of Gitea. act_runner will generate logs if there are tasks. The logs will be written to database first and then disk after finished.

GiteaMirror commented

2025-11-02 10:43:23 -06:00

@devaige commented on GitHub (Sep 25, 2024):

I investigated for a long time but couldn't find the cause. Later, I simply disabled all automated tasks and the problem never occurred again. I guess it was caused by a certain automated task, but I couldn't locate it accurately.

@devaige commented on GitHub (Sep 25, 2024): I investigated for a long time but couldn't find the cause. Later, I simply disabled all automated tasks and the problem never occurred again. I guess it was caused by a certain automated task, but I couldn't locate it accurately.

GiteaMirror commented

2025-11-02 10:43:23 -06:00

@GiteaBot commented on GitHub (Oct 25, 2024):

We close issues that need feedback from the author if there were no new comments for a month. 🍵

@GiteaBot commented on GitHub (Oct 25, 2024): We close issues that need feedback from the author if there were no new comments for a month. :tea:

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#13470