You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 14, 2021. It is now read-only.
Since 1.14.x, Bundler tries to create a fallback home directory underneath Dir.tmpdir in case the user home read from Bundler.rubygems.user_home (doing File.expand_path "~") is not writable. This is causing problems in certain scenarios such as #5371 and #5363.
How about adding an environment variable $BUNDLE_HOME:
When set to a path, the path is used instead of Bundler.rubygems.user_home. Good for deployments to readwrite FS where the regular user home is not writable due to security restrictions.
When set to "", no fallback home directory is created and Bundler does not attempt to read the global config. Good for deployments to writeonly FS (e.g. Docker).
The text was updated successfully, but these errors were encountered:
Since 1.14.x, Bundler tries to create a fallback home directory underneath
Dir.tmpdir
in case the user home read fromBundler.rubygems.user_home
(doingFile.expand_path "~"
) is not writable. This is causing problems in certain scenarios such as #5371 and #5363.How about adding an environment variable
$BUNDLE_HOME
:Bundler.rubygems.user_home
. Good for deployments to readwrite FS where the regular user home is not writable due to security restrictions.The text was updated successfully, but these errors were encountered: