sameersbn / sameersbn/docker-gitlab

Error when cloning big repo over https

Open
#688 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

wontfix
Dominant language
Shell
Stars
8.1k
Forks
2.1k
Avg merge
17h 47m
Merged PRs (30d)
7

Description

Hello,

I have some troubles when cloning big repo (more than 1G) over https.

I got this error :

Cloning into 'MY_DIRECTORY\bam-src'...
POST git-upload-pack (150 bytes)
remote: Counting objects: 5478, done.
fatal: The remote end hung up unexpectedly
fatal: protocol error: bad pack header
error: RPC failed; result=18, HTTP code = 200

I tried a lot of things without any result.

I tried to set some git config :
git config --global pack.windowMemory "2000m"
git config --global pack.SizeLimit "2000m"

Also this one : git config --global http.postBuffer 2000000000

I also added some conf to the docker-gitlab :
- GITLAB_MAX_OBJECT_SIZE=2000000000
- UNICORN_WORKERS=7
- UNICORN_TIMEOUT=1200

Can you help me please ? I am stuck since several days ..

My server info :

host : Ubuntu 14.04 LTS

docker version
Client:
Version: 1.9.1
API version: 1.21
Go version: go1.4.2
Git commit: a34a1d5
Built: Fri Nov 20 13:12:04 UTC 2015
OS/Arch: linux/amd64
Server:
Version: 1.9.1
API version: 1.21
Go version: go1.4.2
Git commit: a34a1d5
Built: Fri Nov 20 13:12:04 UTC 2015
OS/Arch: linux/amd64

docker info
Containers: 34
Images: 307
Server Version: 1.9.1
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 375
Dirperm1 Supported: false
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.13.0-66-generic
Operating System: Ubuntu 14.04.3 LTS
CPUs: 4
Total Memory: 3.844 GiB
Name: ns371642.ip-37-187-105.eu
ID: KHGB:5JDZ:DNOD:YIZP:DUXA:7WDO:DMKW:V2XT:CWKR:F64G:PTVA:G7MY
WARNING: No swap limit support

docker run
sudo docker-compose up

Thanks in advance for your help.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository file or test is named. Start by reproducing the large HTTPS clone with the reported Docker, GitLab, Ubuntu, and Git versions, then inspect the docker-compose service configuration and logs; done means identifying a reproducible cause and a confirmed configuration or deployment fix.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, git, gitlab
Domain
infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.