The docker image did not install git-lfs #2225

New Issue

GiteaMirror · 2025-11-02T04:28:18-06:00

GiteaMirror commented

2025-11-02 04:28:18 -06:00

Originally created by @Haixing-Hu on GitHub (Aug 21, 2018).

Gitea version (or commit ref): Gitea version ce7c64c built with: bindata, sqlite
Git version: git version 2.15.2
Operating system: docker image gitea/gitea
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant
Log gist:

Description

The docker image of gitea did not install git-lfs. Therefore the client side could commit lfs objects but cannot pull lfs objects.

Following procedure will reproduce the problem:

install a docker image gitea/gitea
create a repository and add some binary file.
git lfs track the binary file.
push to the repository
try to clone the repository in another place. It will fail to pull the lfs object.

Screenshots

Originally created by @Haixing-Hu on GitHub (Aug 21, 2018).  - Gitea version (or commit ref): Gitea version ce7c64c built with: bindata, sqlite - Git version: git version 2.15.2 - Operating system: docker image gitea/gitea - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No - [ ] Not relevant - Log gist: ## Description The docker image of gitea did not install git-lfs. Therefore the client side could commit lfs objects but cannot pull lfs objects. Following procedure will reproduce the problem: - install a docker image gitea/gitea - create a repository and add some binary file. - git lfs track the binary file. - push to the repository - try to clone the repository in another place. It will fail to pull the lfs object. ## Screenshots

GiteaMirror added the issue/needs-feedback label 2025-11-02 04:28:18 -06:00

GiteaMirror closed this issue

2025-11-02 04:28:18 -06:00

GiteaMirror commented

2025-11-02 04:28:19 -06:00

@lafriks commented on GitHub (Aug 21, 2018):

But server does not need to have git-lfs installed for it to work on client side

@lafriks commented on GitHub (Aug 21, 2018): But server does not need to have git-lfs installed for it to work on client side

GiteaMirror commented

2025-11-02 04:28:20 -06:00

@Haixing-Hu commented on GitHub (Aug 23, 2018):

@lafriks No，the server must have the git-lfs installed to make the gitea work correctly. If the server has no git-lfs, checking out a lfs repository always failed. But if it installed, checking out succeeds.

@Haixing-Hu commented on GitHub (Aug 23, 2018): @lafriks No，the server must have the git-lfs installed to make the gitea work correctly. If the server has no git-lfs, checking out a lfs repository always failed. But if it installed, checking out succeeds.

GiteaMirror commented

2025-11-02 04:28:20 -06:00

@lafriks commented on GitHub (Aug 24, 2018):

Are you talking about editing files from UI?

@lafriks commented on GitHub (Aug 24, 2018): Are you talking about editing files from UI?

GiteaMirror commented

2025-11-02 04:28:20 -06:00

@sapk commented on GitHub (Aug 24, 2018):

@Haixing-Hu Can you provide more details on an example/story when gitea failed because it missed git-lfs ? For exemple what command you used.

@sapk commented on GitHub (Aug 24, 2018): @Haixing-Hu Can you provide more details on an example/story when gitea failed because it missed git-lfs ? For exemple what command you used.

GiteaMirror commented

2025-11-02 04:28:21 -06:00

@techknowlogick commented on GitHub (Oct 29, 2018):

@Haixing-Hu following up on @sapk's question. Would you be able to provide more details?

@techknowlogick commented on GitHub (Oct 29, 2018): @Haixing-Hu following up on @sapk's question. Would you be able to provide more details?

GiteaMirror commented

2025-11-02 04:28:21 -06:00

@techknowlogick commented on GitHub (Nov 29, 2018):

Closing as needs-feedback. Please re-open if needed.

@techknowlogick commented on GitHub (Nov 29, 2018): Closing as needs-feedback. Please re-open if needed.

GiteaMirror referenced this issue

2025-11-02 12:06:53 -06:00