diff options
| author | Dan Allen <dan.j.allen@gmail.com> | 2022-10-12 04:22:46 -0600 |
|---|---|---|
| committer | Dan Allen <dan.j.allen@gmail.com> | 2022-10-12 04:22:46 -0600 |
| commit | b27407d8ced2a176fec5ba7342466e5be6e9acc2 (patch) | |
| tree | 0ac6e9baa9e6266307d53f8a92fc086bfaeeb4f9 /docs | |
| parent | 24956eff390f56d27c62accf0f6ea4a6eeb89b8f (diff) | |
add warning to docs about not using gem install as root user unless in a container
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/modules/install/pages/ruby-packaging.adoc | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/docs/modules/install/pages/ruby-packaging.adoc b/docs/modules/install/pages/ruby-packaging.adoc index 60bb1ab9..133ce164 100644 --- a/docs/modules/install/pages/ruby-packaging.adoc +++ b/docs/modules/install/pages/ruby-packaging.adoc @@ -5,6 +5,11 @@ The benefit of using Ruby packaging to install Asciidoctor is that it's universa Provided you have configured Ruby correctly, Ruby packaging works the same way across Ruby runtimes and operating systems. This page explains how to use Ruby packaging to install Asciidoctor. +WARNING: Unless you're running in a container (Docker, podman, OCI), _never_ install gems using `gem install` as the root user. +Doing so will almost certainly interfere with, and possibly corrupt, the Ruby installation on your system. +We strongly advise you to use <<Bundler>> to manage your gems within a project (or at very least, within user space). +The `gem install` instructions are provided for when you're running in a container. + == Configure Ruby packaging The best way to ensure Ruby is configured to use Ruby packaging is to install Ruby using a Ruby version manager. |