sameersbn / sameersbn/docker-gitlab
Doesn't pickup LFS settings
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Hi all!
After adding the following options to the docker-compose.yml and doing 'docker-compose up' LFS doesn't seem to use S3
- GITLAB_LFS_ENABLED=TRUE
- GITLAB_LFS_OBJECT_STORE_ENABLED=TRUE
- GITLAB_LFS_OBJECT_STORE_REMOTE_DIRECTORY=****
- GITLAB_LFS_OBJECT_STORE_CONNECTION_PROVIDER=AWS
- GITLAB_LFS_OBJECT_STORE_CONNECTION_AWS_ACCESS_KEY_ID=****
- GITLAB_LFS_OBJECT_STORE_CONNECTION_AWS_SECRET_ACCESS_KEY=****
- GITLAB_LFS_OBJECT_STORE_CONNECTION_AWS_REGION=us-east-1
- GITLAB_LFS_OBJECT_STORE_BACKGROUND_UPLOAD=false
- GITLAB_LFS_OBJECT_STORE_DIRECT_UPLOAD=true
Also when I ssh into the gitlab container and check the /home/git/gitlab/config/gitlab.yml it doesn't seem to contain any of the LFS settings. Am I missing something?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the docker-compose.yml environment entries and the generated /home/git/gitlab/config/gitlab.yml inside the GitLab container. Determine why the listed LFS settings are not present, then verify that the container uses S3 for LFS storage after the configuration is applied.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, gitlab
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100