New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bundle install fails on WSL when using a git repository with a path #5322

Closed
omarqureshi opened this Issue Jan 12, 2017 · 9 comments

Comments

Projects
None yet
4 participants
@omarqureshi

omarqureshi commented Jan 12, 2017

I'm currently using Docker for Windows (1.12.6) and WSL on Windows 10 (Linux DESKTOP-DLRRFKC 3.4.0+ #1 PREEMPT Thu Aug 1 17:06:05 CST 2013 x86_64 x86_64 x86_64 GNU/Linux)

I'm having issues when running bundle install --path vendor/bundle, note that this ONLY happens in WSL when writing to NTFS, both in Linux and OSX this works fine

`git clone --no-checkout --quiet
"/myapp/vendor/bundle/ruby/2.3.0/cache/bundler/git/bootstrap-sass-b9ed78534df7520565c4f55770e38b8d270f127f"
"/myapp/vendor/bundle/ruby/2.3.0/bundler/gems/bootstrap-sass-cf9a9b181fdf"` due
to error (4/4): Bundler::Source::Git::GitCommandError Git error: command `git
clone --no-checkout --quiet
"/myapp/vendor/bundle/ruby/2.3.0/cache/bundler/git/bootstrap-sass-b9ed78534df7520565c4f55770e38b8d270f127f"
"/myapp/vendor/bundle/ruby/2.3.0/bundler/gems/bootstrap-sass-cf9a9b181fdf"` in
directory /myapp has failed. If this error persists you could try removing the
cache directory
'/myapp/vendor/bundle/ruby/2.3.0/cache/bundler/git/bootstrap-sass-b9ed78534df7520565c4f55770e38b8d270f127f'error:
internal error: refs/remotes/origin/2.0-stable is not a valid packed reference!

I've put up a repository with an example of what I mean at https://github.com/omarqureshi/not_valid_packed_reference

I'm pretty sure that this is a Git issue and will also be looking to report this to the Git mailing list, however, they may equally say that this is a Docker and/or NTFS issue

The volume mount is the cause of this https://github.com/omarqureshi/not_valid_packed_reference/blob/master/docker-compose.yml#L8

I can get around this by NOT using --path, however, it would be preferable if this just worked on WSL too.

If you'd like any other information, please let me know, otherwise, the Dockerfile should have enough information there to let you know what my setup is like.

@segiddins

This comment has been minimized.

Show comment
Hide comment
@segiddins

segiddins Jan 12, 2017

Member

I'm honestly not seeing how this could be a bundler issue if the same git command works everywhere else -- it looks like an issue either with git or WSL to me.

Member

segiddins commented Jan 12, 2017

I'm honestly not seeing how this could be a bundler issue if the same git command works everywhere else -- it looks like an issue either with git or WSL to me.

@omarqureshi

This comment has been minimized.

Show comment
Hide comment
@omarqureshi

omarqureshi Jan 12, 2017

I personally think it's more of an issue with Git interacting with NTFS, however, given that the use of bundler is the only place that I have experienced this (and I have successfully been using Docker, Git and WSL on other Rails apps before this), it's probably not a bad place to put this issue.

I'll probably try testing this by installing Ruby on WSL and then bundler too.

omarqureshi commented Jan 12, 2017

I personally think it's more of an issue with Git interacting with NTFS, however, given that the use of bundler is the only place that I have experienced this (and I have successfully been using Docker, Git and WSL on other Rails apps before this), it's probably not a bad place to put this issue.

I'll probably try testing this by installing Ruby on WSL and then bundler too.

@segiddins

This comment has been minimized.

Show comment
Hide comment
@segiddins

segiddins Jan 12, 2017

Member

Can you run the git command successfully outside of bundler?

Member

segiddins commented Jan 12, 2017

Can you run the git command successfully outside of bundler?

@omarqureshi

This comment has been minimized.

Show comment
Hide comment
@omarqureshi

omarqureshi Jan 12, 2017

I've tried a git clone --no-checkout bootstrap-sass/ other-bootstrap/ and that seems to work, however, that's not quite the same here

omarqureshi commented Jan 12, 2017

I've tried a git clone --no-checkout bootstrap-sass/ other-bootstrap/ and that seems to work, however, that's not quite the same here

@omarqureshi

This comment has been minimized.

Show comment
Hide comment
@omarqureshi

omarqureshi Jan 12, 2017

What exactly does a bundle install do when given a github repository and a tag?

omarqureshi commented Jan 12, 2017

What exactly does a bundle install do when given a github repository and a tag?

@omarqureshi

This comment has been minimized.

Show comment
Hide comment
@omarqureshi

omarqureshi Jan 12, 2017

Also, with the example, it makes no difference whether I specify a tag or not.

omarqureshi commented Jan 12, 2017

Also, with the example, it makes no difference whether I specify a tag or not.

@PhilipOakley

This comment has been minimized.

Show comment
Hide comment
@PhilipOakley

PhilipOakley Jan 12, 2017

There was a similar issue recently on Git for Windows with fix dscho/git@2174823 and a Git test git/git@16615f0 with fix git/git@7814fbe

Check if it is relevant
(This responds to the message on the git list - can't reply there at this moment)

PhilipOakley commented Jan 12, 2017

There was a similar issue recently on Git for Windows with fix dscho/git@2174823 and a Git test git/git@16615f0 with fix git/git@7814fbe

Check if it is relevant
(This responds to the message on the git list - can't reply there at this moment)

@omarqureshi

This comment has been minimized.

Show comment
Hide comment
@omarqureshi

omarqureshi Jan 12, 2017

I'll have a look later on this evening, thanks!

omarqureshi commented Jan 12, 2017

I'll have a look later on this evening, thanks!

@colby-swandale

This comment has been minimized.

Show comment
Hide comment
@colby-swandale

colby-swandale Feb 21, 2017

Member

I'm closing this for now. If you're still experiencing your original issue don't be afraid to re-open this ticket.

Member

colby-swandale commented Feb 21, 2017

I'm closing this for now. If you're still experiencing your original issue don't be afraid to re-open this ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment