Gitlab-runner local execution fails when Downloading LFS Files
Description of the problem
One major advantage for us in using GitLab CI is to use the easily installable runners to quickly verify the CI on our local machines. Unfortunatelly almost all our repositories have LFS files, and the execution (e.g.
gitlab-runner exec docker pages) seems to fail on all of them due to a
Smudge Error (both after cloning with SSH or HTTPs). The output of the executor looks appromitaely like this:
Running with gitlab-runner 11.3.1~beta.4.g0aa5179e (0aa5179e) Using Docker executor with image maven:3.3.9-jdk-8 ... Pulling docker image gitlab/gitlab-runner-helper:x86_64-0aa5179e ... Using docker image sha256:3f3da2655aa1ebfdf875c2d81667c0dc118122c7f2817a0bd8b53faac912131f for gitlab/gitlab-runner-helper:x86_64-0aa5179e ... Pulling docker image maven:3.3.9-jdk-8 ... Using docker image sha256:9997d8483b2fc521a4159feab922546dda0c5c22b5084f86dfab48f123ae4364 for maven:3.3.9-jdk-8 ... Running on runner--project-0-concurrent-0 via bsse-bs-dock-5-231.ethz.ch... Cloning repository... Cloning into '/builds/project-0'... done. Checking out 138a3af8 as master... Downloading page/themes/unitelabs/images/preview.png (109 KB) Error downloading object: page/themes/unitelabs/images/preview.png (c9ca663): Smudge error: Error downloading page/themes/unitelabs/images/preview.png (c9ca663134f101de37d6868f0c1e7438d24688b29237c3331a30ef0d25bffa18): batch request: missing protocol: "/Users/mnschulz/unitelabs/repositories/unitelabs_base.git/info/lfs" Errors logged to /builds/project-0/.git/lfs/logs/20181016T170759.0210499.log Use `git lfs logs last` to view the log. error: external filter 'git-lfs filter-process' failed fatal: page/themes/unitelabs/images/preview.png: smudge filter lfs failed ERROR: Job failed: exit code 1 FATAL: exit code 1
Note that cloning itself works fine (SSH or HTTPs), also the Runners hosted on Gitlab CE seem to handle the repository well.
Which Group/Project (with full path) is experiencing the issue?
This is a private repository, but the problem probably exists in public repositories as well.
Approximate date/time when the error occurred.
Errors with a local execution of gitlab-runners downloading LFS files have been occurring since we have started using GitLab over one year ago.
I have seen other Issues regarding problems with LFS, but I assume they are unrelated? References: