libgit2 / libgit2/libgit2sharp
Repository not being cloned inside a docker container
还没有人认领这个 Issue。
- 主要语言
- C#
- 星标
- 3.5k
- 派生
- 925
- PR 合并指标
- 30 天内没有已合并 PR
描述
Reproduction steps
I currently am deploying a micro-service using .net standard 2.0, which either clones or updates a repo from GitLab.
For this I have a functionality that works perfectly in a Windows environment, but it does not do the trick inside a docker container after I spin it up.
Expected behavior
The repo should be cloned/pulled in a Docker container just like in Windows.
Actual behavior
No repo structure is present inside the linux directory (permissions set to 777). I am also seeing the directory's timestamp being updated when it should do the pull.
Version of LibGit2Sharp (release number or SHA1)
**netstandard2.0**Operating system(s) tested; .NET runtime tested
Working:
Windows 10 Enterprise, 64-bit
Not working:
Linux 828ec2e85f2c 4.9.184-linuxkit #1 SMP Tue Jul 2 22:58:16 UTC 2019 x86_64 GNU/Linux
Implementation
if (gitFolder.GetDirectories().Length == 0)
{
try
{
// Get user credentials
Repository.Clone("repository.git", deployerPath, new CloneOptions()
{
BranchName = "develop",
CredentialsProvider = CredentialsProvider(),
});
}
catch (Exception ex)
{
...
}
}
else
{
try
{
var repository = new Repository(deployerPath);
Commands.Pull(repository,
new Signature("blah", "blah@blah.com", DateTimeOffset.Now), new PullOptions()
{
FetchOptions = new FetchOptions() {CredentialsProvider = CredentialsProvider()},
MergeOptions = new MergeOptions() {FailOnConflict = true},
});
}
...
I raised this question in SO (find it here); however, I have not received a response back.
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
报告的入口点是所示 C# 实现中的 Repository.Clone 和 Commands.Pull;首先在列出的 Linux Docker 环境中使用 LibGit2Sharp 0.26.1 重现该行为,并捕获异常或状态输出。完成的标准是确定 repository 缺失的原因,并记录或实现一个经过验证且兼容容器的修复方案。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- csharp, docker, gitlab
- 领域
- devops
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 25/100