-
Notifications
You must be signed in to change notification settings - Fork 79
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_VERSION
not picked up with ruby 2.5.1-slim base image
#32
Comments
@vrinek Have you updated the image version in the Docker compose file? (This might be necessary for Docker to use the changed environment variables.) |
Hi,
I remove all bundler block and use just: What I am doing wrong? Thanks! |
@elalemanyo The problem is with your Gemfile.lock; how did it get into the Docker image? It shouldn't be there at the time of building it. |
@palkan I am almost doing the same way, I did some changes 🙈 All the docker files (Dockerfile, docker-compose.yml) are inside a folder (
and docker-compose.yml:
thanks for your help |
As far as I understand, the image is build successfully, the exception is raised during Then, you should either specify the same version for the Docker image as in your |
@palkan the error is just when I try to check the bundle version 🤷♂️, the interesting thing ist that if I remove all bundler stuff from the Dockerfile and check the bundle version I get |
Try to run |
@palkan out of the project root I get this error:
|
@palkan now works. I was so stupid and After doing this change I can install the correct bundler version like this:
thanks for all the help |
I've tried using dockerdev with the
2.5.1-slim-stretch
base docker image and it kept using v1.16 for bundler.After a little digging, I noticed that the base image explicitly defines the
BUNDLER_VERSION
as an environment variable: https://hub.docker.com/layers/ruby/library/ruby/2.5.1-slim/images/sha256-f05f349dcb24a2e4d556fc95476753348e4678503689422cd093de7067ea59c5?context=exploreENV BUNDLER_VERSION=1.16.6
The same issue is not present in the
2.6.3-slim-buster
base image.I am not sure how to fix this elegantly. For now, I have renamed my
ARG
to not conflict withBUNDLER_VERSION
but I cannot consider this optimal.Any other ideas on how to mitigate this for ruby 2.5.1?
The text was updated successfully, but these errors were encountered: