![]() Stop setting `BUNDLE_PATH`. All default bundler versions shipped with all supported rubies install gems to `GEM_HOME` by default, so this shouldn't be a breaking change and it's a less surprising behavior because it does not deviate from how bundler is configured by default. Future versions will probably install locally by default, but that hasn't happened yet. I think leaving bundler "unconfigured" also matches the direction of the recent change where the images no longer explicitly install `bundler` but simply leave whatever version comes with ruby. Similarly, it makes sense to me to leave whatever configuration comes by default with `bundler` in place. |
||
---|---|---|
2.4 | ||
2.5 | ||
2.6 | ||
2.7 | ||
.travis.yml | ||
Dockerfile-alpine.template | ||
Dockerfile-debian.template | ||
Dockerfile-slim.template | ||
generate-stackbrew-library.sh | ||
LICENSE | ||
README.md | ||
update.sh |
https://github.com/docker-library/ruby
Maintained by: the Docker Community
This is the Git repo of the Docker "Official Image" for ruby
(not to be confused with any official ruby
image provided by ruby
upstream). See the Docker Hub page for the full readme on how to use this Docker image and for information regarding contributing and issues.
The full image description on Docker Hub is generated/maintained over in the docker-library/docs repository, specifically in the ruby
directory.
See a change merged here that doesn't show up on Docker Hub yet?
For more information about the full official images change lifecycle, see the "An image's source changed in Git, now what?" FAQ entry.
For outstanding ruby
image PRs, check PRs with the "library/ruby" label on the official-images repository. For the current "source of truth" for ruby
, see the library/ruby
file in the official-images repository.
Build | Status | Badges | (per-arch) |
---|---|---|---|