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
Bundler hangs on resolving dependencies when a dependency does not support the current platform #6054
Comments
|
Interestingly and confusingly I just run your repro steps and I got the expected results :/ |
|
That's fascinating! I will try to figure out what might be different about my environment. Since it's happening inside a docker container, I'm not sure what it could be. |
|
Oh, totally my mistake — I messed up the repro steps. I edited the original issue to include the correct Gemfile.lock. The key is the |
Describe the problem as clearly as you can
When a dependency of a gem listed in the Gemfile does not support the current platform, bundler gets stuck in a loop attempting to re-resolve dependencies.
Did you try upgrading rubygems & bundler?
Yes, I'm using bundler 2.3.25.
Post steps to reproduce the problem
First, write the following files to an empty directory:
Gemfile
Gemfile.lock
Dockerfile
Then, in that directory, run
docker build --progress=plain --platform=linux/arm64 .. Note that I am doing this on an M1 Mac, which is natively ARM64. I'm not sure whether thisdockercommand will be possible on an x86_64 machine.Which command did you run?
What were you expecting to happen?
bundler should fail to install, because
sorbet=0.5.10554depends onsorbet-static=0.5.10554, andsorbet-static=0.5.10554doesn't support theaarch64-linuxplatform.What actually happened?
bundler gets stuck in a loop trying to re-resolve dependencies:
If not included with the output of your command, run
bundle envand paste the output belowI ran
bundle envin the Docker container:The text was updated successfully, but these errors were encountered: